Debugger partially broke after installing update 2 to VS2015

After installing update 2 to Visual Studio 2015 Community Edition, TypeScript debugging broke partially.
When brakepoint is set in TS source and debugger started, IE (v11) launches and the breakpoint is hit / execution suspended as expected, BUT:

Instead of opening the TS source file containing the breakpoint, a copy of the source is opened with its tab on the right hand side of the editor tabs bar, and marked with [dynamic]. Editing of the [dynamic] version of the source does not reflect the changes to the real source.

Hovering cursor over variables does NOT display the normal popup/tooltip showing the variable's current value.

Stepping through the [dynamic] version of the source file does work correctly, and 'locals' window does display the local variables correctly, so it seems that Update 2 broke something about how the debugger handles sourcemaps?
This is a multi project solution with about 10 projects, build with browserify. The format of the sourcemap is absolute paths + inlined sources.
The exact same source and sourcemap continues to work correctly when debugging in VS2013 Ultimate with TS 1.8.5.
After detecting this issue I uninstalled VS2015 and did clean install of 'VS2015 with Update 2', but the problem persists. Trying to uninstall Update 2 from VS2015 resulted in VS not even starting, same after running windows recovery to a checkpoint before the evil Update 2.

@paulvanbrenk can you comment on this? Sounds like the inline source related topic we've been discussing internally. I didn't think this changed with Update2 however.

@henrify what kind of project is this exactly, ASP.NET, Cordova, something else? Which version of TypeScript did this work correctly with? And can you share a small sample project that shows the issue?
Honestly I'm surprised this works in VS2013, since we haven't made any changes in the handling of sourcemaps in a while, and definitely don't support inline sources there.

@henrify can you share the project? we would be happy to sign any NDAs to get access to the sources. also feel free to send us directly a sample project the demonstrates the issue on mhegazy at microsoft dot com

I was able to simplify the repro to point where unmodified app.ts straight from "HTML Application with TypeScript" project template brakes the debugger in VS2015.2, but works fine in VS2013.5.
VS2013 debugger probably gets the sources using the absolute source paths from sourcemap, while VS2015 starting from Update 2 either gives priority to the inlined sources, or then fails to resolve the absolute paths and falls back to the inlined sources?
Please find the repro attached.
The source has been simplified to single file, but the build system has been left intact. The relevant browserify code is from line 240 of file gulpcommon.js.
To build:

run 'npm install' on the solution root folder
then 'npm install' in 'some-project' folder
then 'gulp dev-build' in 'some-project' folder
the output bundle will be in 'some-project/build/dev/' folder, and index.html has been already modified to load the bundle from there.

VS2015DebuggerTest.zip

@sheetalkamat can you take a look?

Just small additional note. I build a new Windows 8.1 VM with VS 2015 from scratch, and the bug reproes 100% in the virgin environment.

I am experiencing the same issues after upgrade to VS2015 Update 2. The debugging has broken. I cannot hover over variables that I could hover over before I applied the update this weekend. What's worse is even the watch window is complaining (Screenshot 2). My project is an ASP.NET 5 MVC 6 EF 7 project. The screenshots are from a ASP.NET Class Library project. I get an exception when I set a conditional breakpoint too (Screenshot 1).
Screenshot 1

Screenshot 2

I have just seen reference to a patch for this issue: http://go.microsoft.com/fwlink/?LinkID=785969

@Tamayi this is ASP.net debugging, and is not the Typescript debugger.

@sheetalkamat @mhegazy Continuing on the language theme:
Actually I only assumed that this would be strictly TypeScript related, because I found it hard to believe that Microsoft would have broken JS debugger entirely in general availability release, but I haven't verified that at all.
Just mentioning to make sure that I don't send you off to a wrong path of investigation.

Seeing that this issue still has "Needs more info" tag.. Do you need further additional info from me? Full repro solution is attached, and I wasn't planning to provide any more info, just waiting for your glorious resolution.

@henrify , I cant remove the tag but I have the information I need.
I looked into this and found that there  are two issues going on here.
The source map presented has text for app.ts which starts with BOM. We aren't handling this correctly and use the whole contents as text of the file resulting in debugger thinking the disk file whose text starts with class Greeter but the document that we are trying to load has BOM followed by class Greeeter being differing in contents and hence the dynamic view. I am looking into handling this scenario and will let you know when I complete the changes for the same.
I also looked into issue with hovering over not showing evaluation result and my guess is it might be something in Roslyn language service and I am talking to the team to see what's going on there. I will keep you updated on it as well.

@henrify  Actually looking deeper into the source map with BOM we have come to conclusion that its a bug in build process you have. The source contents field shouldn't be containing BOM since they specify contents of the file and are suppose to be always UTF8 according to sourcemap spec.
Still looking into why you aren't able to see evaluation data tip in the dynamic file.

This is just so horrible end-user experience.
To get basic build and debugging to work, we needed to have over 1000 lines of fragile build scripts, tying together no less than TWENTY ONE gulp plugins, mostly badly documented and buggy as hell, maintained by private people, when they have time.
Then you release Update 2 of Visual Studio 2015. The build / debugging brakes, and now it is us 'having bug in our build system'.
I have no idea what you mean that the 'sourcesContent' shouldn't contain BOM? As far as I can see the 'sourcesContent' property just has the sources as expected, and then we list the source files separately in 'sources'?
I'm not saying that you are wrong or that there isn't some 'bug in our build system', but in practice it is absurdly difficult to get TypeScript to transpile multiproject solution to bundles that can be debugged across different Browsers and IDEs, and you changing Update 2 to be stricter about acceptable sourcemap format made this now even more difficult.
Now we need to waste yet more time finding another fragile combination of sourcemap parameters that works with all browsers and IDEs, until somebody else decides to change something and we get another "bug in our build system".

@henrify The source contents field for the app.ts`` in the sourcemap contains the text has   in the generated map contain the string that starts with BOM character which is seen as below at the start of the source map in notepad++ "ï»¿class Greeter {\r\n    element: HTMLElement;\r\n    span: HTMLElement;\r\n    timer```
It is either the bundler or sourcemap manipulator which consumes the sourcemaps generated by typescript compiler that is causing this.

Thank you for the explanation and your help.
This is a perfect example what I meant when I said that browserify-based build system requires ridiculous amount of plugins, and many of them are buggy us hell, resulting in extremely fragile builds and wasted time. This is about the tenth time that we are experiencing weird issues with browserify plugins.
Browserify based build is clearly not realistic alternative for us, and we'll be replacing it with something else ASAP. Feel free to close this issue.


Cleanup responsible nodes

We are now using storage depth to determine if a node is responsible for storing a chunk.
We should clean up the responsible nodes by removing related code, also the commented-out lines, and removing the config option.

fixed in 9625eeb


Weird error in Linux.

My config is:
lua << EOF local nvimbattery = {   function()     return require("battery").get_status_line()   end } EOF lua << EOF require('lualine').setup {     options = {         theme = "catppuccin",         icons_enabled = true     },     sections = {         lualine_a = {'mode'},         lualine_b = {'branch', 'diff', 'diagnostics'},         lualine_c = {'filename'},         lualine_x = {'encoding', 'fileformat', 'filetype'},         lualine_y = {'location'},         lualine_z = {nvimbattery, 'ctime'}   } } EOF
And I have acpi installed in Linux, but I get this weird error everytime:
`
Error executing vim.schedule lua callback: ...k/.local/share/nvim/plugged/lualine.
nvim/lua/lualine.lua:432: Error executing lua: .../nvim/plugged/lualine.nvim/lua/l
ualine/utils/section.lua:38: attempt to get length of a nil value
stack traceback:
.../nvim/plugged/lualine.nvim/lua/lualine/utils/section.lua:38: in functio
n 'draw_section'
...k/.local/share/nvim/plugged/lualine.nvim/lua/lualine.lua:173: in functi
on 'statusline'
...k/.local/share/nvim/plugged/lualine.nvim/lua/lualine.lua:301: in functi
on <...k/.local/share/nvim/plugged/lualine.nvim/lua/lualine.lua:282>
[C]: in function 'nvim_win_call'
...k/.local/share/nvim/plugged/lualine.nvim/lua/lualine.lua:432: in functi
on 'refresh'
...k/.local/share/nvim/plugged/lualine.nvim/lua/lualine.lua:356: in functi
on <...k/.local/share/nvim/plugged/lualine.nvim/lua/lualine.lua:355>
stack traceback:
[C]: in function 'nvim_win_call'
...k/.local/share/nvim/plugged/lualine.nvim/lua/lualine.lua:432: in functi
on 'refresh'
`
Any ideas about what's happening?

Could you check it if it's a problem with your lua line config or the plugin, by running this command:
:lua vim.print(require("battery").get_status_line())
If all is well you should see the battery status.

Closing as it has been open for 6 months and no further information was provided.


Further refinements for Confluence specific HTML

There are some parts of the HTML that look very different in Confluence.

replace :toc: with
<ac:structured-macro ac:name="toc"/>

replace Note with <ac:structured-macro ac:name="info"><ac:rich-text-body>
${body}
</ac:rich-text-body></ac:structured-macro>
replace  with <ac:structured-macro ac:name="code"><ac:plain-text-body><![CDATA[${body}]]></ac:plain-text-body></ac:structured-macro>

Feedback welcome

some problems with :toc: ...

... asciidoc currently renders the :toc: in the preamble section which is currently not posted to confluence... but this could be fixed
afaik, the toc macro only renders the toc for one page - so in only makes sense if confluenceCreateSubpages = false, but it doesn't harm for subpages since it just displays nothing in this case... . So it wouldn't be a replacement, but an insertion for each page, right?
for confluenceCreateSubpages = true, the script already adds the children macro to the end of each page.

=> I will now add the toc macro to the start of each page

note works fine. Also added special handling for the arc42help sections.
How can we render the other admonitions like warn?

To be honest, I guess we have 2 options here:

We go forward with the current approach (modify generated HTML so it fits Confluence) and are therefore able to handle other input than asciidoc as parsing and conversion can be extracted into a separate Groovy file (parseBody() function) or
we take asciidoc input files and use asciidoctor (e.g. the Gradle or Maven plugin) with a Confluence backend that we will have to write - based on the existing HTML5 backend

Personally I'd vote for option 2 because I love asciidoc, but it's your choice and I know some colleagues who'd love to see option 1 and Markdown support.

option 1 is IMHO currently the easier, option 2 the cleaner and better way.
I don't mind to drop my code/project for a cleaner working solution. Until then, I guess it makes sense to refine option 1.
Can you give me more details about "I know some colleagues who'd love to see option 1 and Markdown support" - maybe in another issue? The arc42-template project already contains code for converting asciidoc output to markdown via pandoc, so this might be a simple task.

I guess we should try merge https://github.com/gscheibel/asciidoctor-confluence and our project into one...

As I said in the comment above, IMO this project has a different scope than gscheibel's version - and I personally like it. So, I'm definitely a bit biased when I say, I'd like to keep it as it is or move it into the direction of variant 1 mentioned above. The point is that the script is named asciidoc2confluence though it actually takes "Asciidoctor created HTML" as an input. An alternative input could be Markdown generated HTML, I'd say.

OK. I do agree.
Alternative input sounds good, but currently I want to get this script "feature complete". This mainly includes pushing images to confluence.
Regarding the name - we could add the the asciidoctor conversion or rename it to "asciidocHtml2confluence" for the time beeing. But for me, that's not too important. For me, it is more important to clean up the interface a bit and maybe create an artifact which could be pushed to a maven repository for ease of use...

currently I want to get this script "feature complete"

Couldn't agree more. Let's focus on #2, #7 and #6 first and bring out a release that can be used with Maven and gradle. That'll already be a huge next step, I'd say. I'd volunteer to take over #6, would that help you?

#6 would be very helpful since I've no experience with it...
I am already working on #2 .
Thanx!


new binary from bk7231tools read_flash: Globe-Electric_37783-RGBCWWW-A19-Smart-LED

Globe-Electric_37783-RGBCWWW-A19-Smart-LED.zip
The included ZIP file contains the 2MB binary Flash dump using the bk7231tools and a FTDI USB cable.  The dumped device was straight from the Globe packaging (from Costco, Canada) to the workbench, so it has never been set up with an AP and the Tuya Smart app.
However, I did first verify that it was exploitable using the LightLeak AP and the Android Cloudcutter app, though when it got to the download flash screen, the error message was "couldn't receive packets from the device".
The firmware version reported by Tuya Smart on other identical bulbs from this same package is v2.0.3, but I can't be certain these ones had not had firmware updates applied at some point.
I attempted to use the build_profile.py in several passes but it was only able to retrieve bootloader and application binaries. No JSON output was generated. In the second pass it reported:
[+] Matched pattern for BK7231T version SDK 2.0.0 8710_2M, payload type datagram
And haxomatic failed with:
[!] Failed to find datagram payload address (found 2, expected 3)
Edit: This lightbulb uses a WB3L module.

So this is an interesting one.
I can confirm that the dump you provided is version 2.0.0 and there is an update available to 2.0.3
You received an error from haxomatic because this build has an older baseline version than the versions supported in haxomatic.  I'll look to see if I can find the haxomatic offsets for this baseline or reach out for help if needed, but that may take some time.
Additionally, using the 2.0.0 firmware, I cannot get this device to connect to my network in any way, it continually fails with Tuya giving the message "net work unavailable" over and over.  I tried with both the Globe Suite app as well as Smart Life, both failed the same (though Global Suite wouldn't even let me attempt to add via slow blink AP mode, it would crash).
I can confirm that the 2.0.3 firmware is still exploitable, and if you can update your devices to that, go ahead.  I will post a 2.0.3 profile shortly.

A profile for Globe Electric 37783 RGBCT Bulb v2.0.3 has been added, I'll continue to look into the v2.0.0

A profile for Globe Electric 37783 RGBCT Bulb v2.0.0 has been added.  Haxomatic has been updated to work with Baseline 30.04 as well.
Even with cutting the 2.0.0 firmware will not connect to my network, not sure what's up with that.  2.0.3 seems to connect fine, so 2.0.0 may just be a buggy release.  Either way, it will 3rd party flash now with CloudCutter.

This may not be the best spot to ask but I've done some searching and haven't found it.
Wondering if either of you have a LibreTuya config for this bulb? The ESPHome config uses the esp8266_pwm platform which I assume doesn't directly convert.

https://github.com/tuya-cloudcutter/tuya-cloudcutter.github.io/blob/a877e69c8f3829be545e9a5a9d76cab9d5fd7fd2/devices/globe-electric-37783-rgbct-bulb-v2.0.3.json#L109
Looks like it's probably SM2135 LED driver, you'll need to add external component with ESPHome PR #3850
external_components:
  - source: github://pr#3850
    components: [ sm2135 ]
    refresh: 10 min

sm2135:
  data_pin: P26
  clock_pin: P8
  rgb_current: 20mA
  cw_current: 50mA

output:
  - platform: sm2135
    id: output_red
    channel: 2
  - platform: sm2135
    id: output_green
    channel: 1
  - platform: sm2135
    id: output_blue
    channel: 0
  - platform: sm2135
    id: output_coldwhite
    channel: 3
  - platform: sm2135
    id: output_warmwhite
    channel: 4

light:
  - platform: rgbww
    name: "Light"
    red: output_red
    green: output_green
    blue: output_blue
    cold_white: output_coldwhite
    warm_white: output_warmwhite
    cold_white_color_temperature: 6536 K
    warm_white_color_temperature: 2000 K
    color_interlock: true

White channels may be mixed up, just switch channels 3/4 if so.

White channels were good, blue and green were reversed.
I also found when power was restored they booted to red by default so I added a on_turn_on command to force them into white. Here's what I ended up with for future searchers.
Any idea if this would work with the globe-electric BR30 bulbs as well? I can't see the internals being much different than the A19 bulbs.
external_components:
  - source: github://pr#3850
    components: [ sm2135 ]
    refresh: 10 min

sm2135:
  data_pin: P26
  clock_pin: P8
  rgb_current: 20mA
  cw_current: 50mA

output:
  - platform: sm2135
    id: output_red
    channel: 2
  - platform: sm2135
    id: output_green
    channel: 0
  - platform: sm2135
    id: output_blue
    channel: 1
  - platform: sm2135
    id: output_coldwhite
    channel: 3
  - platform: sm2135
    id: output_warmwhite
    channel: 4

light:
  - platform: rgbww
    name: "Light"
    id: globelight1
    red: output_red
    green: output_green
    blue: output_blue
    cold_white: output_coldwhite
    warm_white: output_warmwhite
    cold_white_color_temperature: 6536 K
    warm_white_color_temperature: 2000 K
    color_interlock: true
    restore_mode: RESTORE_DEFAULT_OFF
    on_turn_on:
      light.control:
        id: globelight1
        state: on
        color_mode: COLD_WARM_WHITE

Oh right, I forgot the channel orders on the SM2135 driver are out of order, so yeah, you just have to change channels until it works.
As for the on color, that's most likely due to the last saved preference.  If you changed it to your preferred color, then turned it off for 10 minutes, it would re-save the preference.  But the on_turn_on also works fine.
As for the BR30s, best answer I can give is maybe.  Depends on which firmware they come with.  Also, most BR30 bulbs I've seen have been PWM.


Missing semicolon after MODEL statement in Table Migration docs

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks!


selfhost: Implement generic inner types for namespaced types

Please don't delete your branch, I'm going to rebase manually later.


chore: update readme text

:tada: This PR is included in version 1.2.27 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Missing Permissions - Handling Failure

Doing some testing with some of the modules, i started to test how they behave when the API permissions are not present and at present it's not really consistent.
For example, the base module will successfully return with the RawEntity data only.... we discussed this behavior in the past in the context of an unresolved entity (404 type error), but in the context of a 401/403 error I think it makes more sense to have the module return a failure back to the connector.
Similarly other modules have different behaviours, OOF still works and returns an unknown state, which I think is right again in the case of 404 or other unknown error, but in a 401/403 where it has no chance of succeeding I think we should just return an error.
Other modules just outright fail but return nothing to the connector, so it retires and times out.  Related alerts for example tries the HTTP call to the log analytics API, hits a 403 and then the module stops with no response
My thoughts are if we hit a 401/403 on a critical API call, then we consistently return an error regardless of a possible ability to proceed.  If the API call is less critical then perhaps we can continue...  Something simple like:
{
    "Error": "Module does not have sufficient permissions, please run the GrantPermissions.ps1 script"
}

Should we check if permissions are set or handle error management in the code?
Might be easier to add a step like we do to check if the right type of entities are present? Like check permissions and Terminate if that's not there? Or should we do terminate at the actual call? Also, should "Error" me a property we always return even when there is a success? Or maybe add a "Status" property woith either Success, Error or maybe Warning. Although I guess it would be easier to stay binary...

I'd lean towards doing it the API call because we could handle additional failure scenarios there.  For example in the KQL module, a ln incorrectly formatted KQL query.
Return schema definitely needs some more thought, we could return an error specific to STAT and the raw error from the API call for additional detail
Interesting idea to add this as a success when no error.

Perhaps the errors should only be handled by the custom connector either in the connector reading the error code returned by the module or the dispatcher? We can't have the end-user check if there was an error level returned. If anything else than a success is returned by any modules down the line, the connector should be ❌. This can also allow a complex error coding at the internal level, but it should necessarly fail for the end user.

I agree but to do that we'll need the modules to pass the 'why' back to the dispatcher so that it is surfaced in the connector.  Otherwise the connector will fail with a useless error like some timeout or similar that isn't as helpful as it could be in diagnosing the issue.  If a critical failure agreed with need a :x: status in the connector

Thinking of a return along these lines... I think we should probably come up with more intuitive property names but as a structure it gives us something to start with.  Perhaps we should also include properties for the playbook name and run id to make it easier to locate to troubleshoot.

Here's a sample of what the would look like with the playbook id, name and run id included
{
    "kind": "Http",
    "inputs": {
        "statusCode": "@outputs('HTTP')['statusCode']",
        "body": {
            "Error": "Watchlist module failed to execute with status @{outputs('HTTP')['statusCode']}",
            "PlaybookName": "@{workflow()?['name']}",
            "PlaybookResourceId": "@{workflow()?['id']}",
            "PlaybookRunId": "@{workflow()?['run']?['name']}",
            "SourceError": "@body('HTTP')"
        }
    }
}

Would "SourceError": "@body('HTTP')['error']" be a better content for SourceError by the way?

Yes, looking back at the modules I've tested so far that seems to be consistent and would be better.  Shall we make it "SourceError": "@body('HTTP')?['error']" just be be safe in the event in some corner case error isn't present?

Looks like we're done here 😄


Added almost all the particles for the druid race.

Video for all the particles made: http://youtu.be/aWXHY80o8PM?hd=1

Shapeshifter wasn't in the video, which passive icon was it? Also the arctic freeze hotkey is working fine, Alex just doesn't have a hotkey set for that ability, thus none shows.

Runemaster's third ability (first passive) then, the crit one

Yea, that's because of the 7.00 lvlup UI. It is actually supposed to have the hotkey there, the other passive is the one with the problem, however this is also an effect of Alex not having a hotkey set, thus no problem

if it was the lvlup ui, it would say ctrl e, but it just says e, and the other passive is fine (both level 1 and can be levelled more)

Teve:
Unleveled: http://i.imgur.com/3dSGs8X.png
Level 1: http://i.imgur.com/UHLXMsl.png
Unlevelable: http://i.imgur.com/S1MYpCw.png
Dota:
Unleveled: http://i.imgur.com/jgNdnue.png
Level 1: http://i.imgur.com/oMI91hJ.png
Unlevelable: http://i.imgur.com/8y5XKMx.png
Seems right on my end atleast

http://youtu.be/csWvgGmViRk?hd=1 Feral rage particle and armageddon burnfire particle

https://www.youtube.com/watch?v=_Jz00sm5lhg Shaman Lightning Fury particle

http://youtu.be/pJpwOk0u1I8?hd=1 Arctic Freeze Particle


It looks like you are trying to open a liberty gate library file as a netlist:

It looks like you are trying to open a liberty gate library file as a netlist:
[01.12.2021 20:37:30] [netlist_parser] [error] [/mnt/ramdisk/hal/src/netlist/netlist_parser/netlist_parser_manager.cpp:34] no hdl parser registered for file type '.lib'
Please try again with a Verilog or VHDL netlist synthesized for the SKY130 PDK. HAL will automatically select the appropriate gate library if it is placed in the correct folder (place it in hal/plugins/gate_libraries/definitions before building  HAL or hal/build/share/hal/gate_libraries afterwards). We're also currently working on changes to the handling of gate libraries when loading a new netlist file, which should clear things up in the future and hopefully prevent such mistakes :)
Originally posted by @SJulianS in https://github.com/emsec/hal/issues/441#issuecomment-985999784

I'm trying to load the sky130 pdk liberty file just like suzizecat but the procedure you've described doesn't work for me.  I've copied sky130_fd_sc_hd__tt_025C_1v80.lib into hal/build/share/hal/gate_libraries/ and can see this file in Gate Library Manager but when I open a netlitst called heartbeat compiled from this library, HAL gives me an error: Unable to find a compatible gate library. Deserialization failed!
heartbeat_netlist.txt


Output stderr, stdout and cmd line for projectExec failures

When cycleFinderTask or translateTask fails with the command line call. The internal error is obscured, making it harder to debug. The output should be captured and then output as part of the thrown exception. It should also show the full command line and perhaps the suggestion of trying to run it with javac to test that it works correctly. This is a lesson from issue #261 by @confile.
Currently a user will have to enable --debug mode and then dig through the debug output to see what command is run and then try debugging it.
Example of the current output which doesn't show any helpful messages:
:j2objcTranslate FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':j2objcTranslate'.
> Process 'command '/Applications/J2Objc/j2objc-0.9.7b/j2objc'' finished with non-zero exit value 1

* Try:
Run with --info or --debug option to get more log output.

This is a great idea!

I've been testing this by adding --nonsense flags to each of the tasks. My feeling is that this is going to be a great change for tracking down tricky build issues.
Previously it would say:
Process 'command '/Users/brunobowden/dev/j2objc-versions/j2objc-0.9.7/j2objc'' finished with non-zero exit value 1

Now it produces some very helpful error messages as follows:
...
:base:j2objcCycleFinder UP-TO-DATE
:base:j2objcTranslate
Standard Output:

Error Output:
j2objc: invalid flag: --nonsense
Usage: j2objc <options> <source files>
use --help for a list of possible options

:base:j2objcTranslate FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':base:j2objcTranslate'.
> Error Output:
  j2objc: invalid flag: --nonsense
  Usage: j2objc <options> <source files>
  use --help for a list of possible options

  Command Line:
  /Users/brunobowden/dev/j2objc-versions/j2objc-<IP_ADDRESS>/j2objc -d ...
  Caused by:
  org.gradle.process.internal.ExecException: Process 'command ...

@advayDev1 - see example above for how the error output has changed. This is going to be a great help for tricky issues.

@brunobowden - totally agree.  waiting for you to merge it in :)


which method provide Youtube Data Api v3 key and we see black screen with audio only. not any buttons.

Bug Report
we are not able to play youtube video just we are hearing the audio only and see the blackscreen not even any controls of youtube player. as well as there is i review your code but We could not see where to set Youtube Data Api key from google server or not mention in document. kindly please update method as well as screen shot of where to set.
Description of the Bug

Environment details

Android Version:
API Version: 30 to 34
Tested devices:

Youtube Player Library Version:
Steps to reproduce the bug

name: Bug report
about: Use this template for reporting bugs
labels: bug

Bug Report
Description of the Bug

Environment details

Android Version:
API Version:  30 t0 34
Tested devices:

Youtube Player Library Version:
Steps to reproduce the bug

Expected behavior

Actual behavior

Additional information
<!-- Provide here further information that might help understand the issue or reproduce the bug, e.g.
- standalone code snippets of implementation that can copy-pasted and work without any missing classes
- screenshot(s) of visualising the bug
- error logs
- any useful background infromation

The YouTube Data API is not required for this library.
Are you seeing the black screen on an emulator or real device?

i also same issue .. you added this?
@Override
public void onDestroy() {
    super.onDestroy();
    youTubePlayerView.release();
}

@Override
public void onDestroy() {
super.onDestroy();
youTubePlayerView.release();
}
yes i added this and i am also see the black screen  i have test on real device real me pro 6 5g as well as emulator both getting same result of output.

Does the black screen happens when you enter fullscreen?

if i go to youtube player activity its working fine
come back and go to any other activity and go back to youtube player activity its black screen..

mmm are you able to replicate this in the sample app? if not, the problem is probably in your code.

mmm are you able to replicate this in the sample app? if not, the problem is probably in your code.

Thank you finally i found the issue .. Problem is i also using another webview library .. two webview library causing this issue

Thanks for sharing! can I ask what is the other webview library you're using?

implementation 'com.github.delight-im:Android-AdvancedWebView:v3.0.0'

after i didsbale mWebView.onResume(); .. its working fine no more black screen
   @SuppressLint("NewApi")
@Override
protected void onResume() {
    super.onResume();
   // mWebView.onResume();
}

yes  I am just using your library  implementation 'com.pierfrancescosoffritti.androidyoutubeplayer:core:12.1.0'


Content is not mandatory

FIxes #435

Hello @adamreisnz,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX

Is that an auto reply whenever a PR gets merged? 🤔

Indeed. I need to make a better one for those that are as prolific as you :)

😆


[PR#284][FOLLOWUP] Fix race condition

   ❨?❩

Why are the changes needed?

Fix the problem if some thread overwrite the same file.
Test Plan:

Add some test cases that check the changes thoroughly including negative and positive cases if possible
Add screenshots for manual tests if appropriate
Run test locally before make a pull request

Please follow the PR template to add
fixes #289
fixes #284

in the PR description
the help the maintainer automatically link and close related PRs and Issues

Please follow the PR template to add
fixes #289
fixes #284

in the PR description
the help the maintainer automatically link and close related PRs and Issues

thanks, merged to master for v1.1.0

thanks, merged to master for v1.1.0


PEAR-1963: cDAVE - Search input should remain fixed and not scroll

Description

Style Changes
Code Clean Up

@wteouchicago please verify the overall behavior of CDave specially the fields panel on the left. Thank you 🙇♂
Checklist

[ ] Added proper unit tests
[ ] Left proper TODO messages for any remaining tasks
[ ] Scanned for web accessibility with aXe, and mitigated or documented
flagged issues

Screenshots/Screen Recordings (if Appropriate)
https://github.com/NCI-GDC/gdc-frontend-framework/assets/101295912/f3cad20e-e66e-4367-af7b-d7d116e02cc2

The scroll behaviour looks right to me -- cemile would be the best judge and we can have her look after merge. I also sanity-checked cDAVE in general, but not every nook and cranny of functionality. Let me know if there's something I should look out for.
One thing -- do you think we need some padding on the right side of the search box? so that it's rightmost edge is aligned with the rightmost edge of the blue section headers (e.g. Demographic)?

Agree with @wteouchicago to add right padding to the search input for better alignment with the facet header's right section.
Some issues with the less button:

The size of the + button is now different than the - button:

Clicking on the less button (the minus icon) does not close the expanded list. Clicking on the "show less" text does work  as before

Good call. I fixed both the issues and fixed a failing unit test.

The scroll behaviour looks right to me -- cemile would be the best judge and we can have her look after merge. I also sanity-checked cDAVE in general, but not every nook and cranny of functionality. Let me know if there's something I should look out for.
One thing -- do you think we need some padding on the right side of the search box? so that it's rightmost edge is aligned with the rightmost edge of the blue section headers (e.g. Demographic)?

I updated the styling.

Items 1 and 2 are addressed.  Everything else looks fine.


fix wrong link.

fixes #954  The link to Arc in v1.9.0 was also wrong, so I fixed that as well.

Thanks for the response!
I'm new to Github, so sorry if I'm wrong.
Prior to v1.10.0, there are typos in the links in the documentation. So if you want to fix the wrong links in earlier versions, I feel you need to replace the tags.


Siglent: Using SDS1104X-E through usbtmc not always work

As discussed here (https://twitter.com/azonenberg/status/1544476705842049024) using a SDS1104X-E through usbtmc mostly dont work (glscope client correctly detects, and sometimes the trace appears on it).
So I made some usb captures, logging and everything to try to help debugging the issue. Funny enough, through ethernet everything seens to work fine (I have some issues setting up the triggers correctly, but I'm not sure is a communication issue). I always though it might be a linux usbtmc driver issue since sigrok sort of works correctly, but it does by using libusb to connecting directly to the oscilloscope instead using usbtmc.
Here are some logs from initialization. The traces do appear once in the glscopeclient, but then everything stops working and I need to remove the usb cable and put again so I can get the trace again (just restarting glscopeclient does not help)
usbcapture_filtered.pcapng.gz
dmesg.log
sds1104x-e.log
I'm currently on x86-64 ubuntu 22.04 (kernel 5.15.0). Once I managed to completely freeze the osciloscope trying to capture from glscopeclient (I had to hardreset the osciloscope to get back), but I really dont remember what I did to cause that.
My oscilloscope is a Siglent SDS1104X-E key-upgraded to SDS1204X-E running latest firmware (<IP_ADDRESS>.37R9)
Might be related #214

Hello racerxdl,
i did some debugging today. It looks like a  firmware bug. The maximum request size is 48 byte.
I am running the latest firmware <IP_ADDRESS>.37R9 on
5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Please take a look at siglent.patch for SCPITMCTransport.cpp
do
{
  // workaround for Siglent SDS1x04X-E   max request size is 48 ?
  // Bug in firmware <IP_ADDRESS>.37R9 ?
  bytes_requested = 48 ;
  bytes_fetched = read(m_handle, (char *)m_staging_buf + i, 48);
  i += bytes_fetched;
} while(bytes_fetched == bytes_requested);

siglent.patch.txt

modinfo usbtmc
filename:       /lib/modules/5.15.0-56-generic/kernel/drivers/usb/class/usbtmc.ko
license:        GPL
srcversion:     A55300AFA898251D26323BB
alias:          usb:vpddcdscdpicFEisc03ip01in*
alias:          usb:vpddcdscdpicFEisc03ip00in*
depends:
retpoline:      Y
intree:         Y
name:           usbtmc
vermagic:       5.15.0-56-generic SMP mod_unload modversions

Do some debugging
Unload the usbtmc  module
rmmod usbtmc
Load module with debug enable
insmod usbtmc.ko dyndpg=+p
Run
glscopeclient --debug --trace SCPITMCTransport
dmesg

Interesting but not surprising. This is something we should probably add as an additional argument to the usbtmc driver (after the /dev path) since enabling the workaround all the time will have serious performance impacts for non-buggy instruments.

Hello Andrew,
now we can configure the transfer size.
for example: opening /dev/ubtmc0 with transfer size 48
/dev/usbtmc0:48
or
glscopeclient myscope:siglent:usbtmc:/dev/usbtmc0:48

Merged the fix to scopehal. Ready to close once @racerxdl confirms the patch fixes it.

Hi @mandl / @azonenberg with that with the scopehal fix and opening with the :48 option it does work without any issues.


arch-install-scripts: 27 -> 28

Description of changes
https://github.com/archlinux/arch-install-scripts/compare/v27...v28

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 202053 run on x86_64-linux 1

1 package built:

arch-install-scripts


Support Table Renaming on Upload

Right now the file name is used by default when a NEW(!) table is uploaded.
Provide the option to rename the table on upload.

I've added validators for the "Game Name" and "Game Filename" in the "Table Data" dialog with version 2.11.2.
Additionally, there are now hints describing the effect when you change critical fields, like the filename or the game name.
Because there is a lot attached to it, I keep the actual table renmaining separated from the upload for now.


Segmentation fault in Assistant initialization on RPi 4

As a recent buyer of the new Raspberry Pi 4 I've been eager to try out some of my software on a more powerful machine, but I've so far bumped into a systematic segmentation fault when initializing the assistant that doesn't occur on other machines - neither on the previous RPi3 that had exactly the same hardware connected, nor on other Pis or on my laptop.
Code to replicate the issue:
import json
import google.oauth2.credentials

from google.assistant.library import Assistant

credentials_file = '/home/pi/.config/google-oauthlib-tool/credentials.json'
device_model_id = 'My Device'

with open(credentials_file, 'r') as f:
    credentials = google.oauth2.credentials.Credentials(token=None, **json.load(f))

with Assistant(credentials, device_model_id) as assistant:
    for event in assistant.start():
        print(event)

with credentials.json containing something like:
{"token_uri": "https://accounts.google.com/o/oauth2/token", "scopes": ["https://www.googleapis.com/auth/assistant-sdk-prototype"], "client_id": "****",         "refresh_token": "****", "client_secret": "****"}

What I see on other machines:
ON_MUTED_CHANGED:
  {"is_muted": false}
ON_MEDIA_STATE_IDLE
ON_START_FINISHED
...

What happens on the RPi 4: segmentation fault.
Stack trace:
(gdb) bt
#0  0xb6f831dc in strlen () from /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so
#1  0xb4facb10 in ?? () from /usr/local/lib/python3.7/dist-packages/google/assistant/library/libassistant_embedder.so
#2  0xb4fa9c8a in assistant_new () from /usr/local/lib/python3.7/dist-packages/google/assistant/library/libassistant_embedder.so
#3  0xb600acc0 in ffi_call_VFP () from /usr/lib/arm-linux-gnueabihf/libffi.so.6
#4  0xb600b6cc in ffi_call () from /usr/lib/arm-linux-gnueabihf/libffi.so.6
#5  0xb6044a38 in _ctypes_callproc () from /usr/lib/python3.7/lib-dynload/_ctypes.cpython-37m-arm-linux-gnueabihf.so

My educated guess is that at some point strlen() gets a NULL or invalid pointer and crashes, but that ?? () frame in libassistant_embedded.so won't allow me to see where exactly things are going wrong.
NOTE: the segmentation fault also occurs when using google-assistant-demo:
$ google-assistant-demo --device-model-id Device
[1]    17095 segmentation fault (core dumped)

I'm using the stock Raspbian Buster, the assistant library and sdk (with samples) have been installed via pip, the machine is set up with a HiFi Berry soundcard for playback and a USB microphone for input (both used to work well with the assistant on the previous RPi 3 and Asus Tinker already) and the following ~/.asoundrc:
pcm.!default {
  type asym
   playback.pcm {
     type plug
     slave.pcm "hw:0,0"
   }
   capture.pcm {
     type plug
     slave.pcm "hw:1,0"
   }
}

Has the assistant SDK been tested on the new RPi 4 already? Are there any changes required to make it work or any hint on how to better investigate this issue?

Other users have reported similar issues on the RPi4.
I've tried more code from the samples to pinpoint the issue:

google-assistant-demo -> segmentation fault
googlesamples-assistant-audiotest -> segmentation fault
googlesamples-assistant-audiotest -> works fine
googlesamples-assistant-pushtotalk -> works fine

My suspect is that the broken code lies in the hotword detection, as both the audio test and push-to-talk work fine.
I know that the library has been compiled for armv7l, but armv7l is a quite big family itself, and the RPi4 sports a newer A72 CPU. Could it be that the libassistant_*.so need a recompile for the new processor?

The Google Assistant Library, which includes the libassistant_*.so and the hotword detection, has been deprecated.

Hi @Fleker, I think that I might have missed the deprecation notice then :)

Is the Google Assistant Service the only supported way to build assistant interactions from now on? (Meaning, should I expect the push-to-talk to break as well in the near future?) If so, is the new service going to provide hotword detection as well, or we developers have to rely on other hotword detection mechanisms?

Where can I find a simple working example in Python with the new supported logic, like the one I've posted in my first comment? If creating the Assistant object itself segfaults then I'm not sure how the new syntax should look like.

Where can I find the deprecation notice for the assistant library, and when was it deprecated? We may agree that building software for production uses and finding out that a library is deprecated only when you try to deploy your software on a new device isn't really the smoothest developer experience.

I've opened a new issue to discuss the assistant library deprecation policy and the provided alternatives. Closing this one.


When is it planned to make a new version of the NuGet packages?

@oysteinkrog: The latest SQLite.NET-PCL package release was on last November. Is there any current plan as for when the new release would happen? I am especially interested in WinSQLite3 support in SQLite.Net.Platform.WinRT. Thanks

I confirm. There are some important fixes confirming queries with special characters which I'm interested in. The Nuget version is unusable for my specific case. The latest code on Github works like a charm.

It seems that this fork is not active anymore.


resizable_layout not work as expect

When I set the windows effect to "Don't show window contents when dragged", the variable layout didn't work as expected

`use winsafe::gui;
use winsafe::prelude::*;
fn main() {
let window = gui::WindowMain::new_dlg(108, Some(128), None);
let notresize = (gui::Horz::None,gui::Vert::None);
let dsd = gui::Edit::new_dlg(&window, 1000, notresize);
let btn = gui::Button::new_dlg(&window, 1002, (gui::Horz::Resize,gui::Vert::Resize));
let tab = gui::ListView::new_dlg(&window, 1003, (gui::Horz::Repos,gui::Vert::Repos), Some(winsafe::HMENU::CreatePopupMenu().unwrap()));
window.run_main(None);

}`

dataview.zip

Try this:
fn main() {
	let window = gui::WindowMain::new_dlg(108, Some(128), None);

	use gui::{Horz as H, Vert as V};
	let dsd = gui::Edit::new_dlg(&window, 1000, (H::Resize, V::Repos));
	let btn = gui::Button::new_dlg(&window, 1002, (H::None, V::Repos));
	let tab = gui::ListView::new_dlg(&window, 1003, (H::Resize, V::Resize),
		Some(winsafe::HMENU::CreatePopupMenu().unwrap()));

	window.run_main(None);
}

There is a label which is not being handled (ID is 65535). In order to adjust it to the layout, you'll have to give it an ID and manage it through a Label.

I'll try to reproduce this here. Is this a system option? Where do I find it?

Perhaps you can search "adjust the appearance and performance of Windows" in Settings.
But I found the path of the program as follows:
"C:\Windows\System32\SystemPropertiesPerformance.exe"

There was a very specific case where the LayoutArranger didn't fire on the 1st WM_SIZE call. Since hide contents while dragging only fires 1 event, the controls didn't resize at the first move.
Let me know if this fixes your problem.

Thanks,it's works pretty well!


[Nuxt Bridge] [vite]: Rollup failed to resolve import

Version
@nuxtjs/i18n: 7.2.1
nuxt: 2.15.8
Nuxt configuration

[ ] Applies to a site deployed to a static server (site generated with nuxt generate)
[X] Applies to a site deployed to a server with a Node backend

@nuxtjs/i18n configuration
{
  i18n: {
    defaultLocale: 'nl',
    detectBrowserLanguage: false,
    parsePages: true,
    locales: [
      { code: 'nl', name: 'Nederlands', file: 'nl.json' },
      { code: 'en', name: 'Engels', file: 'en.json' },
    ],
    vueI18n: {
      fallbackLocale: 'nl',
    },
    vueI18nLoader: true,
    lazy: true,
    langDir: 'translations/',
  },
}

Hi!
I'm trying to see If I can migrate to Nuxt Bridge. Upon build, I get an error that the import nuxti18n middleware is failed to resolve. I have no middleware related to or named nuxti18n, so I guess its related to this module.
I'm not sure if this is a bug in this module which surfaces with Nuxt Bridge, or if this is a bug in Nuxt Bridge itself.
 Building client...
 ERROR  [vite]: Rollup failed to resolve import "/home/node/app/middleware/nuxti18n" from ".nuxt/middleware.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
 ERROR  [vite]: Rollup failed to resolve import "/home/node/app/middleware/nuxti18n" from ".nuxt/middleware.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
  This is most likely unintended because it can break your application at runtime.
  If you do want to externalize this module explicitly add it to
  `build.rollupOptions.external`
  at onRollupWarning (node_modules/vite/dist/node/chunks/dep-27bc1ab8.js:39256:19)
  at onwarn (node_modules/vite/dist/node/chunks/dep-27bc1ab8.js:39072:13)
  at Object.onwarn (node_modules/rollup/dist/shared/rollup.js:23173:13)
  at ModuleLoader.handleResolveId (node_modules/rollup/dist/shared/rollup.js:22463:26)
  at node_modules/rollup/dist/shared/rollup.js:22424:26

Hello,
The current stable version isn't compatible with the bridge. You need to wait until the next branch will be ready.
Thanks!

See https://github.com/nuxt-community/i18n-module/issues/1410


Add size and dictionary check in Control::_edit_set_state() to fix crash

fixes #46017
add size checks and dictionary element checks to prevent crash when executing Control.new()._edit_set_state({})
This is a new PR in-place of #46620 based on suggested changes.

Thanks!

Cherry-picked for 3.2.4.


qa: [MyCollections] 1st round QA pass

The type of this PR is: Enhancement

This PR addresses most of https://artsyproduct.atlassian.net/browse/CX-655
Description
This PR goes through the list in the JIRA ticket above and does a first round QA pass.
Still need to do some design and polish, as well error handling in follow-up.
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a CHANGELOG.yml entry or my changes do not require one.

#trivial

Nothing too controversial in here so ggoing to MOG this so that we can get stuff out for QA in the beta tonight.
#mergeOnGreen


Agent is getting slower when calling handle_message many times

Rasa Core version:
0.8.6
Python version:
3.6.4
Operating system (windows, osx, ...):
windows 10
Issue:
I modified the run.py file in concert bot example as below.
def run_concerts(serve_forever=True):
    agent = Agent.load("models/dialogue",
                       interpreter=RegexInterpreter())
    from datetime import datetime
    for i in range(200):
        t = datetime.now()
        agent.handle_message("/greet")
        print(datetime.now() - t)

The run time of agent.handle_message is increasing overall (from about 0.005s to 0.02s for me). To verify the accuracy of a policy, one may need to call agent.handle_message massively for different intent sequence combinations.
Is there any way to keep the agent to react fast when calling handle_message many times?
My current solution is to reload the agent for every several calls.
Content of domain file (if used & relevant):

I mean it is probably taking longer because the dialogue gets longer and longer and between calls to handle_message it needs to be serialised and deserialised. So you could use different session ids if you don't care that each message will be its own dialogue (but I guess thats fine).


Sync DTDL files from DTDL repo main branch -- Remove all solecism test cases (#154)

This change removes all solecism tests that are imported from the DTDL repo.  These will be replaced by solecism tests that live in the DTDLParser repo, which is a more appropriate location because tolerance of solecisms is a parser quirk, not a DTDL language feature.

This change relates to bug https://github.com/digitaltwinconsortium/DTDLParser/issues/103 but does not fix it.  The fix will be in an upcoming PR.

Copied these changes into #104, so no need for this separate PR.


Problem is resolved

Challenge Chaining If Else Statements has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
the problem is resolved
My code:
removed solution by mod

Just to make sure: did you solve the issue?

@wilfredinni, do not use the issue for show your solution code.
These GitHub Issues are for reporting bugs on the freeCodeCamp website only.
Happy coding.

@dhcodes Oh, odd. I did close this. but thank you!


[Bug]: Eufy S120 Solar Wall Cam Support

What happened?
I am writing since it seems the new Dufy S120 is not supported, do you have this on your radar for support going forward?  If so is there an ETA?
 There were 0 instance(s) using the livestream until now.
[09/01/2023 20:29:40]   [EufySecurity-2.2.6]    DEBUG   [LocalLivestreamManager.ts:233] Side Fence Left Start new station livestream (P2P Session)...
[9/1/2023, 4:29:40 PM] NotSupportedError: This functionality is not implemented or supported by this device
    at EufySecurity.startStationLivestream (/usr/lib/node_modules/homebridge-eufy-security/node_modules/eufy-security-client/src/eufysecurity.ts:834:19)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
[9/1/2023, 4:29:40 PM] Got SIGTERM, shutting down Homebridge...
[9/1/2023, 4:29:40 PM] [Harmony Hub] INFO - shutdown
[09/01/2023 20:29:40]   [EufySecurity-2.2.6]    DEBUG   [platform.ts:212]       Push Closed!
[09/01/2023 20:29:40]   [EufySecurity-2.2.6]    DEBUG   [platform.ts:218]       Closed!
[09/01/2023 20:29:40]   [EufySecurity-2.2.6]    INFO    [platform.ts:394]       Finished shutdown!
[09/01/2023 20:29:40]   [EufySecurity-2.2.6]    DEBUG   [LocalLivestreamManager.ts:283] Side Fence Left Stopping station livestream.
[9/1/2023, 4:29:40 PM] NotSupportedError: This functionality is not implemented or supported by this device
    at EufySecurity.stopStationLivestream (/usr/lib/node_modules/homebridge-eufy-security/node_modules/eufy-security-client/src/eufysecurity.ts:882:19)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

config
{
            "enableDetailedLogging": true,
            "enableCamera": false,
            "CameraMaxLivestreamDuration": 30,
            "pollingIntervalMinutes": 10,
            "hkHome": 1,
            "hkAway": 0,
            "hkNight": 3,
            "hkOff": 63,
            "ignoreStations": [],
            "ignoreDevices": [],
            "country": "US",
            "ffmpegdebug": false,
            "cameras": [
                {
                    "serialNumber": "************",
                    "rtsp": false,
                    "enableCamera": "true",
                    "videoConfig": {
                        "audio": true,
                        "audioSampleRate": 0
                    },
                    "talkback": true,
                    "snapshotHandlingMethod": 3,
                    "refreshSnapshotIntervalMinutes": 10
                }
            ],
            "cleanCache": true,
            "unbridge": true,
            "platform": "EufySecurity",
            "username"<EMAIL_ADDRESS>            "password": "XXXXXX",
            "deviceName": ""
        }

can you send me yours logs ? https://github.com/homebridge-eufy-security/plugin/wiki/Basic-Troubleshooting

Here are my logs:
configui-server.log
log-lib.log
eufy-log.log

Ok in fact as per lib description this device is not yet supported : https://bropat.github.io/eufy-security-client/#/supported_devices
You can add your 2 cents here : https://github.com/bropat/eufy-security-client/issues/366

The latest release of eufy-security-client added support for this device
https://github.com/bropat/eufy-security-client/releases/tag/3.0.0

Running on the latest hksv release 2.3.11, all of the switches and sensors show up, but not the camera (tried bridged vs unbridged, hksv and regular camera). Error for unbridged with no hksv:
[03/11/2024, 12:06:28]  [EufySecurity]  ERROR   Solar Wall Light Cam while happending Delegate TypeError: Cannot read properties of undefined (reading 'log')

Currently expected.
No cameras or streaming is working atm.
Current version was to see / get the new devices to show up "correctly".

@town3r No cameras or streaming working on the hksv branch? Or on the main branch as well?

Only the hksv branch which is the only one w/ the new v3.0 device library.

These logs are from a homebridge running the plugin off of that branch

yeah no streaming on HKSV and the main branch don't support the new device

debug/error logs running on v3.0.0:
[04/16/2024 11:45:37]   [EufySecurity-3.0.0]    DEBUG   [BaseAccessory.ts:157]  Solar Wall Light Cam GET 'AccessoryInformation / HardwareRevision': <IP_ADDRESS>
[04/16/2024 11:45:37]   [EufySecurity-3.0.0]    ERROR   [StationAccessory.ts:323]     Solar Wall Light Cam handleSecuritySystemCurrentStateGets: Wrong return value
[04/16/2024 11:45:37]   [EufySecurity-3.0.0]    DEBUG   [BaseAccessory.ts:157]  Solar Wall Light Cam GET 'SecuritySystem / SecuritySystemCurrentState': false
[04/16/2024 11:45:37]   [EufySecurity-3.0.0]    ERROR   [StationAccessory.ts:323]     Solar Wall Light Cam handleSecuritySystemTargetStateGet: Wrong return value


The selected permissions 'Tag' and 'Filter' do not display on one SAS attached storage account's properties panel

Storage Explorer Version: 1.16.0-dev
Build:  20201014.18
Branch: main
Platform/OS: Windows 10/Ubuntu 16.04/ MacOS Catalina
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Select one normal storage account -> Attach it via SAS (Select full permissions).
After successfully attached -> Check the permissions on the attached storage account's properties panel.

Expect Experience:
The permissions display well.
Actual Experience:
The permissions 'Tag' and 'Filter' do not display.

Verified this issue on build 20201016.4. Reproduce. We will verify this issue on a newer build.

Verified this issue on build 20201020.3. This issue has been fixed. So close it.


Add black text to MisakiConsole timestamp

Please describe the changes this PR makes and why it should be merged, as well as any and all proof of successful tests:
Adds black text to MisakiConsole timestamp
Semantic versioning classification:

[] This PR changes the framework's interface (methods or parameters added)

[] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

[] This PR only includes non-code changes, like changes to README, etc.

I've tried about 20 different variations of colors but they're all very murdering on the eyes or don't mix well


ensure labels always show up at reasonable proximity

Occasionally the initial graph will finish loading but the labels won't show up until zoom is adjusted despite being "close enough" for labels to appear.

Fixed in client v0.3.0


Raise the minimum compatible Python version to 3.6

As we discussed recently, Python 3.5 is getting old, and we could take advantage of some newer language features and ditch some old compat code if we raised the version floor for our projects up to 3.6.
Things that would definitely need to happen for this to be feasible for us:

[x] Either upgrade nix to Mint 19, or otherwise use a backports repository of some form to replace python-3.5 with python-3.6.

[x] If doing the OS upgrade, definitely would want to take full disk images beforehand so that I can compare the before-and-after and ensure that none of our important system configuration files etc get reverted or otherwise messed with.

Things that we would then be able to clean up or otherwise nice-ify in our Python code:

[x] Remove the enum36 enums-in-pre-Python-3.6 compat module
[x] Use subscript operator on re.Match objects
[ ] Probably many other things (TODO: look at Python 3.5 --> 3.6 changelog for opportunities to make further exciting backward-compatibility-breaking changes!)

Things we should then also do:

[x] Update the minimum allowed Python version in our README, packaging configuration, etc as applicable
[x] Probably apply the same Python version step to our other repos as applicable

@bgottula
https://github.com/seeing-things/point/pull/39
https://github.com/seeing-things/track/pull/132
https://github.com/seeing-things/zwo/pull/34


Error in httpserver.cpp on Arch Linux

When installing on Arch Linux, I receive the following error:
make[3]: Leaving directory '/storage/deeponion'
  CXX      DeepOniond-bitcoind.o
  CXX      libbitcoin_server_a-addrdb.o
  CXX      libbitcoin_server_a-addrman.o
  CXX      libbitcoin_server_a-bloom.o
  CXX      libbitcoin_server_a-blockencodings.o
  CXX      libbitcoin_server_a-chain.o
  CXX      libbitcoin_server_a-checkpoints.o
  CXX      consensus/libbitcoin_server_a-tx_verify.o
  CXX      libbitcoin_server_a-httprpc.o
  CXX      libbitcoin_server_a-httpserver.o
httpserver.cpp:73:10: error: ‘deque’ in namespace ‘std’ does not name a template type
   73 |     std::deque<std::unique_ptr<WorkItem>> queue;
      |          ^~~~~
httpserver.cpp:32:1: note: ‘std::deque’ is defined in header ‘<deque>’; did you forget to ‘#include <deque>’?
   31 | #include <support/events.h>
  +++ |+#include <deque>
   32 |
httpserver.cpp: In member function ‘bool WorkQueue<WorkItem>::Enqueue(WorkItem*)’:
httpserver.cpp:91:13: error: ‘queue’ was not declared in this scope; did you mean ‘Enqueue’?
   91 |         if (queue.size() >= maxDepth) {
      |             ^~~~~
      |             Enqueue
httpserver.cpp:94:9: error: ‘queue’ was not declared in this scope; did you mean ‘Enqueue’?
   94 |         queue.emplace_back(std::unique_ptr<WorkItem>(item));
      |         ^~~~~
      |         Enqueue
httpserver.cpp: In member function ‘void WorkQueue<WorkItem>::Run()’:
httpserver.cpp:105:35: error: ‘queue’ was not declared in this scope; did you mean ‘Enqueue’?
  105 |                 while (running && queue.empty())
      |                                   ^~~~~
      |                                   Enqueue
httpserver.cpp:109:31: error: ‘queue’ was not declared in this scope; did you mean ‘Enqueue’?
  109 |                 i = std::move(queue.front());
      |                               ^~~~~
      |                               Enqueue
make[2]: *** [Makefile:7312: libbitcoin_server_a-httpserver.o] Error 1
make[2]: Leaving directory '/storage/deeponion/src'
make[1]: *** [Makefile:11630: install-recursive] Error 1
make[1]: Leaving directory '/storage/deeponion/src'
make: *** [Makefile:754: install-recursive] Error 1

I have attempted the installation with several different configurations:

./configure ## I attempted this with a source build of db4.8 in my $PATH, the AUR db4.8 in $PATH, and the db4.8 that comes with this package

./configure --disable-wallet --without-gui --without-miniupnpc ## As suggested in README.md

./configure --with-incompatible-bdb ## I attempted this with package (db5.3)[https://www.archlinux.org/packages/core/x86_64/db/] from Arch Linux repository

Regardless of the configuration flags, when I sudo make install I end up with the same error

This is an environment issue and not a code base issue, Have you tried the pre-compiled Linux version?
https://github.com/deeponion/deeponion/releases/download/v2.1.2/DeepOnion-2.1.2-x86_64-linux-gnu.tar.gz

I'll attempt it now. Do you know what the environment issue might be?

No really. The error in your logs would be an error in all builds if it were "true". Yet all Windows, OSX and Linux builds are currently passing the Travis CI.
If you really want to build from scratch, I would start the process from scratch again from a clean deeponion dir.


Travis: update rubies in matrix

This PR uses the latest-released MRI rubies rvm can supply.

These are the newest, but the listed ones are the preinstalled ones on Travis.


Use last 5.2, 6.0, 6.1 and 6.2 versions

Looks like Alfresco <IP_ADDRESS> doesn't work anymore on Java 8.
To work around that, we would need to use a different skeleton for community 6.0.7-ga and the enterprise 6.0 images.
As a temporary workaround, I just used <IP_ADDRESS> als last 6.0 version.


On windows use XDG base directory if set

On windows, I set XDG directories and I want to use this location instead of ~\AppData\Roaming.  My home directory is full and I can't change it so I set my XDG directories to a different drive that I clone from git and update from git.  Can you add a strategy to use XDG directories if set?

You can use base_strategy::Xdg (or app_strategy::Xdg) instead of base_strategy::Windows (or app_strategy::Windows) if you want to get the paths according to the XDG base directory spec instead of the Windows' known folder spec.

https://github.com/helix-editor/helix/issues/6747

I've added a comment in the linked issue. Helix isn't using the correct function to support XDG on Windows.


Short (wrong) CRC fixed by padding with "0".

The CRC is calculated wrongly in case the CRC contains a "0" as the leftmost digit in the string representation (before the byte swap). This is fixed by padding the string with "0".

Test example: F703040000019B is computed to (wrong) F703040000019BC72 instead of (correct) F703040000019B2C07.


Fix blob storage credentials

This PR adjusts the filename for the S3 credentials, which was recently updated to conform with initupload.

/override post-infra-deploy-prow-cluster
bogus, was accidentally configured as presubmit

/override post-infra-deploy-prow-cluster

/override post-infra-deploy-prow-cluster


Corporate Terms of Services Updates - Fall 2019

Opening this pull request to show changes that are currently live: https://help.github.com/en/github/site-policy/github-corporate-terms-of-service.
The updates in this pull request cover:

Moving certain product terms sections (e.g. GitHub Pages and Learning Lab) to the new GitHub Additional Product Terms
Moving certain usage limitations to the Acceptable Use Policy
Adding pricing language to address usage-based billing for Actions and Packages
Addition of a Feedback section

Thanks @meentastic! Merging now.


fix: protect password from being serialized

🔗 Linked issue

❓ Type of change

[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
I am surprised that v6 template expose password when serialized, which was done correctly in v5 template. This patch should fix it all.
📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Thanks :) We had it back in v5. Somehow missed it this time.


Rounded Corners With Aspect as 'Fill' Compresses Loading image

Hi,
I have a listview with ffimageloading image plugin. My requirement is image should be rounded corner while the image shape is rectangular. While the loading image is visible, it is getting compressed when Aspect is 'Fill'. When Aspect is 'AspectFill', the image wont get shrinked. But, the image wont appear with rounded rectangle.
When the image is 'Fill'

When the image is 'AspectFill'

Here is my code
<ffimageloading:CachedImage x:Name="NewsImage"   LoadingPlaceholder="default_image2.png"  Grid.Row="1" Grid.RowSpan="7" Grid.Column="1"       Aspect="AspectFill" HorizontalOptions="Fill" VerticalOptions="Fill" MinimumHeightRequest="120" WidthRequest="120" >
<ffimageloading:CachedImage.Transformations >               					 <fftransformations:RoundedTransformation BorderSize="10" BorderHexColor="#C6C8CA"   Radius="60"/>
</ffimageloading:CachedImage.Transformations>
</ffimageloading:CachedImage>

I am sorry for being off topic, but could you share your transformation code with me? I need it myself and I'd love to take a look at yours.
Try using DownsizeToView to fix your problem? I am new to this plugin so I can't be of much help.

RoundedTransformation has an additional CropWidthRatio and 'CropHeightRatioparameters used for such purposes (egCropWidthRatio=2; CropHeightRatio=1;`). https://github.com/luberda-molinet/FFImageLoading/blob/master/source/FFImageLoading.Transformations/RoundedTransformation.cs#L29-L30


@nhost/react-urql package

Can we expect a package similar to @nhost/react-apollo for URQL?
I've seen this repository, but the README.md is not what I expect. But in fact, most of the configuration for the @nost/react-urql was ready.

#271

yes, duplicate of the above. closing


Fixes to conda installer for Python3

Pull Request Test Coverage Report for Build 104

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 70.498%

Totals

Change from base Build 102:
0.0%

Covered Lines:
2012

Relevant Lines:
2854

💛  - Coveralls


fix: correct path to images

Description
The PR just fixes the path to the images referenced in markdown files.
Proposed Changes
Just the image paths changed from ../img to ./img
Checklist

[X] I have tested these changes locally.
[X] I have reviewed the code changes.
[X] I have updated the documentation (if necessary).
[ ] I have added appropriate unit tests (if applicable).

These paths are actually correct - the markdown pages render as a "folder" in the URL hierarchy (e.g.,: https://microsoft.github.io/graphrag/prompt_tuning/auto_prompt_tuning/), so you need the extra ../. This is a bit confusing during development because it seems one level too low.


Crash when accessing the app settings on tablets

When accessing the general app settings (the wrench symbol at the top) on a tablet, the app will crash.

This seems to be the case for Android 4.4 and above.


[Bug]: The number of members of a role group is not always displayed correctly.

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
The number of members of a role group is not always displayed correctly.
Steps to reproduce?

Log in as Administrator
Goto the admin Personabar and select Roles
The number of members of a role group is not always displayed correctly.

Current Behavior
The number of members of a role group should be always displayed correctly.
Expected Behavior
The number of members of a role group should be always correctly.
Relevant log output
No response
Anything else?
No response
Affected Versions
9.13.2 (latest release)
What browsers are you seeing the problem on?
Firefox, Chrome, Safari, Microsoft Edge
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I think this is the actual situation:

When a user is deleted (but exsiting in the basket), he is still member of the group and counted. You can say that this is Correct because the user is visible too in the Grouplost
When the membership is expired (end date), the user is even listed but NOT counted anymore.

==> Only active members are counted, but there is some inconsitency. If you do not count expired accounts, than you should also not count the 'soft deleted' users.
So, it is nog a bug, but an inconsitency. It can be solved:

explane the count column (users = active users) AND change code so it do not count deleted users (and not expired users).

I think we talk about the same. I did some research/testing to find out the cause of the problem. The issue is that not all Members in a role are counted. The cause is that expired memberships are not counted but still listed. In my opinion that explains the difference.
A verry Dutch 'groet',
Ad


use mf2util

@kylewm's mf2util is awesome. i should start using it, especially for publish and incoming blog webmentions.

yay done!


Import of .dae-embedded materials fails during URDF import

[x] I am at the right place and my issue is directly related to ROS#. General technical questions I would post e.g. at ROS Answers or Stack Overflow. For library-specific questions I would look for help in the corresponding library forums.
[x] I have thoroughly read the Contributing Guideline and writing this issue is the right thing to do in my case.

I found a bug!

[x] I am using the latest ROS# version available here on the master branch.

[x] I am adding all required information, code and data files, screenshots and log files so that you can reproduce the problem.

My OS is: MacOS 10.14

My Unity Version is: 2018.2.11f1

My ROS Distribution is: kinetic

My Build Target Platform is: mac/linux

Here is my bug description:
Some .dae files, e.g. pr2's shoulder_pan.dae, use custom, embedded materials, which are not loaded when importing the URDF from ROS or from file.
Perform the following steps reproduce the bug:

You can use the attached unitypackage file (it's a "pdf" so github allows to upload it... just change the name to actually use it) PR2_urdf.unitypackage.pdf, or use your ROS# setup as explained in #129 to import the pr2.
Import the robot_description.urdf using the context menu import function.

Observed results:

Expected results:
Instead of the blue and green meshes, they should use their proper materials.
For example, the Assets/Urdf/PR2/pr2_description/meshes/shoulder_v0/shoulder_pan.dae can be dragged into the scene and has proper textures then, as unity recognizes them properly:

This is different from #110 as the texturization is not happening via embedded textures but embedded materials.

Thank you @shoeffner for this thorough report. It was very easy to understand and to reproduce.
"It's not a bug, it's a feature!" 😏
Seriously: The original dae textures are overridden by the material definition in the URDF.
If you want to have the original dae material textures, just delete the corresponding lines in the urdf file.
For example, in the definition for the head visuals, lines 926-932:
    <visual>
      <origin rpy="0.0 0.0 0.0" xyz="0 0 0"/>
      <geometry>
        <mesh filename="package://pr2_description/meshes/head_v0/head_tilt.dae"/>
      </geometry>
      <material name="Green"/>
    </visual>

If you delete <material name="Green"/> you will have the original dae texture instead:

I find this override order (URDF over dae) more practical and user friendly than the other way round:

Individual meshes (dae files) are normally used in other programs (e.g. CAD software) where users might want to apply other textures than in the URDF robot system model.
If users make the effort to additionally define a material in the URDF, this definition should win.

Please let me know in case you have any remarks or comments on this. If not, please don't forget to close the issue.

Thank you, I guess I will change the URDF then!
Both cases make sense to me, I understood the materials inside the URDF more like a backup, but this is a perfect explanation. Much appreciated!

Hey, I know this issue is closed, but RViz defaults the opposite way, i.e. the DAE material takes precedence over the URDF color. I understand if you don't want to change it, but where in the code would I change it so it matches RViz?

Nevermind, I found it in UrdfMaterial.cs


[draft] removing provider/channel push/pull of files

This removes push/pull support from channels.
All the HPC providers used channel.push_file to push their batch scripts to the (no-longer) remote system. This has been a basically dead code path since removal of non-remote channels:
The channel is always a LocalChannel now (PR #3677)
The "remote" script directory is always the local script directory (PR #3688) and so LocalChannel.push_file always skips making a copy and returns the path it was given without further action.
So all the removed code is a no-op, and this PR simplifies that into nothing.
Changed Behaviour
Some providers had an option to let users decide if scripts (and other files) would be pushed/pulled to the remote system. Those options are removed by this PR.
Type of change

New feature
Code maintenance/cleanup

@ryanchard any chance you could test the PBS bit of this? (specifically, verify that you can make parsl submit PBS jobs ok still?)
@yadudoc you're listed as technical sponsor (#2554) for a bunch of these changed providers - can you review those?

I tried this on Polaris to test PBS and it all worked great.

@yadudoc wakey wakey - I'd like to get the rest of channel removal done before the Parsl maintenance work ends in May.


docs(api-kit): Update SafeApiKit instantiation

⚠ Do not merge until the following PR is merged ⚠
Changes reflecting the updates here

Will merge all changes in PR #266


Use libcloud unittest

This changeset includes two patches:

Modify Dimension Data tests again to use libcloud.test.unittest which contains logic for deciding the appropriate package version that works across Python versions. This allows us to use assertRaises as a context manager which makes the test cleaner.

Add an entry in docs/development.rst to recommend using libcloud.test.unittest. This is based on a suggestion from @Kami in PR #674.

Good work Mark. I'd like your eyes on #666 if you get a minute. I'm sure the tests need fixing up in the same way so I will get to that.
This change set looks good. Getting these tests and fixtures together was a big effort as you can probably tell!

Thanks, @tonybaloney! I'll look at that PR soon. And woah on the number! ;-)

Thanks :+1:


Weird Plain Text view behaviour

Hi,
On a plain text mail, Plain Text tab displays HTML.
On a HTML mail, Plain Text tab displays HTML and HTML tab displays plain text.
This is just weird and should be easy to fix I guess. :smiley:

Hi @sd65 — thanks for your report!
I'm afraid I can't replicate this. It would be a pretty obvious problem! But if I run something like using the latest version of mailcatcher and the example emails in this repository it all behaves as expected:
mailcatcher
catchmail < examples/plainmail
catchmail < examples/htmlmail
catchmail < examples/multipartmail

Can you please provide complete example message bodies and show some screenshots with the issue? Also, what version of mailcatcher are you using (mailcatcher --version)?

Hi,
Thanks for the quick response. I'm using mailcatcher 0.6.5.
Since your post, I can precise my astonishment. In fact, links are concerted in hyperlinks automatically when using plain text view.
Furthermore,  HTML tags are interpreted in plain text.
Here's some screenshots:

Is it an expected behavior? To me, auto hyperlinks are OK and great but interpreting HTML tags is wrong and should be just ignored. What do you think?
Thanks!

Ah, sounds related to #356 introduced by #97. I'm tempted just to revert #97 completely.

Any update on this issue? I've been encountering it lately.

This is tracked in a new issue #446, please follow there.


add conda installation instructions

Adds the line conda install -c conda-forge pigar to the instructions

Thanks!


Not booting after restart, can't seem to disable dm-verity

So as other people here, I'm stuck not being able to boot the DSU after a succesful installation.
As mentionned in #15, I tried flashing Google's empty vbmeta.img with the --disable-verity --disable-verification flags, but I just get a bootloop.
Also tried flashing my own vbmeta.img with the same flags or reinstalling Magisk with the echo KEEPVERITY=false>>/data/.magisk method, to no avail.
Am I stuck just having to format and flash the empty vbmeta, or is there another way for me to disable AVB without performing a factory reset ? :)
Trying this on a Poco F3 (alioth) running PixelPlusUI v4.8, and using the Magisk module with custom gsid.

Maybe your issue is not even related to vbmeta:

Some Custom ROM builds may contains custom implementations, which may not provide any GSI support.

Anyway, does DSU Loader in developer options works for you?
If not, maybe the custom ROM build you're using in your device is not capable of booting GSIs, or maybe a vbmeta issue.
Also, i highly recommend you trying DSU in Stock ROM, to check if it works as expected, if so, then, it is likely to be a Custom ROM problem.


Feat: Enable hosting app in any route, with easy config

Pull Request type

[ ] Bugfix
[x] Feature
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes (Please run ./gradlew generateLock saveLock to refresh dependencies)
[ ] WHOSUSING.md
[ ] Other (please describe):

Changes in this PR
Describe the new behavior from this PR, and why it's needed
Issue #3656
Alternatives considered
All details are in the issue attached with this PR

Fixed review comments and rebased my commits with upstream.

@nhandt2021, @peterlau - could we get this PR merged if there are no further changes required?

@nhandt2021, @peterlau - could we get this PR merged if there are no further changes required?

I don't have permission to do that 😄

@peterlau - could we get this PR merged if there are no further changes required?


Authorization in URL fails with Domain-based Username

The authorization for vCenter is passed by providing the username and password in the URL itself.  fmt.Sprintf("%s:%s@%s", username, password, url).
Some consumers use domain's in their usernames: my-domain\username.  The error provided from Golang is along the lines of invalid character in URL.
Workaround
To workaround this issue, we modified the buildGovcCommand function to use the Url instead of CredentialUrl and exported GOVC_USERNAME and GOVC_PASSWORD prior to running the stembuild.

@mike-carey We've built support for Domains in the vCenter username into stembuild itself. So the 2019.9 and 1803.14 should fix this issue. Please re-open it if it doesn't!


Cassandra PHP client - Invalid or unsupported protocol version

I am trying your php client.
My code:
$nodes = ['<IP_ADDRESS>:9042'];
$database = new \evseevnn\Cassandra\Database($nodes, 'people');
$database->connect();

I get this exception error:
evseevnn\Cassandra\Exception\ConnectionException: Protocol error: Invalid or unsupported protocol version (1); the lowest supported version is 3 and the greatest is 4
Where do I set protocol version?
Thank you.
R.

Sorry, this repository deprecated and not maintained anymore.
Please use https://github.com/duoshuo/php-cassandra


removes printing and adds logging

This would make it suitable for a new version release, @e-lo & @ianberg-volpe


Smallest divisible number

Given a number N, find an integer denoting the smallest number evenly divisible by each number from 1 to n.
I would like to contribute to this under GSSOC'21. Please assign it to me.
Algo-Tree/Code/C++/

I would like to contribute to this under GSSOC'21. I will do it in Java.Please assign it to me.

I'm the participant in GSSOC'21. Could you please assign me this.I would love working on this.

Hi , I would like to work on this project under GSSOC'21 , Could you please assign it to me?

Hello sir/ma'am, I am a participant of GSSoC'21 and I would like to work over it, can u assign it to me?

Hi,
I am GSSOC'21 participant
My code will be in JAVA with proper comments and test cases.
@rudrakshi99 @nakul-19 @plazzy99 please assign me this issue

Added Smallest Divisible Number in Java #1491

@OjusWiZard
sir, please review my PR.

Hi,
I am a GSSOC'21 participant. I would like to solve this issue in Python. Please assign it to me.

@OjusWiZard
sir, please review my PR.


Karpenter makes wrong assumptions about CNI and kubelet max pods

Expected Behavior
Karpenter either takes in max pods as a configurable constraint or does not take it into consideration when calculating the amount of pods needed.
Actual Behavior
When small instances are provisioned, it only assigns it a handful of pods, way below what the node can actually handle.
In other cases, it creates really huge instances and assigns it hundreds of points, but the kubelet only accepts 110 (the default maxPods kubelet setting) of them.
The calculations assume that the AWS VPC CNI is used and that prefix mode is not enabled, which will be an increasingly rare configuration.
Steps to Reproduce the Problem
Spin up 500-600 pods with cpu.request=100m on any cluster not running AWS VPC CNI.

This is on our radar and we're working on finding a solution to this as part of cohesive improvements to launch template flexibility.

We could probably tap into the same lookup table I used for Pod ENI (might even be same value)

I'd really like to get to a world where we limit max pods by cpu/memory, and choose acceptable density/overhead values. The fact that <1.8 CNI is used widely is an inhibitor to this. I can see potentially supporting higher density by default, and including a flag that forces a more restrictive value.
@suket22 would love your opinion on this.

In kops, most people use other CNIs. MaxPods is a per instance group configuration one can set if one wants to. Default is 110 and from my own experience one rarely has that high density. I am also not sure I ever want such high density as a significant part of capacity would be gone if the instance fails.
Should someone use vpc cni, then same logic as Karpenter is used.

One idea to explore, use "IntOrString" to support things like spec.density: 30, spec.density: vpc-cni, spec.density: default (some strategy like cpu/memory)

Topology spread constraints won't do anything to avoid say 1/3 of capacity to go away if a single instance dies. 1/3 capacity going away during AZ failure may be something one gets away with, but not on a regular basis. I think a lot of cluster admins aim to have a certain amount of Nodes in the cluster and adjusts instance type thereafter.
If karpenter intends to control max pods, it must also expose what it intends it to be so installers can configure accordingly. E.g an annotation on the Node object.

I'm using another CNI and running into this now as well. Now that we have spec.kubeletConfiguration, I'm thinking about creating a PR that adds a maxPods option there. The tricky part is the AL2 EKS-optimized AMI makes the assumption you're using the AWS CNI, unless you set --use-max-pods=false. So, we could allow someone to set a value of -1 (which isn't allowed), but can be handled by the specific provider to indicate no value should be set. In the case of the AL2 AMI, we can pass along the --use-max-pods=false flag. Thoughts?

The important bit is the logic karpenter use internally for scheduling pods before it knows the actual Node Pod capacity.

Would it be possible to consolidate this and #445 since they both deal with the same problem / request?

@akestner,
It would seem more logical to me, from a user perspective, to inform in the provisioner specs whereas the ENI prefix is being used in the cluster's CNI or not. Then the amount of pods could be calculated using the MaxPodsCalculator or any other similar method.
If we use the "max-pods" as a parameter in the provider, we'd be restricting the instance families that would match this number. This is ok if we think about reusing the created instance for other workloads but, if so, it would be a similar approach to what is obtained through Cluster Auto Scaler not? Once that all the instances from an specific ASG would have the "same" size.
In the other hand, if Karpenter's proposal is to find a "Best fit" for the current "Pending" pods, calculating the number of pods once the instance family is selected seems more accurate for me. It seems unreasonable, from the "best-fit" perspective, to search among instances that could fit a pre-defined "--max-pods 110" (considering it predefined in the provisioner) if I only have 1 pending pod due to lack of CPU.
What do you think? Have I misunderstood your suggestion? Or I could also have a wrong Idea of Karpenter's goals as well...


Unable to save model when using Mirrored Strategy with multiple GPUs

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Debian GNU/Linux 9 (stretch) (Linux 4.9.0-9-amd64)
TensorFlow installed from (source or binary): Binary
TensorFlow version (use command below): v1.12.1-7260-gd4bc7d98c6 2.0.0-dev20190729
Python version: 3.7.2
GPU model and memory: 2 X Tesla V100 (24 gig RAM)

Describe the current behavior
An error is thrown when saving a keras model that has been compiled in using a Mirrored Strategy using more than one GPU.
Describe the expected behavior
Should be able to save and reload models that have been saved under Mirror Strategy.
Code to reproduce the issue
from tensorflow.keras.applications.inception_v3 import InceptionV3

mirrored_strategy = tf.distribute.MirroredStrategy()

def get_model():
    with mirrored_strategy.scope():
        model = InceptionV3(input_shape=(299, 299, 3),
                                 include_top=True,
                                 weights='imagenet',
                                 pooling='avg')

        model.compile(loss='sparse_categorical_crossentropy',
                      optimizer=tf.keras.optimizers.Adam(),
                      metrics=['accuracy'])

    return model

model = get_model()
model.save("my_model")

Other info / logs
See attached.
logs.txt

You need to define the model function inside strategy.scope() or remove the function and just use
`
with mirrored_strategy.scope():
    model = InceptionV3(input_shape=(299, 299, 3),
                         include_top=True,
                         weights='imagenet',
                         pooling='avg')

    model.compile(loss='sparse_categorical_crossentropy',
                  optimizer=tf.keras.optimizers.Adam(),
                  metrics=['accuracy'])`

@richriley ,
Can you please let us know if solution provided by @rishabhsahrawat worked? Thanks!

It seems that my original code now works on 2.0.0-dev20190809. I can confirm that @rishabhsahrawat's example also works.
Thanks for your help.

Closing since the issue is resolved.Thanks!

Closing since the issue is resolved.Thanks!


Release notes for 18.06.0-ce-win70 (Stable) cc @gbarr01

Deploy preview for modest-edison-79d82e ready!
Built with commit 5ec623faadb4c26d744ae8e34e1c0cfdecc6ef8d
https://deploy-preview-7101--modest-edison-79d82e.netlify.com


First digit only has single color using color presets

First of all thanks for the great work! Otherwise using multiple boards with inbuilt segments would have been the only other solution.
Describe the bug
When using "Clock" effect with a preset color pallet, e.g. "Yelmag", the first (left) digit has one single color, while the other 3 digits have the expected color effects.
I have checked the wiring and functionality of my LED strips with the rainbow effect. Every LED is addressable and function normally.
To Reproduce
In 12h format. Choose Clock, then instead of using 2 colors (one for hh and one for mm), choose any preset color pallet from below. Maybe select Yelmag for the most observable effect.
Expected behavior
Every digit should have the selected color effect applied.
WLED version

Board: [Sonoff Basic R2]
Version [10.2]
Format [self-compiled]

Additional context
Here are some pictures.

Thank you for your help!

Sounds like an easy fix. I'm on it.

Sounds like an easy fix. I'm on it.

There was just one line missing. Fixed it and it should work now. Remember to include this new commit in your fork. Have a nice day and stay safe! =)

There was just one line missing. Fixed it and it should work now. Remember to include this new commit in your fork. Have a nice day and stay safe! =)

I have no idea, as i never dealt with those. Maybe try a shot in the official WLED Discord.

I have no idea, as i never dealt with those. Maybe try a shot in the official WLED Discord.


When doing git pull, git merge, ... (basically any git operation that changes files) then omnisharp does not update its intellisense / symbols database

Issue Type: Bug
To reproduce:

Start vscode
Wait for omnisharp to have completely started and having parsed all files
Do a git merge, git pull or something that creates new files, moves files, ...
Intellisense / Omnisharp symbols are not updated

This causes several different issues, for example:

New classes not being recognized by intellisense
If a file that is open in vscode was moved on git, and one does a git pull, it sometimes thinks the symbol is defined twice
...

VS Code version: Code 1.32.2 (e64cb27, 2019-03-13T02:00:46.035Z)
OS version: Windows_NT x64 10.0.16299

@RononDex Those git operations can do all kinds of file manipulations. Can you help us narrow this down? Is it renaming file that results in duplicate? Adding a new file with a new type and it doesn't show up? And so forth.

@rchande yes, its file renaming that results in a duplicate.
New files declaring new classes are then not resolved by omnisharp (and it keeps showing unkown type error within vscode, building works fine though)

@rchande @akshita31 Just tried with the beta10 release, still got the same issue (occurred with git checkout, checking out another branch)

But project builds without issues

Issue here is that omnisharp currently loads source text:

initial server load,
"Buffer Update" endpoint (which updates source as you type in vscode)
"FileCreated" event.

What is missing here is "FileChanged" event, which gets triggered every time any process changes file. Adding this is very simple, I have a local build with this turned on because I find the issue so annoying
https://github.com/SirIntruder/omnisharp-roslyn/commit/7ef1410c44cbffa41d9e14c4431d6b3d4f175ebf
I assumed it was not done originally for performance fears, but having this is a life saver when working with git. In my experience, I didn't have any major issues with this on. If it was just an oversight I would apply this patch, and if not, at least expose an option to the users.

Also there is another issue in "making omnisharp more responsive" agenda: vscode extension currently doesn't forward "folder changed" events because the globbing pattern is set to only watch files, and there is no code in omnisharp that can handle "folder deleted" events.

A lot has changed with O# project watching since this issue was opened. If you are still having problems, please open a new issue.


pip refactoring will break pipdeptree

@dstufft has decided to move around the imports in pypa/pip#4700, which will necessitate adjustments to the imports in pip 10.0.

Yeah, pipdeptree is pretty much a hack because it relies on pip as a library and uses it's internal api. I knew we'd run into this situation some day! But if it's just code being moved around, I think it should be a fairly straightforward change to handle imports for different versions of pip using a simple try..catch block.
Thanks for informing 👍  I'll keep track of that PR in the pip repo.

Yea, basically no code changes, just shuffling everything into pip._internal to try and make it more obvious that the APIs are internal, to hopefully prevent some people from accidentally using them unawares of that fact.


[backport] Add 1.17 to supported NumPy versions

Backport of #2368

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit dae4d5059da2ebc8d297572def3b431e221aa662, target branch v6) succeeded!

CI failure is unrelated.


feat: Add AI generated metadescription for metadata entities

Many entities that are queried in the metadata endpoint haven't any meta description (see here).
Therefore, they lack also a description for SEO.
Generating metadescription through AI and saving in the database is the most sustainable way of solving this problem.

videos are excluded, since AI can't generate description of them

entities with very short content (less than 20 characters) won't also receive description, since AI can't do anything meaningful with it

[x] ~Do we want to remove cache from entities? (Unnecessary for metadata endpoint, but good for SEO)~

[x] Should we add a string like  [maschinengenerierte Beschreibung] at the end for transparency and in case we in the future want to identify which ones are human written and which ones generated?

Do we want to remove cache from entities? (Unnecessary for metadata endpoint, but good for SEO)

No, not needed :smile:

@AndreasHuber @hugotiburtino I see the following todos:

[ ] Add the description in batches, see https://github.com/serlo/db-migrations/pull/314/files/5864d0c84785feb2ec979a50a0a37f5ac0bda925#diff-eb91645333eee3e46f55a0d3e588fe18185e1cd4c9339a70fc4f4713ebb7d6ca
[ ] Add a field metadata_description_source or is_description_ai_generated, see https://github.com/serlo/db-migrations/pull/314/files/5864d0c84785feb2ec979a50a0a37f5ac0bda925#diff-eb91645333eee3e46f55a0d3e588fe18185e1cd4c9339a70fc4f4713ebb7d6ca
[ ] Reduce the script to the first 100 articles so that we can test it in staging


[VCDA-4514] Add events only on create operations

Signed-off-by: Aniruddha Shamasundar<EMAIL_ADDRESS>Description
Please provide a brief description of the changes proposed in this Pull Request

Update event set in vcdcluster_controller only when cluster.status.phase is not "Provisioned"
Update event set in vcdmachine_controller only when machine.status.bootstrapready is false

Checklist

[x] tested locally
[ ] updated any relevant dependencies
[ ] updated any relevant documentation or examples

API Changes
Are there API changes?

[ ] Yes
[x] No

If yes, please fill in the below

Updated conversions?

[ ] Yes
[ ] No
[x] N/A

Updated CRDs?

[ ] Yes
[ ] No
[x] N/A

Updated infrastructure-components.yaml?

[ ] Yes
[ ] No
[ ] N/A

Updated ./examples/capi-quickstart.yaml?

[ ] Yes
[ ] No
[ ] N/A

Updated necessary files under ./infrastructure-vcd/v1.0.0/?

[ ] Yes
[ ] No
[x] N/A

Issue
If applicable, please reference the relevant issue
Fixes #

This change is

/lgtm from me too