Samuel updates

Corrections for backtracking : change in the fixed point forward function with a check_iteration_fn that checks if we can perform next iteration.
Update some docstrings
Enable plotting with batch_size > 0

Codecov Report

Merging #17 (cc35030) into main (347dc22) will decrease coverage by 0.07%.
The diff coverage is 35.36%.

:exclamation: Current head cc35030 differs from pull request most recent head 2fdabc1. Consider uploading reports for the commit 2fdabc1 to get more accurate results

@@            Coverage Diff             @@
##             main      #17      +/-   ##
==========================================
- Coverage   52.85%   52.79%   -0.07%
==========================================
  Files          80       80
  Lines        3971     3995      +24
  Branches      530      545      +15
==========================================
+ Hits         2099     2109      +10
- Misses       1709     1719      +10
- Partials      163      167       +4

Impacted Files
Coverage Δ

deepinv/optim/optim_iterators/optim_iterator.py
85.71% <0.00%> (-2.39%)
:arrow_down:

deepinv/training_utils.py
57.67% <0.00%> (+3.71%)
:arrow_up:

deepinv/optim/optimizers.py
47.95% <27.11%> (-4.16%)
:arrow_down:

deepinv/optim/fixed_point.py
41.33% <66.66%> (-0.46%)
:arrow_down:

deepinv/utils/metric.py
34.21% <100.00%> (ø)


Error on build: Could not load file or assembly 'xunit.execution.dnx, Version=<IP_ADDRESS>'

This error happens when I execute the build command.
Also. Unit Tests doesn't work. I already tried to clean my TEMP folder.
info: Target compile
info: Target test-compile
info: Target xunit-test
info: Exec
info:   program: cmd
info:   commandline: /C dnx test
info:   workingdir: test\EntityFramework.Commands.FunctionalTests
xUnit.net DNX Runner (32-bit DNX 4.5.1)
Discovering: EntityFramework.Commands.FunctionalTests
System.IO.FileNotFoundException: Could not load file or assembly 'xunit.execution.dnx, Version=<IP_ADDRESS>' or one of its dependencies. The system cannot find the file specified.
warn: Exit code 1 from cmd
verbose: Stack trace:
at View0af0878dbd52486781c8ef1c6662917a.K(String command, String workingdir, String dnvmUse) in c:\Users\felip\AppData\Local\Temp\9546b2cfde444cd9941bb6c5124e17c5-1.cs:line 1232
at View0af0878dbd52486781c8ef1c6662917a.DnxTest(String projectFile, Boolean testParallel) in c:\Users\felip\AppData\Local\Temp\9546b2cfde444cd9941bb6c5124e17c5-1.cs:line 441
at View0af0878dbd52486781c8ef1c6662917a.b__6b(String projectFile) in c:\Users\felip\AppData\Local\Temp\9546b2cfde444cd9941bb6c5124e17c5-1.cs:line 8576
at System.Collections.Generic.List1.ForEach(Action1 action)
at View0af0878dbd52486781c8ef1c6662917a.b__69() in c:\Users\felip\AppData\Local\Temp\9546b2cfde444cd9941bb6c5124e17c5-1.cs:line 8576
at Sake.Engine.Builder.BuilderBase1.CallTarget(String name)    at Sake.Engine.Builder.BuilderBase1.StartingTarget(String name)
at View0af0878dbd52486781c8ef1c6662917a.b__4a() in c:\Users\felip\AppData\Local\Temp\9546b2cfde444cd9941bb6c5124e17c5-1.cs:line 2727
at Sake.Engine.Builder.BuilderBase1.CallTarget(String name)    at View0af0878dbd52486781c8ef1c6662917a.<RenderViewLevel0>b__42() in c:\Users\felip\AppData\Local\Temp\9546b2cfde444cd9941bb6c5124e17c5-1.cs:line 2583    at Sake.Engine.Builder.BuilderBase1.CallTarget(String name)
at Sake.Engine.SakeEngine.Execute(Options options)
at Sake.Engine.SakeEngine.Execute(String[] args)
at Sake.Program.Main(String[] args)

Can you delete everything from the .dnx folder in your user profile and try again

Great, worked!


Empty runQualities/setQualities should not be exported

Empty runQualities/setQualities (i.e. if the other one is present) should not be included in an mzQC file, but are currently still serialized as an empty list.

PR for RC coming tomorrow (probably)

fix now in main


[stdlib] Removes redundant buffer zeroing in IndexPath initialiser by using `init(unsafeUninitializedCapacity:initializingWith:)

Removes redundant buffer zeroing in IndexPath initialiser by using `init(unsafeUninitializedCapacity:initializingWith:)

@natecook1000 would you please review?

@swift-ci Please smoke test

ping

@swift-ci Please smoke test

ping

@swift-ci Please smoke test macOS

ping

ping

Thanks, @valeriyvan! 🥇


no network/internet access

Windows Version
Microsoft Windows [Version 10.0.22635.3720]
WSL Version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-2
WSLg version: 1.0.61
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26091.1-240325-1447.ge-release
Windows version: 10.0.22635.3720
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-microsoft-standard-WSL2
Distro Version
Fedora
Other Software
No response
Repro Steps
try to use any networking/internet command
Expected Behavior
internet to be connected
Actual Behavior
no internet/networking access
Diagnostic Logs
WslNetworkingLogs-2024-06-09_19-29-43.zip

probably similar to https://github.com/microsoft/WSL/issues/11061

also tried disabling all network interface as the issue linked about said, and that did not work also.

WSL 2.2.4 has an issue, at least with an existing .wslconfig like the following:
# configure .wslconfig . If needed, change debugConsole=true
echo "[wsl2]">"$env:userprofile\.wslconfig"
echo "# Enable nested virtualization">>"$env:userprofile\.wslconfig"
echo "nestedVirtualization=true">>"$env:userprofile\.wslconfig"
echo "# networking mode">>"$env:userprofile\.wslconfig"
echo "networkingMode=NAT">>"$env:userprofile\.wslconfig"
echo "# Turn on default connection to bind WSL 2 localhost to Windows localhost">>"$env:userprofile\.wslconfig"
echo "localhostforwarding=true">>"$env:userprofile\.wslconfig"
echo "# turn off idle timeout">>"$env:userprofile\.wslconfig"
echo "vmIdleTimeout = -1">>"$env:userprofile\.wslconfig"
echo "# needed to start properly user-runtime-dir@0.service">>"$env:userprofile\.wslconfig"
echo "guiApplications = true">>"$env:userprofile\.wslconfig"
echo "# debug console" >>"$env:userprofile\.wslconfig"
echo "debugConsole=false">>"$env:userprofile\.wslconfig"

Downgrade to WSL 2.1.5 (https://github.com/microsoft/WSL/releases/download/2.1.5/wsl.<IP_ADDRESS>.x64.msi) resolves the issue.
Unfortunately I couldn't take the time to find out how to make run WSL 2.2.4 with the configuration mentioned.

@keith-horton: This user is using mirrored networking:
networkingMode=mirrored

yep, downgrading also did not work.

also, i do not use any vpn on this particular box.

WSL 2.2.4 has an issue, at least with an existing .wslconfig like the following:
# configure .wslconfig . If needed, change debugConsole=true
echo "[wsl2]">"$env:userprofile\.wslconfig"
echo "# Enable nested virtualization">>"$env:userprofile\.wslconfig"
echo "nestedVirtualization=true">>"$env:userprofile\.wslconfig"
echo "# networking mode">>"$env:userprofile\.wslconfig"
echo "networkingMode=NAT">>"$env:userprofile\.wslconfig"
echo "# Turn on default connection to bind WSL 2 localhost to Windows localhost">>"$env:userprofile\.wslconfig"
echo "localhostforwarding=true">>"$env:userprofile\.wslconfig"
echo "# turn off idle timeout">>"$env:userprofile\.wslconfig"
echo "vmIdleTimeout = -1">>"$env:userprofile\.wslconfig"
echo "# needed to start properly user-runtime-dir@0.service">>"$env:userprofile\.wslconfig"
echo "guiApplications = true">>"$env:userprofile\.wslconfig"
echo "# debug console" >>"$env:userprofile\.wslconfig"
echo "debugConsole=false">>"$env:userprofile\.wslconfig"

Downgrade to WSL 2.1.5 (https://github.com/microsoft/WSL/releases/download/2.1.5/wsl.<IP_ADDRESS>.x64.msi) resolves the issue.
Unfortunately I couldn't take the time to find out how to make run WSL 2.2.4 with the configuration mentioned.

Hi. I am facing the same network issue and couldn't resolve it for a while now.
Could you share how we can downgrade WSL from <IP_ADDRESS> to 2.1.5?
Do we just run the executable you link?

Hi,
Case distinction:

networkingMode=mirrored : I don‘t know the actual results neither with 2.1.5 nor with 2.2.4. As far as I remember, it didn’t work well in both versions (Windows 11 - patches - configuration).
networkingMode=NAT : In my lab, 2.1.5. works, 2.2.4. results in no network connectivity. Downgrade helps by simply starting the 2.1.5 .msi installer with local administrative privileges, click through and reopen a new Terminal(Administrator).

Hi @dcasota . Thank you for your prompt response.
I ran the .msi installer and managed to downgrade my WSL - however, it seems like my network issues still persists.
For context, I do not have an existing .wslconfig in my %USERProfile% directory, and I believe the default WSL behavior is to use NAT
https://learn.microsoft.com/en-us/windows/wsl/networking

Default networking mode: NAT
By default, WSL uses a NAT (Network Address Translation) based architecture for networking. Keep the following considerations in mind when working with a NAT-based networking architecture:

Do you have some ideas of what other issues this network connectivity problem might be caused by?
Thanks so much.

I tried to populate a curated answer. Hope this helps.
Constellations
1a) enterprise workstation/laptop: Data Loss prevention policy
'Device control in Microsoft Defender for Endpoint' with an activated policy for W11 devices might detect WSL instances and prevent access to storage and networks.
In any case, prevent data loss. Ask company's IT compliance manager for help. Work together.
1b) Support good standing of IT security. Backup your system.

Hardware bios/firmware level
Windows 11
Installed drivers and agents
Windows Subsystem for Linux
WSL Distribution
For a WSL distribution, use wsl --export <distribution-name> <path\filename.tar>

2) WSL Reinstallation
Typically, a WSL reinstallation fixes misconfiguration issues quite well.
However, create first a backup of your WSL distribution as mentioned in Step 1. A reinstallation deletes any registered WSL distribution.
Here a sample of a reinstallation recipe.
# see https://learn.microsoft.com/en-us/windows/wsl/install-manual#step-1---enable-the-windows-subsystem-for-linux

# Open a Powershell Terminal (Administrator)
dism /online /disable-feature /FeatureName:Microsoft-Windows-Subsystem-Linux
dism /online /disable-feature /featurename:VirtualMachinePlatform
dism /online /disable-feature /FeatureName:Microsoft-Hyper-V
rm "$env:userprofile\.wslconfig"

# reboot

# Open a Powershell Terminal (Administrator)
dism /online /enable-Feature /All /FeatureName:Microsoft-Windows-Subsystem-Linux /norestart
dism /online /enable-feature /All /Featurename:VirtualMachinePlatform /norestart
dism /online /enable-Feature /All /FeatureName:Microsoft-Hyper-V /norestart
bcdedit /set hypervisorlaunchtype auto

# reboot

# Open a Powershell Terminal (Administrator)
wsl --install

3) Network Connectivity
Network connectivity results as a sort of pipeline e.g. physical network adapter ! virtual network adapter ! bridged ! vnic ! vswitch ! portgroup .
If a vnic inside a WSL distribution does not get a network link, the pipeline is broken. Investigate if network connectivity works in another WSL distribution. If it works, it's rather not a WSL issue.
There are different types of network adapters e.g. built-in wired or wi-fi, usb(-c)-to-ethernet, etc. Not all vendor types are enabled by default in the Distros' Linux Kernel.
In case of a Windows 11 network configuration issue, check your configuration.
The WSL Networking Logs provided by @fawaf clearly testifies to the method required.

@fawaf thanks for reporting the issue
can you please collect a new set of networking logs using instructions below? - we need to the capture the process of WSL startup in the logs
run .\collect-networking-logs.ps1
run wsl --shutdown
start WSL and repro
stop .\collect-networking-logs.ps1

oddly, i ran it, but it doesn't continue to collect logs. it just runs to completion and exits.

a reinstall of wsl seems to have fixed this issue as mentioned above. i'll report back if it occurs again.

a reinstall of wsl seems to have fixed this issue as mentioned above. i'll report back if it occurs again.

Hey @fawaf - did you follow @dcasota's instruction above for reinstallation?
After reinstallation, how did you reimport your project files etc. back to your newly installed WSL2?
(I presume his Step 2 instructions above will delete your original WSL's Ubuntu content?)

yep, that is correct. step 1 will back up the distro into a tar file.
i used the import command provided by wsl
wsl --import <Distro> <InstallLocation> <FileName>

@fawaf Thank you for the swift replies!
Could I clarify that everything works well for you after re-importing?
i.e. your personal bash commands, project files, VSCode configuration, etc. etc. are all working ok?
^ just needed some re-assurance before I run the commands, lol!

yep, everything works from what i can tell.

@fawaf @cyberjj999 a question: can you check with wmic qfe list if you have a Windows Security Update KB5039212 installed?
There seems to be a build-in wsl update in KB5039212, because even after having uninstalled wsl + dism packages, wsl -v shows up as 2.2.4.
KB5039212 contains newer wsl bits:
wsl.exe,"10.0.22621.3672","07-Jun-2024","07:29","195,072"
wslconfig.exe,"10.0.22621.3672","07-Jun-2024","07:29","120,320"
wslg.exe,"10.0.22621.3672","07-Jun-2024","07:29","120,320"

Those wsl files are in c:\windows\system32.
I uninstalled the KB with wusa /uninstall /kb:5039212. The files weren't deleted, but wsl -v is back to 2.1.5.
in addition wsl show the well-known Error code Wsl/Service/CreateInstance/GetDefaultDistro/WSL_E_DEFAULT_DISTRO_NOT_FOUND.
On this install base, a reinstallation succeed.
KB5039212 seems to already update the installbase to 2.2.4 despite issue(s) 'no network issue/internet access'.

i do not have KB5039212 installed.

@fawaf @cyberjj999 a question: can you check with wmic qfe list if you have a Windows Security Update KB5039212 installed?
There seems to be a build-in wsl update in KB5039212, because even after having uninstalled wsl + dism packages, wsl -v shows up as 2.2.4.
KB5039212 contains newer wsl bits:
wsl.exe,"10.0.22621.3672","07-Jun-2024","07:29","195,072"
wslconfig.exe,"10.0.22621.3672","07-Jun-2024","07:29","120,320"
wslg.exe,"10.0.22621.3672","07-Jun-2024","07:29","120,320"

Those wsl files are in c:\windows\system32.
I uninstalled the KB with wusa /uninstall /kb:5039212. The files weren't deleted, but wsl -v is back to 2.1.5.
in addition wsl show the well-known Error code Wsl/Service/CreateInstance/GetDefaultDistro/WSL_E_DEFAULT_DISTRO_NOT_FOUND.
On this install base, a reinstallation succeeds.
KB5039212 seems to update the installbase to 2.2.4 despite issue(s) 'no network issue/internet access'. Placed an info at https://answers.microsoft.com/en-us/windows/forum/all/cumulative-updates-for-windows-june-2024/7e7ebdf9-4c8a-420e-aa6c-9ce470649cb3.

Yes. I do have KB5039212 installed in my latest update - incidentally, it seems like the installation date is pretty near or maybe even coincide with the day I started facing the network issue...
is the fix to remove this update then?

I can confirm that uninstalling KB5039212 (and reboot afterwards) help me with my problem (dns working, nat not)

@cyberjj999 In my x86_64 lab, removing kb5039212 helped to afterwards reinstall wsl to 2.1.5 successfully and not have issues with networkingMode. Also, in Start > Settings > Windows Updates > choose pause updates e.g. for 7 days.


Improve hax::main macro

Manual mapping? (internal)
Cleaner hooking? (internal)

#[hax::main(init=setup_hooks)]

Try to do some checks?

Check if the crate-type is ["cdylib"] during compilation (internal)
Check if the process is running with sufficient privileges (external)

I think the adding the init attribute to hax::main would be fairly simple. I'll try to implement it and see how it goes.

While I'm implementing this I had the idea of also being able to pass a process parameter, basically within the proc-macro everything for setting up an external will be done for you.
I think this idea can be augmented to eliminate a ton of boilerplate, for both external and internal.
Think of this example (external):
#[hax::main(process = "csgo.exe")]
fn entrypoint() {
    let value = hax.read::<i32>(0x123456);
}

Expanded to:
fn main() {
    // "hax context" will be created; you can use hax.????? to interact with it

    // ...
}

I think during creation of the "hax context" it could do checks depending on the feature flag (internal: check if crate-type is cdylib, external: check if process is running as admin, etc), and setup everything you need.
Maybe make the "hax context" globally accessible?
What do you think @not-matthias?

I like that approach. But we have to carefully think about whether or not to make the hax_ctx (hax context) static or pass it as parameter.
Static:

Could lead to problems if multiple threads access it (reading/writing at the same time)
Could this lead to some problems in very specific applications? We have to be careful if lazy_static or once_cell uses TLS callbacks. Cause often people try to do weird stuff with the dll (e.g. split it up or make it as small as possible) to get around detections.

Parameter:

If we pass ownership to the entrypoint, then we don't have any of those issues. The developer can store it globally if they want to.
Downside to this is, that you have to pass it around.

Both: We could try and implement both, but I think this would lead to very confusing errors and other problems.
We should really ask more people what they think about those solutions and which they like best.

Yep, that's my main concern with doing something like that. Definitely doing polls would be the best approach here.
Although, we could just have it default to a parameter unless the developer adds a ctx = "global" or something in the hax::main attribute. Something like #[hax::main(process = "csgo.exe", ctx = "global")]?
Another issue is that this already proving to be pretty difficult for me to add init = .... I need to do a lot more research on proc-macros, however there is pretty limited documentation about them.

My primary concern against it, is having two different implementations which generally makes it confusing for the user.
If one looks at an example which uses a global context, I imagine it can be confusing when you don't know about parameter contexts (especially if we only enable one by default)

My primary concern against it, is having two different implementations which generally makes it confusing for the user.

I didn't take that into account, you're right, it definitely would be confusing to the user. I'm trying to mentally figure out which one would be better for the user and it's confusing me xD

Allow to pass your own memory:
fn setup_memory -> impl MemoryRead + MemoryWrite {
    // ...
}

#[hax_macros::main(process = "ac_client")]
#[hax_macros::memory(setup_memory)]
fn main(memory: Memory) {
    println!("Hello, world!");
}


WebVTT subtitles not referenced.

Describe the bug
I am using this package to transcode video and convert it to HLS format for streaming. While it does do that correctly I've ran into an issue where the WebVTT files that it creates aren't referenced or added to the manifests. This has been tested with plenty of video sources and it's the same result.
To Reproduce
Steps to reproduce the behavior:
Just simply get a .mkv file with a subtitle track and use python-ffmpeg-video-streaming to transcode it to HLS format.
Expected behavior
The .vtt files should be referenced in the manifest from my understanding.
Local machine (please complete the following information):

OS: Windows
python-ffmpeg-video-streaming 0.1.15

Any solution? I have this problem too

Hey man, I had to abandon this library and write my own script with shaka packager, I recommend trying that out it's really helped me out a lot. Let me know if you need any help.
https://github.com/shaka-project/shaka-packager
https://shaka-project.github.io/shaka-packager/html/documentation.html#getting-shaka-packager
https://shaka-project.github.io/shaka-packager/html/tutorials/hls.html

Hi, I'm already creating my own in python.
Thanks anyway.


Not compatible with Shopware <IP_ADDRESS>

Thank you for developing this plugin. It worked fine, until the update.

@samkasd Thanks for reporting, I will check it

@mfmaut @samkasd Hi sorry for the forever update 😞 , Im finally have time to update it, could have a look at the latest version if it works with your SW <IP_ADDRESS> onward?


ip_allow.config needs Traffic Monitor IPs

Traffic Monitors should be in the config file when a mid is in a reported OR online state

This issue has been tested and we do not see any issues.
I modified the IP on two Traffic Monitors one with anonline status and one with a reported status.  I then validated the IP showed up in the ip_allow.config.


[FEATURE] add faq section popup modal

design faq section popup modal at footer
To design a FAQ section popup modal at the footer, implement a "FAQ" button that opens a modal overlay when clicked. The modal should display frequently asked questions in a clean, scrollable interface with a close button. Place this at the footer for easy access without disrupting the page layout.

@ananyag309
go for it

@ananyag309
Are you working on this???


Update bundle to 2.12.4

Merge / deployment checklist

[ ] Confirm this change is backwards compatible with existing workflows.
[ ] Confirm the readme has been updated if necessary.
[ ] Confirm the changelog has been updated if necessary.

I've pushed a fix for a bug in #1527 that meant we passed a --qlconfig=undefined argument when there was no qlconfig file.  I've also merged in main to bring in https://github.com/github/codeql-action/pull/1560 which should fix the issues with setup-swift.

Thanks for the fix, @henrymercer. I've confirmed that it works locally. I created a PR against main to fix it there. https://github.com/github/codeql-action/pull/1564

I've pushed a fix for a bug in #1527 that meant we passed a --qlconfig=undefined argument

Erm, yes, I’m running into this because the bundle has been updated (compared to the previous run of the action). But there’s no new release; how do I get the builds working again?

Ah well, reverting to an earlier version codeql-bundle-20230105 worked.

Erm, yes, I’m running into this because the bundle has been updated (compared to the previous run of the action). But there’s no new release; how do I get the builds working again?

Hi @mirabilos — this fix was released in version 2.2.6 of the CodeQL Action.  Please let us know if you still aren't able to use the latest bundle.

Henry Mercer dixit:

Hi @mirabilos — this fix was released in version
2.2.6 of
the CodeQL Action. Please let us know if you still aren't able to use
the latest bundle.

Hm, where did you even get this release from?
https://github.com/github/codeql-action/releases does not show it,
and it shows codeql-bundle-20230317 as latest version, which is what
the GHA updater upgrades to then, for example:
{
"jobs": {
"analyse": {
"steps": [
[…]
{
"name": "Initialise CodeQL",
"uses": @.***",
"with": {
"languages": "cpp"
}
},
[…]
So v2.2.6 does not look like a real release?
[GHA updater] → https://github.com/saadmk11/github-actions-version-updater
bye,
//mirabilos
„Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein Grund,
mksh auf jedem System zu installieren.“
-- XTaran auf der OpenRheinRuhr, ganz begeistert
(EN: “[…]uhr.gz is a reason to install mksh on every system.”)

We release the CodeQL Action using git tags, and release CodeQL Action Bundles using GitHub Releases.  It looks like the tool you're using is only picking up on the GitHub Releases.  We'd recommend configuring your workflow to use the v2 tag (for example uses: github/codeql-action/init@v2).  We update this tag with each release.


Add replicaset helper functions

Closes #793.
Thanks ahead of time for reviewing!

FYI The kubernetes tests passed. Since the tests passed, and the issue mentioned above is very minor, I'll go ahead and merge this in (but would appreciate if you can address the above comment in a follow up PR!).

Awesome thanks! I'll put up PR for that fix here in a second


Updated link for Luxon formats

Instead of link to pre-defined format table, will now point to tokens table.

Thank you @Shreyaakothari for your contributions!


Followed instructions, doesn’t work

Hi, I love what you did. I wanted to use that sleek cool looking page loading but I can’t.
I am running flutter version 3.24.3
I think that flutter have changed the way it loads on web or sm.
If you could spare some time to help me in get it working on new flutter versions, I would be grateful.

Hey @JustAdreamerFL, thanks for reaching out! Just a heads up, the repo is already using the new loader. I believe the steps in the readme might still reference the old method, so I’ll review and update them.

I’ve updated the README file with the steps for the new Flutter Web initialization method. You can check out the changes in PR #3. Let me know if you still run into any issues.

Thanks for looking into this!
I have tried doing it again with updated how to but with no success.
When I set everything in flutter_bootstrap.js to be just the loading animation code, flutter doesn’t start and so nothing happens and the same thing happens even when I put the code before or after default flutter_bootstrap.js code.
Error what I get is this:

Can you post the content of your flutter_bootstrap.js, index.html? Feel free to exclude any sensitive parts, if any.
Also, can you confirm you're using the new Flutter Web initialization method?

Yes, I created this project I think on Flutter version 3.24.
I am sending those files in txt cuz github restriction.
Also these files are from the build/web folder.
bootstrap file
flutter_bootstrap.txt
index file
index.txt

Hey @JustAdreamerFL, sorry for the delay. Updating the build/web/flutter_bootstrap.js file isn't recommended, as it's generated during the build process and will be overwritten. Instead, please update the web/flutter_bootstrap.js file to retain your changes across builds.


bump solr version to 5.2.1

looks like jetty9 is causing trouble for solr init service for v5.2.x:
https://archive.apache.org/dist/lucene/solr/5.2.1/changes/Changes.html#v5.2.0.upgrading_from_solr_5.1
It is no longer possible to run "java -jar start.jar" from inside the server directory. The bin/solr script is the only supported way to run Solr. This is necessary to support HTTP and HTTPS modules in Jetty which can be selectively enabled by the bin/solr scripts. In case you have a pressing need to run solr the old way, you can run "java -jar start.jar --module=http" to get the same behavior as before.
need to check whether require other changes (worth looking into bin/solr) or --module=http is sufficient.

Heh I started work on this Friday as well! Anything I can do to help?

@sylvainsf thank you, really appreciate it.
what i gathered so far is that, new directory structure seems to be broken in v5.2.x and attributes needs to be modified accordingly, like jetty_home.
jetty 9 seems to be using different jetty*xml file for different module (got it from start.jar --help, need to check new init script).
And one major change is new sysv init style, i think its better to update the cookbook with it for >v5.2.x. keeping the attributes is always a challenge and there are significant changes in v5.2
i will start creating individual issues and perhaps i can spend this weekend on it.

Yes I quickly found there was a LOT that would need to change. In the interim I've created some recipes for starting/restarting via the solr command instead of init.d but this is less optimal because after a system restart it would not start solr until the next scheduled chef run.

Was looking into helping write new init.d's from the provided config in the new 5.2.x tarball and integrate the various node attributes in. I think I have had decent success so far but went to try and test the changes and couldn't get kitchen to converge.
Specifically ubuntu 12.04 errors when the java cookbook installs curl due to some really out of date default urls in apt-get. Also noticed the actual specs are real light.
Is there something special you do to get kitchen up or to test in general? Other than this part I think I have the new blessed path for init.d pretty close to working and would love to submit them for review.

@kiwimanman i am with you for specs to be minimal for this cookbook. i am planning to add once cookbook is v5.2.x ready.
the issue you are facing might be due to outdated apt-get update. i have updated .kitchen.yml. thanks for reporting this!
good to hear that you got new sysv init working, i have not gotten much time to finish it. but, i think we would have to modify it in favor of  leveraging /etc/default/solr.
i just committed few changes and opened #46 to add more specs.

Whew, a little more work than I was expecting but I believe that should do it. 5.2.x it seems changed a lot about how the /etc/default/solr file worked but I believe the way I did it should be backwards compatible.


Add method signatures for JDK >= 11

Hello,
the following methods have been added in or after JDK 11. Would it make sense to consider them?

JDK 12:

NumberFormat.getCompactNumberInstance()

JDK 15:

String.formatted(Object...)

For the following methods added in JDK 17 I am not sure if they should be considered. For the Standard In and Out and Error steams it might make sense to use the native / default encoding; though if the other process explicitly specifies an encoding, that should of course be used.

Process.outputWriter()
Process.inputReader()
Process.errorReader()

I found these methods using the newly added "New" tab of the Javadoc: https://docs.oracle.com/en/java/javase/17/docs/api/new-list.html (see JDK-8269400).
Maybe that can be useful for you in the future as well.
However, this information is based on the @since tag. So if the JDK authors forget it you will miss APIs. It apparently also only considers direct usage of @since. So if a class is annotated with @since, but its methods are not, then only the class is listed as new.
In case you were not aware of it already, there are also https://github.com/AdoptOpenJDK/jdk-api-diff and https://github.com/marchof/java-almanac/; but for both the output is rather verbose given that mainly newly added methods and contructors are relevant for this project.

Hi,
{quote}
the following methods have been added in or after JDK 11. Would it make sense to consider them?

JDK 12:

NumberFormat.getCompactNumberInstance()

JDK 15:

String.formatted(Object...)

{quote}
I will check those, thanks for reporting!
{quote}
For the following methods added in JDK 17 I am not sure if they should be considered. For the Standard In and Out and Error steams it might make sense to use the native / default encoding; though if the other process explicitly specifies an encoding, that should of course be used.

Process.outputWriter()
Process.inputReader()
Process.errorReader()
{quote}

Those is indeed worth a discussion. But other methods like System.in which is a printstream also uses default encoding, same for the Readers and Writers. For the external process this is a bit different (because we call it), but I think most uses of those methods are about communicating with console programs).
A good idea would be to check the latest JDK 18 JEP about making UTF-8 the default (unless specified differently). It would be good to figure out how this is handled in this issue.
I will dig, but I am a bit busy at moment.

A good idea would be to check the latest JDK 18 JEP about making UTF-8 the default (unless specified differently). It would be good to figure out how this is handled in this issue.

The documentation of these methods say they use the native.encoding System property. If I understand JEP 400 and JDK-8266075 correctly that System property will have the value Charset.defaultCharset() used to have.
For console applications I assume using the OS specific charset would make sense, however I am not sure if that makes sense when communicating with other processes.

Maybe the following < JDK 11 methods should be added as well (probably not worth it to create a separate GitHub issue):

java.util.GregorianCalendar#from(java.time.ZonedDateTime)
However, there is no overload taking a Locale, so maybe it should not be reported then.
java.util.ResourceBundle#getBundle(java.lang.String,java.lang.Module)
java.beans.beancontext.BeanContextSupport#BeanContextSupport()
java.beans.beancontext.BeanContextSupport#BeanContextSupport(java.beans.beancontext.BeanContext)
java.io.ByteArrayOutputStream#toString(int)
javax.imageio.ImageWriteParam#ImageWriteParam()
Not completely sure about this one because it says "It is up to the subclass to set up the instance variables properly", but the only implementation difference compared to the ImageWriteParam(Locale) seems to be that the locale field is not initialized (and uses the default locale).
javax.imageio.plugins.bmp.BMPImageWriteParam#BMPImageWriteParam()
java.util.Properties.html#load(java.io.InputStream)
Causes issues when Properties stream contains Unicode characters (which are not Unicode-escaped), e.g. when it was saved with store(Writer, String).

Note that the signatures above don't exactly match the ones used by this project; they have to be adjusted.
In case you are interested, I have written a small CodeQL query which can be used to find callables using default Charset or Locale. You can use it on https://lgtm.com to run against public GitHub projects, for example Apache Commons IO. It might however produce some false positives and have some false negatives.

CodeQL query
import java

class CharsetOrLocaleParam extends Parameter {
    CharsetOrLocaleParam() {
        getType().hasName(["Charset", "Locale"])
        or
        // Or is charset name as String
        getType() instanceof TypeString
        and exists(getName().regexpFind("(?i)(charset|encoding)", _, _))
    }
}

predicate usesDefault(Callable c) {
    // Either Javadoc mentions default Charset or Locale
    exists(string javadoc |
        // Join Javadoc lines using " "
        javadoc = concat(JavadocText javadocText |
            javadocText.getJavadoc().getCommentedElement() = c
        |
            javadocText.getText(), " " order by javadocText.getLocation().getStartLine() asc
        )
        and exists(javadoc.regexpFind("(?i)(default|platform)\\s+(locale|charset|encoding)", _, _))
        and not c.getAParameter() instanceof CharsetOrLocaleParam
    )
    // Or overload with Charset or Locale parameter exists
    or exists(Callable overload |
        overload.getDeclaringType() = c.getDeclaringType()
        and overload.getName() = c.getName()
        and overload != c
        and (
            // Either has no parameters
            c.hasNoParameters()
            and overload.getAParameter() instanceof CharsetOrLocaleParam
            or
            // Or has same parameters except for Charset / Locale parameter
            exists (int specificIndex |
                overload.getNumberOfParameters() = c.getNumberOfParameters() + 1
                and overload.getParameter(specificIndex) instanceof CharsetOrLocaleParam
                and forall(int smallerIndex |
                    smallerIndex = [0..specificIndex - 1]
                |
                    c.getParameterType(smallerIndex) = overload.getParameterType(smallerIndex)
                )
                and forall(int largerIndex |
                    largerIndex = [specificIndex + 1..overload.getNumberOfParameters() - 1]
                |
                    c.getParameterType(largerIndex - 1) = overload.getParameterType(largerIndex)
                )
            )
            // Ignore false positives from detection above
            and not c.getAParameter() instanceof CharsetOrLocaleParam
        )
        // Ignore if documentation says default is UTF-8 (e.g. java.nio.file.Files methods)
        and not exists(JavadocText javadocText |
            javadocText.getJavadoc().getCommentedElement() = c
            and exists(javadocText.getText().regexpFind("(?i)UTF(\\-| )8", _, _))
        )
    )
}

// Build signature in the format specified by https://github.com/policeman-tools/forbidden-apis/wiki/SignaturesSyntax
string getQualifiedTypeName(Type t) {
    if t instanceof Array then result = getQualifiedTypeName(t.(Array).getElementType()) + concat(int i | i = [1..t.(Array).getDimension()] | "[]")
    else if t instanceof RefType then result = t.(RefType).getSourceDeclaration().getQualifiedName()
    else result = t.getName()
}

string getParameters(Callable c) {
    result = "(" + concat(Parameter p |
        p = c.getAParameter()
    |
        getQualifiedTypeName(p.getType()), "," order by p.getPosition() asc
    ) + ")"
}

string getQualifiedName(Callable c) {
    exists(string callableName |
        result = c.getDeclaringType().getQualifiedName() + "#" + callableName + getParameters(c)
    |
        c instanceof Method and callableName = c.getName()
        or c instanceof Constructor and callableName = "<init>"
    )
}

from Callable c, string qualifiedName
where
    c.fromSource()
    // Only consider publicly visible callables
    and (c.isProtected() or c.isPublic())
    and forall(RefType t |
        t = c.getDeclaringType().getEnclosingType*()
    |
        t.isProtected() or t.isPublic()
    )
    and not c.getDeclaringType() instanceof TestClass
    and usesDefault(c)
    and qualifiedName = getQualifiedName(c)
select qualifiedName, c order by qualifiedName

I am working on the process to releasea new version with JDK 18 support, so I will look into this today. Adding the signatures should be easy.

Hi,
I stepped through the whole list and added signatures in 1.7 file (the very old ones), but left out the following:

java.util.GregorianCalendar#from(java.time.ZonedDateTime) => reasons you mentioned. Funny detail: I did fall over this one a few days ago when I was working on https://github.com/pgjdbc/pgjdbc/pull/2467
java.io.ByteArrayOutputStream#toString(int) => this is cleary specified what it does. It converts using the high byte. Anyways it is deprecated so you would also hit it when using jdk-deprecated signatures
java.util.Properties.html#load(java.io.InputStream) => this is also clearly specified to use ISO 8859-1. This was on the list back at the time, but this does not fall under category "uses default charset". Same applies for the reverse action to save a properties file.

I also left out the Process readers/writers for the reasons described above. Also with the new UTF-8 as default change in later Java versions those still use the system charset.

Here is the PR: #195
Please have a look at it, if all is fine I would merge and then release version 3.3.

P.S.: If you have some addition, now is last chance!

Looks good, thanks a lot!


Decide on testing approach

Creating this so we have a thread to discuss test issues.

Do we require tests with every pull request? (I vote yes)
Do we do unit test? Functional tests? Integration tests?
How do we do test data? Rails fixtures? Factories? Do we use a gem like Factory Girl?
Any general thoughts on how thorough to be, how granular, etc.

Tentative decisions:

Include tests with every pull request
Tests should cover all key requirements (this is more important than code coverage)
Use both unit and functional tests, especially functional for our purposes; integration tests probably not needed
Use Rails fixtures and/or Factory Girl; maybe in combination as seems appropriate

I was initially leaning towards using just fixtures due to their builtin support. However, after looking more into it I’m learning more towards Factory Girl. I don’t have much experience with either but from what I gathered with fixtures, the test data initialized is uniform between unrelated tests. This can create confusing coupling between seemingly unrelated tests. For example, you might change the test data for one tests only to realize other, "unrelated" tests were making assumptions about the shared data. Factory Girl seems to nicely handle this concern.
Overall, I’m still fine with using whatever tool works best and fixtures may be more ideal in some cases. However, for some of the initial setup code I’m going to add in Factory Girl support as it works nicely with the tests.

Sure, sounds good. I think a very small number of fixtures could be helpful. But do it however seems best to you.
@timcheadle let us know if you have opinions/guidance here!

I've used minitest and rspec extensively, as well as fixtures and FactoryGirl. Since you're new to Rails @dominicbertolino, I'd recommend rspec. It's another DSL to learn, but frankly the community support and documentation FAR exceeds minitest.
I personally like minitest, but fixtures are a bit burdensome to work with unless you design them properly. FactoryGirl is much easier to define and use.
That said, FactoryGirl does result in slower tests, as records are created for every test case instead of loaded in bulk at the outset. I don't think test performance is a primary concern for this app, though.

Great, that was my impression about Factory Girl vs fixtures. As for rspec, I'll check it out more. My initial impression was to favor minitest as it is more bare-bones and I couldn't tell if learning rspec's DSL provided much gain.


Create license-compliant version of the Pile: Enron Emails

This one wil be a nice trial for PII removal

https://huggingface.co/datasets/bigscience-catalogue-lm-data/lm_en_the_pile_enron_emails


Fix failing attempt to calculate bootstraps where only a single EXP prediction is available V2

Fixes #1135 #1136
Developers certificate of origin

[X] I certify that this contribution is covered by the MIT license as defined in our LICENSE and adheres to the Developer Certificate of Origin.

@jthorton replaces previous PR #1137

@jthorton @ijpulidos could I grab a review here?

Fixes #1138 and creates interactive tables with no graphs if we have no experimental data.


suspinfect Table in blood-gas-infect-time.sql

Hello,
I cannot find the query for "suspinfect" table. It is required on line 93 of file blood-gas-infect-time.sql
Thanks

In general there were a few ways to define suspicion of infection and we ended up purely using the prescriptions data. If you find a suspinfect it should be updated to suspinfect_poe. I've done that for most files in https://github.com/alistairewj/sepsis3-mimic/commit/635200f26763dcf370bee8fbdc72aa477c035f10
All adjunct queries are just made available for your reference - caveat emptor!


Java version not locked down

When compiling with a different JDK version you could get "Unsupported major.minor version 52.0". So the plugin should lock down the targetCompatibility and sourceCompatibility settings for a better experience.

Fixed in 024f944215ad44a


Fix punycode deprecation warning

(node:77048) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

punycode is a child dep of various installed packages, so we can't do much to get rid of it. Cancelling for now


ValueError: Value out of range, should be between 0 and 176

Windows 10
Python 3.6
Brats 2013 datase (HG/LG)
Traceback (most recent call last):
File "D:/Darsh/Nirma/Semester 7/Trial/nn-segmentation-for-lar-master/brain_tumor_segmentation_cnn/brain_pipeline.py", line 234, in
save_patient_slices(patients, 'reg')
File "D:/Darsh/Nirma/Semester 7/Trial/nn-segmentation-for-lar-master/brain_tumor_segmentation_cnn/brain_pipeline.py", line 202, in save_patient_slices
a.save_patient(type_modality, patient_num)
File "D:/Darsh/Nirma/Semester 7/Trial/nn-segmentation-for-lar-master/brain_tumor_segmentation_cnn/brain_pipeline.py", line 154, in save_patient
for slice_ix in progress(range(176)):
File "C:\Users\DELL\AppData\Local\conda\conda\envs\tensorflow\lib\site-packages\progressbar\bar.py", line 433, in next
self.update(self.value + 1)
File "C:\Users\DELL\AppData\Local\conda\conda\envs\tensorflow\lib\site-packages\progressbar\bar.py", line 553, in update
% (self.min_value, self.max_value))
ValueError: Value out of range, should be between 0 and 176
Process finished with exit code 1
Above is the error i'm getting after several images are created for the first iteration.

idk why this error is causing but i tackled it by commenting  norm and n4 first and run "reg" only basically i ran one at a time.. so it made patches correctly for me by this trick of running one at a time

@BKShaikh I was able to run brain pipeline in python 2.7 successfully.
However the main program of brain segmentation is giving some errors in the in built python files.

@darshthakkar i'm able to run brain pipeline also training part of segmentation file but i'm stuck in testing phase i'm not able to run that testing phase of this code maybe i'm not giving right format of testing data but getting this error and not able to find out why i'm getting this error

@BKShaikh I'm not sure what the error is about, there seems to be a type mismatch but I think if the author - @naldeborgh7575 reply's, it will be osf some use.
@BKShaikh I'm getting this error when I try to train the model, if you could help, it would be great.

@darshthakkar it looks like that your code is trying to get a wrong image format i think you should only change the range research

@darshthakkar kindly contact me here<EMAIL_ADDRESS>we can discuss it there I can help you in training phase.


无法安装python

红米ac2100在使用opkg安装python3时报错，可能是软件源有问题。。。
root@OpenWrt:~# opkg update
Downloading https://op.supes.top/packages/mipsel/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_custom
Downloading https://op.supes.top/19.07.4/packages/mips_24kc/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_packages2
Downloading https://op.supes.top/snapshots/targets/ramips/mt7621/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_core
Downloading https://op.supes.top/snapshots/packages/mipsel_24kc/base/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_base
Downloading https://op.supes.top/snapshots/packages/mipsel_24kc/freifunk/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_freifunk
Downloading https://op.supes.top/snapshots/packages/mipsel_24kc/luci/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_luci
Downloading https://op.supes.top/snapshots/packages/mipsel_24kc/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_packages
Downloading https://op.supes.top/snapshots/packages/mipsel_24kc/routing/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_routing
Downloading https://op.supes.top/snapshots/packages/mipsel_24kc/telephony/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_telephony
root@OpenWrt:~# opkg install python3
Package libavahi-dbus-support version 0.8-1 has no valid architecture, ignoring.
Package libavahi-nodbus-support version 0.8-1 has no valid architecture, ignoring.
Package libcap version 2.27-1 has no valid architecture, ignoring.
Package libdaemon version 0.14-5 has no valid architecture, ignoring.
Package libdbus version 1.12.12-1 has no valid architecture, ignoring.
Package libexpat version 2.2.9-1 has no valid architecture, ignoring.
Package libgd version 2.2.5-2 has no valid architecture, ignoring.
Package liblz4-1 version 1.9.2-4 has no valid architecture, ignoring.
Package libmpdclient version 2.18-1 has no valid architecture, ignoring.
Package libopus version 1.3.1-2 has no valid architecture, ignoring.
Package libpcre2-16 version 10.32-1 has no valid architecture, ignoring.
Package libpcre version 8.43-1 has no valid architecture, ignoring.
Package libsqlite3-0 version 3310100-1 has no valid architecture, ignoring.
Package libxml2 version 2.9.9-3 has no valid architecture, ignoring.
Package mariadb-common version 10.2.33-1 has no valid architecture, ignoring.
Package pulseaudio-daemon version 12.2-3 has no valid architecture, ignoring.
Package python3 version 3.7.9-1 has no valid architecture, ignoring.
Package python version 2.7.18-3 has no valid architecture, ignoring.
Package sbc version 1.4-2 has no valid architecture, ignoring.
Package shine version 3.1.1-1 has no valid architecture, ignoring.
Package strongswan version 5.8.2-2 has no valid architecture, ignoring.
Package yajl version 2.1.0-2 has no valid architecture, ignoring.
Package alsa-lib version 1.1.8-1 has no valid architecture, ignoring.
Package avahi-dbus-daemon version 0.8-1 has no valid architecture, ignoring.
Package boost-system version 1.71.0-6 has no valid architecture, ignoring.
Package boost version 1.71.0-6 has no valid architecture, ignoring.
Package coreutils-install version 8.30-2 has no valid architecture, ignoring.
Package coreutils version 8.30-2 has no valid architecture, ignoring.
Package dbus version 1.12.12-1 has no valid architecture, ignoring.
Package gcc version 7.4.0-5 has no valid architecture, ignoring.
Package glib2 version 2.58.3-5 has no valid architecture, ignoring.
Package libacl version 2.2.53-1 has no valid architecture, ignoring.
Package libattr version 2.4.48-1 has no valid architecture, ignoring.
Package libavahi-client version 0.8-1 has no valid architecture, ignoring.
Package libavahi-dbus-support version 0.8-1 has no valid architecture, ignoring.
Package libavahi-nodbus-support version 0.8-1 has no valid architecture, ignoring.
Package libcap version 2.27-1 has no valid architecture, ignoring.
Package libcares version 1.15.0-4 has no valid architecture, ignoring.
Package libdaemon version 0.14-5 has no valid architecture, ignoring.
Package libdb47 version <IP_ADDRESS>.NC-5 has no valid architecture, ignoring.
Package libdbus version 1.12.12-1 has no valid architecture, ignoring.
Package libev version 4.25-1 has no valid architecture, ignoring.
Package libevdev version 1.6.0-1 has no valid architecture, ignoring.
Package libexpat version 2.2.9-1 has no valid architecture, ignoring.
Package libfaad2 version 2.9.2-1 has no valid architecture, ignoring.
Package libffmpeg-audio-dec version 3.4.7-3 has no valid architecture, ignoring.
Package libffmpeg-full version 3.4.7-3 has no valid architecture, ignoring.
Package libffmpeg-mini version 3.4.7-3 has no valid architecture, ignoring.
Package libflac version 1.3.3-1 has no valid architecture, ignoring.
Package libgcrypt version 1.8.5-1 has no valid architecture, ignoring.
Package libgd version 2.2.5-2 has no valid architecture, ignoring.
Package libgnutls version 3.6.15-1 has no valid architecture, ignoring.
Package libgpg-error version 1.36-3 has no valid architecture, ignoring.
Package libid3tag version 0.15.1b-4 has no valid architecture, ignoring.
Package libidn2 version 2.0.5-1 has no valid architecture, ignoring.
Package libjpeg version 9c-2 has no valid architecture, ignoring.
Package liblz4-1 version 1.9.2-4 has no valid architecture, ignoring.
Package libmad version 0.15.1b-5 has no valid architecture, ignoring.
Package libmariadb version 10.2.33-1 has no valid architecture, ignoring.
Package libmicrohttpd-no-ssl version 0.9.62-3 has no valid architecture, ignoring.
Package libmicrohttpd-ssl version 0.9.62-3 has no valid architecture, ignoring.
Package libmms version 0.6.4-4 has no valid architecture, ignoring.
Package libmosquitto-nossl version 1.6.12-1 has no valid architecture, ignoring.
Package libmosquitto-ssl version 1.6.12-1 has no valid architecture, ignoring.
Package libmpdclient version 2.18-1 has no valid architecture, ignoring.
Package libmpg123 version 1.25.13-2 has no valid architecture, ignoring.
Package libnss version 3.55-1 has no valid architecture, ignoring.
Package libopus version 1.3.1-2 has no valid architecture, ignoring.
Package libpcre2-16 version 10.32-1 has no valid architecture, ignoring.
Package libpcre version 8.43-1 has no valid architecture, ignoring.
Package libpng version 1.6.37-3 has no valid architecture, ignoring.
Package libshout version 2.4.3-1 has no valid architecture, ignoring.
Package libsndfile version 2019-04-21-25824cb9-1 has no valid architecture, ignoring.
Package libsodium version 1.0.18-1 has no valid architecture, ignoring.
Package libsoxr version 0.1.3-1 has no valid architecture, ignoring.
Package libsqlite3-0 version 3310100-1 has no valid architecture, ignoring.
Package libudev-fbsd version 20171216-1 has no valid architecture, ignoring.
Package libunbound-heavy version 1.11.0-2 has no valid architecture, ignoring.
Package libunistring version 0.9.10-1 has no valid architecture, ignoring.
Package libupnp version 1.8.7-2 has no valid architecture, ignoring.
Package libuv1 version 1.40.0-1 has no valid architecture, ignoring.
Package libuwsc-mbedtls version 3.3.2-1 has no valid architecture, ignoring.
Package libuwsc-nossl version 3.3.2-1 has no valid architecture, ignoring.
Package libuwsc-openssl version 3.3.2-1 has no valid architecture, ignoring.
Package libuwsc-wolfssl version 3.3.2-1 has no valid architecture, ignoring.
Package libvorbis version 1.3.7-1 has no valid architecture, ignoring.
Package libvorbisidec version 1.0.3-20180319-1 has no valid architecture, ignoring.
Package libwebsockets-openssl version 3.1.0-1 has no valid architecture, ignoring.
Package libwrap version 7.6-2 has no valid architecture, ignoring.
Package libxml2 version 2.9.9-3 has no valid architecture, ignoring.
Package libzmq-curve version 4.3.3-2 has no valid architecture, ignoring.
Package libzmq-nc version 4.3.3-2 has no valid architecture, ignoring.
Package mariadb-common version 10.2.33-1 has no valid architecture, ignoring.
Package mariadb-server-base version 10.2.33-1 has no valid architecture, ignoring.
Package musl-fts version 1.2.7-1 has no valid architecture, ignoring.
Package nspr version 4.27-1 has no valid architecture, ignoring.
Package pulseaudio-daemon version 12.2-3 has no valid architecture, ignoring.
Package python-defusedxml version 0.6.0-2 has no valid architecture, ignoring.
Package python-et_xmlfile version 1.0.1-1 has no valid architecture, ignoring.
Package python-jdcal version 1.4.1-1 has no valid architecture, ignoring.
Package python3-codecs version 3.7.9-1 has no valid architecture, ignoring.
Package python3-light version 3.7.9-1 has no valid architecture, ignoring.
Package python3-logging version 3.7.9-1 has no valid architecture, ignoring.
Package python3-openssl version 3.7.9-1 has no valid architecture, ignoring.
Package python3-pytz version 2019.3-1 has no valid architecture, ignoring.
Package python3-urllib version 3.7.9-1 has no valid architecture, ignoring.
Package python3-xml version 3.7.9-1 has no valid architecture, ignoring.
Package python3 version 3.7.9-1 has no valid architecture, ignoring.
Package python version 2.7.18-3 has no valid architecture, ignoring.
Package sbc version 1.4-2 has no valid architecture, ignoring.
Package shine version 3.1.1-1 has no valid architecture, ignoring.
Package strongswan version 5.8.2-2 has no valid architecture, ignoring.
Package yajl version 2.1.0-2 has no valid architecture, ignoring.
Package alsa-lib version 1.1.8-1 has no valid architecture, ignoring.
Package avahi-dbus-daemon version 0.8-1 has no valid architecture, ignoring.
Package boost-system version 1.71.0-6 has no valid architecture, ignoring.
Package boost version 1.71.0-6 has no valid architecture, ignoring.
Package coreutils-install version 8.30-2 has no valid architecture, ignoring.
Package coreutils version 8.30-2 has no valid architecture, ignoring.
Package dbus version 1.12.12-1 has no valid architecture, ignoring.
Package gcc version 7.4.0-5 has no valid architecture, ignoring.
Package glib2 version 2.58.3-5 has no valid architecture, ignoring.
Package libacl version 2.2.53-1 has no valid architecture, ignoring.
Package libattr version 2.4.48-1 has no valid architecture, ignoring.
Package libavahi-client version 0.8-1 has no valid architecture, ignoring.
Package libavahi-dbus-support version 0.8-1 has no valid architecture, ignoring.
Package libavahi-nodbus-support version 0.8-1 has no valid architecture, ignoring.
Package libcap version 2.27-1 has no valid architecture, ignoring.
Package libcares version 1.15.0-4 has no valid architecture, ignoring.
Package libdaemon version 0.14-5 has no valid architecture, ignoring.
Package libdb47 version <IP_ADDRESS>.NC-5 has no valid architecture, ignoring.
Package libdbus version 1.12.12-1 has no valid architecture, ignoring.
Package libev version 4.25-1 has no valid architecture, ignoring.
Package libevdev version 1.6.0-1 has no valid architecture, ignoring.
Package libexpat version 2.2.9-1 has no valid architecture, ignoring.
Package libfaad2 version 2.9.2-1 has no valid architecture, ignoring.
Package libffi version 3.3-2 has no valid architecture, ignoring.
Package libffmpeg-audio-dec version 3.4.7-3 has no valid architecture, ignoring.
Package libffmpeg-full version 3.4.7-3 has no valid architecture, ignoring.
Package libffmpeg-mini version 3.4.7-3 has no valid architecture, ignoring.
Package libflac version 1.3.3-1 has no valid architecture, ignoring.
Package libgcrypt version 1.8.5-1 has no valid architecture, ignoring.
Package libgd version 2.2.5-2 has no valid architecture, ignoring.
Package libgnutls version 3.6.15-1 has no valid architecture, ignoring.
Package libgpg-error version 1.36-3 has no valid architecture, ignoring.
Package libid3tag version 0.15.1b-4 has no valid architecture, ignoring.
Package libidn2 version 2.0.5-1 has no valid architecture, ignoring.
Package libjpeg version 9c-2 has no valid architecture, ignoring.
Package liblz4-1 version 1.9.2-4 has no valid architecture, ignoring.
Package libmad version 0.15.1b-5 has no valid architecture, ignoring.
Package libmariadb version 10.2.33-1 has no valid architecture, ignoring.
Package libmicrohttpd-no-ssl version 0.9.62-3 has no valid architecture, ignoring.
Package libmicrohttpd-ssl version 0.9.62-3 has no valid architecture, ignoring.
Package libmms version 0.6.4-4 has no valid architecture, ignoring.
Package libmosquitto-nossl version 1.6.12-1 has no valid architecture, ignoring.
Package libmosquitto-ssl version 1.6.12-1 has no valid architecture, ignoring.
Package libmpdclient version 2.18-1 has no valid architecture, ignoring.
Package libmpg123 version 1.25.13-2 has no valid architecture, ignoring.
Package libnss version 3.55-1 has no valid architecture, ignoring.
Package libopus version 1.3.1-2 has no valid architecture, ignoring.
Package libpcre2-16 version 10.32-1 has no valid architecture, ignoring.
Package libpcre version 8.43-1 has no valid architecture, ignoring.
Package libpng version 1.6.37-3 has no valid architecture, ignoring.
Package libshout version 2.4.3-1 has no valid architecture, ignoring.
Package libsndfile version 2019-04-21-25824cb9-1 has no valid architecture, ignoring.
Package libsodium version 1.0.18-1 has no valid architecture, ignoring.
Package libsoxr version 0.1.3-1 has no valid architecture, ignoring.
Package libsqlite3-0 version 3310100-1 has no valid architecture, ignoring.
Package libudev-fbsd version 20171216-1 has no valid architecture, ignoring.
Package libunbound-heavy version 1.11.0-2 has no valid architecture, ignoring.
Package libunistring version 0.9.10-1 has no valid architecture, ignoring.
Package libupnp version 1.8.7-2 has no valid architecture, ignoring.
Package libuv1 version 1.40.0-1 has no valid architecture, ignoring.
Package libuwsc-mbedtls version 3.3.2-1 has no valid architecture, ignoring.
Package libuwsc-nossl version 3.3.2-1 has no valid architecture, ignoring.
Package libuwsc-openssl version 3.3.2-1 has no valid architecture, ignoring.
Package libuwsc-wolfssl version 3.3.2-1 has no valid architecture, ignoring.
Package libvorbis version 1.3.7-1 has no valid architecture, ignoring.
Package libvorbisidec version 1.0.3-20180319-1 has no valid architecture, ignoring.
Package libwebsockets-openssl version 3.1.0-1 has no valid architecture, ignoring.
Package libwrap version 7.6-2 has no valid architecture, ignoring.
Package libxml2 version 2.9.9-3 has no valid architecture, ignoring.
Package libzmq-curve version 4.3.3-2 has no valid architecture, ignoring.
Package libzmq-nc version 4.3.3-2 has no valid architecture, ignoring.
Package mariadb-common version 10.2.33-1 has no valid architecture, ignoring.
Package mariadb-server-base version 10.2.33-1 has no valid architecture, ignoring.
Package musl-fts version 1.2.7-1 has no valid architecture, ignoring.
Package nspr version 4.27-1 has no valid architecture, ignoring.
Package pulseaudio-daemon version 12.2-3 has no valid architecture, ignoring.
Package python-defusedxml version 0.6.0-2 has no valid architecture, ignoring.
Package python-et_xmlfile version 1.0.1-1 has no valid architecture, ignoring.
Package python-jdcal version 1.4.1-1 has no valid architecture, ignoring.
Package python3-asyncio version 3.7.9-1 has no valid architecture, ignoring.
Package python3-base version 3.7.9-1 has no valid architecture, ignoring.
Package python3-codecs version 3.7.9-1 has no valid architecture, ignoring.
Package python3-email version 3.7.9-1 has no valid architecture, ignoring.
Package python3-light version 3.7.9-1 has no valid architecture, ignoring.
Package python3-logging version 3.7.9-1 has no valid architecture, ignoring.
Package python3-openssl version 3.7.9-1 has no valid architecture, ignoring.
Package python3-pytz version 2019.3-1 has no valid architecture, ignoring.
Package python3-urllib version 3.7.9-1 has no valid architecture, ignoring.
Package python3-xml version 3.7.9-1 has no valid architecture, ignoring.
Package python3 version 3.7.9-1 has no valid architecture, ignoring.
Package python version 2.7.18-3 has no valid architecture, ignoring.
Package sbc version 1.4-2 has no valid architecture, ignoring.
Package shine version 3.1.1-1 has no valid architecture, ignoring.
Package strongswan version 5.8.2-2 has no valid architecture, ignoring.
Package yajl version 2.1.0-2 has no valid architecture, ignoring.
Unknown package 'python3'.
Collected errors:
 * opkg_install_cmd: Cannot install package python3.
root@OpenWrt:~#

疯狂提示has no valid architecture, ignoring.,我好懵啊。。。

目测python3的ipk包在openwrt_packages2 https://op.supes.top/19.07.4/packages/mips_24kc/packages 里面

更新到最新版固件即可解决,

更新到最新版固件即可解决,

成功解决问题！谢谢


cleaning up variable declarations.

Moving variable declaration to the outside of inner blocks when they are also referenced outside the block.

Is there a specific reason why this is preferable?

I think it is a code legibility issue.  When you declare a variable inside a for loop most people assume the variable is only scoped /used inside the for loop. In this case the variables are also referenced outside the for loops since they are being returned so I moved the declarations outside the for loops.

Thanks for the contribution, but I prefer the brief form. As far as I know, it has no stability or speed ramifications, and I haven't seen any bug reports or other notes that it's confusing before this one.


Add support for server-side events season

Duck season

231 tests were run on 18d2979e. ⚠ 5 Flaked. View Full Report ↗

⚠ 5 Flakes

Test Name
Failure Summary
Logs

[chromium] should return list of users correctly.

Logs ↗

[chromium] should show the privacy policy correctly.

Logs ↗

[chromium] should display error message for invalid login correctly.

Logs ↗

[chromium] should login with credentials correctly correctly.

Logs ↗

Test$1ServiceUnavailable
failure$1message: Failedfailure$1text: === RUN   Test$1ServiceUnavailable    api$1test.go:18: Service unavailable--- FAIL: Test$1ServiceUnavai...
Logs ↗

settings


Fixed compile errors and warnings.

Was unable to build the project. Had to add a few casts and remove unused headers. With this patch I am able to build (and run) with platformio.

Thanks


Add amplify enhanced action

Related issue https://github.com/scylladb/sphinx-scylladb-theme/issues/540
How it works
See Amplify enhanced action README.
Test this pull request
The workflow will not start running until it is merged on the default branch.
Once we merge this pull request, I'll submit separate pull requests to trigger and test the new action.

@tzach @annastuchlik Could you please merge it? Thanks!

I've no permissions. Let's wait for @tzach.


8 bit PCM Wav Audio Distorted

According to the errormessage printed out when trying to play unsupported audio files LövePotion supports 16 bit and 8 bit PCM wav files.
But trying to play 8 bit PCM wav files results in broken/distorted audio

LövePotion  on the 3DS can only support normal wav files as of now.
Try converting your wav that your having issues with to an .ogg
http://audio.online-convert.com/convert-to-ogg

No worries about that, they are allready 16 bit PCM.
I just thought using 8 bit PCM would work and could save half the file/memory size

Actually, LövePotion should support 8bit PCM, as the audio playing code is almost the same as ctrµLua's one (which I made).
But now I realize I only tested with 16bit PCM files on ctrµLua :/
Unfortunately I don't have my 3DS now, but I'll look into this when I can.
Could you provide one file which plays distorted ? Thanks.

I haven't done much testing either (I hope you don't mind me taking some code, I was having trouble getting audio working with dsp) but I'll look into it aswell

Any 8bit PCM file I tested so far has distorted sound.
But here you go:
jazz.zip

32bit too.


Bedrock Support

Support for Amazon Bedrock Models
Chat Models from the AWS Bedrock collection can now be used for the same usecases.
Updated existing SimpleServer to handle Bedrock provider as well, but it's not pretty. A lot of the existing code of SimpleServer and the ChatSessions have been built around concepts introduced by the openai4j library, but do not match another provider.
Bedrock came without any integration or abstractions, so I had to build the function definition and calling into the regular prompt communication with the LLM.
In order to run an Example with Bedrock, run the SimpleServer with --example=BEDROCK. Also add the environment variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.
Implementation Details

Made separation between classes in com.datasqrl.ai.models.openai and  com.datasqrl.ai.models.groq apparent at class name level
Added com.datasqrl.ai.models.bedrock Classes to simulate the domain objects brought by the openai4j library
Added BedrockTokenCounter in order to keep the class separation, although it's the same as the GroqTokenCounter. Think of merging these two into a HuggingFaceTokenCounter in the future
Added BEDROCK example in Examples. It contains the system prompt and instructions on function calls and function responses, for the raw llama prompt api
Since the Llama3 raw communication mode expects special delimiters for messages, added an interface ChatMessageEncoder and a concrete Llama3MessageEncoder implementation. I have used it at the application level just for the communication with the LLM, so that the GenericChatMessages do not include these special delimiters.
The system prompt was extended to include all functions and instructions on how to call them. I am not sure the calling syntax is standard, so please give me your opinion on that.
The function call to string in the BedrockChatSession was changed to have the same format as the function calls described in the system prompt

@mbroecheler Ready for review :)


Await editor.action.triggerSuggest

The problem: currently its really hard to test accepting completions from completion widget, as its not possible from extension host to know when completion widget is here and ready to accept suggestions, which requires some weird workarounds that even don't work on some slow machines
I don't see a reason to not await the fact that completion widget is visible.
Also this:
https://github.com/microsoft/vscode/issues/23814#issuecomment-291919365

it would be nice if after resolving editor.action.triggerSuggest promise it was already ready to accept the suggestion.

The extension code I used to test this:
vscode.commands.registerCommand('testCommand', async () => {
  await vscode.commands.executeCommand('editor.action.triggerSuggest'); // previously adding await had no effect
  await vscode.commands.executeCommand('acceptSelectedSuggestion');
  // now test completion is applied, even if it takes provider 1.5s to resolve it
});

vscode.languages.registerCompletionItemProvider('typescript', {
  async provideCompletionItems() {
    await new Promise(resolve => {
      setTimeout(resolve, 1500);
    });
    return [
      {
        label: 'test',
        sortText: '!'
      }
    ];
  },
});

I believe its also possible to add a test for that fact that code above works properly, but there are dozens of completions test files and I'm not sure where it should be done.
If you don't want to wait until completion is ready (old behavior), just ignore the promise (don't add await).
WDYT? @jrieken
fixes #177750

Hey, can you elaborate or maybe assign someone else to work on it? I just don't see a milestone and wonder are there any plans on it? Since it seems to be working fine why it can't be just merged?

Sorry, this has been snowplowed a few times and again will be moved. This is largely to a lack of time but also because the change is questionable in what it promises it does
These changes do not always align with your statement _"I don't see a reason to not await the fact that completion widget is visible." This change awaits triggering, asking providers, and building the model but there is no guarantee that the suggest widget will show after this. It has it's own logic to decide when to show and hide so I don't feel very comfortable in say'ing awaiting this event guarantees that the widget shows.


Reload Resources from other csproj

Hi,
I used this package and it works correctly.
But I have other projects in my solution, and these do not reload the resources dynamically.
Is there a solution for this case?
Thanks

Certainly! Here's a more polished and professional version of the text:
Hi,
Could you please provide more context and technical details regarding your issue? It would be very helpful if you could share a reproduction of the problem. Your current description is quite vague and doesn't offer enough information for me to assist you.
Thank you.

Hi,
Sorry for the delay in replying.
I'm trying to make a demo project in the next few days.
Thanks

Hi @Pinox,
You need to add the following code to the DynamicCulture.Web project:
builder.Services.AddLocalization();
builder.Services.TryAddSingleton<ILocalizationService, LocalizationService>();
builder.Services.TryAddScoped<LocalizationLocalStorageManager>();
builder.Services.TryAddScoped<LocalizationNavigatorManager>();
builder.Services.TryAddScoped<LocalizationQueryManager>();
builder.Services.TryAddScoped<LocalizationContextManager>();
builder.Services.TryAddScoped<LocalizationDynamicMiddleware>();

Unfortunately, the WebApp template requires these services to be registered in both places, for DynamicCulture.Web.Client it's done through AddLocalizationDynamic.
While I see that the Localizer["About"] in the AppBar changes when switching languages, I haven't tested this solution in a WebApp. It was primarily designed for standalone WASM projects and has only been battle-tested in my startup projects using this template. Using WebApp as is at your own risk. I may look into officially supporting WebApp later.

 Thanks so much !!
For anyone that is interested here is the source for the full working copy tested on
Android , WinUI3 and WASM.
https://1drv.ms/u/s!AkcH3KVxOeYGvspdctvubjVyq7TqNg?e=SPcDCv
All working like a charm !!

Well after some tests it turns out that the resources load well finally, it is rather a problem of refresh depending on where I place the component.
For example in my demo, if it is placed in the appBar, it does nothing.
If we use the one that is in the Home page, the resources of this same page are modified, but not that of the NavBar as long as I do not interact with it.
I still put the example, but I managed to get by with StateHasChanged on the components that I want to refresh.
Thanks.
DynamicCultureMultiProjects.zip

I still put the example, but I managed to get by with StateHasChanged on the components that I want to refresh.

This is the expected behavior. You need to call StateHasChanged on page / component that require translation.

If we use the one that is in the Home page, the resources of this same page are modified, but not that of the NavBar

It works on the same page because when you change language, Blazor automatically refreshes the page / component as part of its default behavior when an EventCallback is triggered. However, other pages / components are not tracked.
This is why the Blazor.WebAssembly.DynamicCulture package includes the LanguageTrackProvider. It tracks language changes and refreshes the need parts that use this provider: https://github.com/ScarletKuro/Blazor.WebAssembly.DynamicCulture/blob/master/docs/Blazor-wasm-localization.md#add-components
Since you are not using Blazor.WebAssembly.DynamicCulture, you'll need to handle this manually.

Thanks @ScarletKuro
I just loaded the localstorage value on startup into culture and that solved the issue ;))
CultureInfo.DefaultThreadCurrentUICulture = new CultureInfo( from localstorage )
When I do above my language control dropdown is also set to the correct value.
So happy with your solution ;))

I am closing this issue, as I believe all questions have been answered.


[GSSoC'23] Added Snake Game..

Added a Snake Game.
Varies UI states of My Snake Game are:

Demo of Snake Game is:
https://github.com/ssitvit/Games-and-Go/assets/117664019/f11adce1-f4ed-4955-afa2-cd269ab6a034
Consider My Pull Request and Try to merge.

Please Create new PRs for this because it contains conflict issue.


Improve copy on email confirmation page

Currently, the email confirmation page for creating a new organization or new user (accounts/send_confirm/) looks like this (without the dev environment banner):

We should update the copy on this page to make it more clear what's going on, and why you need to check your email. New copy:

Confirm your email address
To complete registration, check your email account<EMAIL_ADDRESS>for a confirmation email from Zulip.
If you don't see a confirmation email in your Inbox or Spam folder, we can resend it.

@sahil839 Would you be up for taking care of this one?

Sure.


VSCode Remote Slow Ring ECONNREFUSED

Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition. Please fill out all the fields! Issues with missing or incomplete issue templates will be closed.
If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.
Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues.  Please direct all Windows crashes and security issues to<EMAIL_ADDRESS> Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".\
See our contributing instructions for assistance.
Please fill out the below information:

Your Windows build number:  (Type ver at a Windows Command Prompt)
Microsoft Windows [Version 10.0.19018.1]

What you're doing and what's happening:  (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)

VSCode occasionally gets in an error state where it can't connect to WSL. I have to reboot to resolve this, as the behavior is seemingly non deterministic. This is described in the issue I filed against the VSCode Remote Repo: https://github.com/microsoft/vscode-remote-release/issues/1841
Please refer there for screenshots and descriptions, as other users have posted additional information there. In short, the VSCode Remote extension is occasionally failing to be able to connect to WSL2.
The maintainers there suggested this is likely a WSL bug and should be filed here.

What's wrong / what should be happening instead:

I expect that VSCode should always be able to connect to WSL without error.

Strace of the failing command, if applicable:  (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here).

For WSL launch issues, please collect detailed logs.

I am going to collect networking logs via Feedback hub momentarily.

The problem is also happening on Microsoft Windows [Version 10.0.19025.1]

This also happens on fast ring on Microsoft Windows [Version 10.0.19037.1]

While I have the same issue I am able to get rid of it by simply restarting WSL using PowerShell.
Powershell command: wsl --shutdown; wsl No need to restart my system.

Happened to me on OS build 19536.1000, but rebooting resolved it.  A Heisenbug, it seems.

Happened to me two times on 19536.1000 (slow ring), this is the log from one of the times:
[2019-12-23 13:58:53.432] Resolving wsl+Ubuntu, resolveAttempt: 1
[2019-12-23 13:58:53.489] Starting VS Code Server inside WSL (Ubuntu)
[2019-12-23 13:58:53.489] Extension version: 0.41.6, Windows build: 19536. Multi distro support: available. WSL path support: enabled
[2019-12-23 13:58:53.644] Probing if server is already installed: C:\WINDOWS\System32\wsl.exe -d Ubuntu -e sh -c "[ -d ~/.vscode-server/bin/26076a4de974ead31f97692a0d32f90d735645c0 ] && printf found || ([ -f /etc/alpine-release ] && printf alpine-; uname -m)"
[2019-12-23 13:58:53.766] Probing result: found
[2019-12-23 13:58:53.766] Server install found in WSL
[2019-12-23 13:58:53.766] Launching C:\WINDOWS\System32\wsl.exe -d Ubuntu sh -c '"$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" 26076a4de974ead31f97692a0d32f90d735645c0 stable .vscode-server 0  ' in c:\Users\basto\.vscode\extensions\ms-vscode-remote.remote-wsl-0.41.6
[2019-12-23 13:58:53.945] Setting up server environment: Looking for /home/bastos/.vscode-server/server-env-setup. Not found.
[2019-12-23 13:58:53.945] WSL version: 4.19.81-microsoft-standard Ubuntu
[2019-12-23 13:58:53.946] WSL2-shell-PID: 16332
[2019-12-23 13:58:53.946] Starting server: /home/bastos/.vscode-server/bin/26076a4de974ead31f97692a0d32f90d735645c0/server.sh  --port=0 --enable-remote-auto-shutdown
[2019-12-23 13:58:54.254]
[2019-12-23 13:58:54.254]
[2019-12-23 13:58:54.254] *
[2019-12-23 13:58:54.254] * Visual Studio Code Server
[2019-12-23 13:58:54.254] *
[2019-12-23 13:58:54.254] * Reminder: You may only use this software with Visual Studio family products,
[2019-12-23 13:58:54.254] * as described in the license https://aka.ms/vscode-remote/license
[2019-12-23 13:58:54.254] *
[2019-12-23 13:58:54.254]
[2019-12-23 13:58:54.254]
[2019-12-23 13:58:54.254] IP Address: 172.27[[REDACTED]]
[2019-12-23 13:58:54.254] Extension host agent listening on 35191
[2019-12-23 13:58:54.254]
[2019-12-23 13:58:54.254]
[2019-12-23 13:58:54.254] [10:58:53] Extension host agent started.
[2019-12-23 13:58:54.256] WSL resolver response: ::1:35191
[2019-12-23 13:58:54.256] To debug connection issues, open a local browser on http://[::1]:35191/version

Hi am also experiencing similar issue.
Failed to fetch remote environment.
Failed to connect to the remote extension host server (Error: connect ECONNREFUSED ::1:40855)
Vs Code insiders:
Version: 1.42.0-insider (user setup)
Commit: 7c0095ee2d064033fc13184127a9adc603454729
Date: 2019-12-20T07:57:35.999Z
Electron: 6.1.6
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.19536
Using Windows Terminal (preview) when i switch to Ubuntu shell and try and start VS code insiders with code-insiders . VS Code insiders opens but I get the error above.  Ran powershell command as admin   wsl --shutdown; wsl and the error stopped.  But on closing and reopening VS Code insiders the error returns.
Output of Remote-WSL: show log
[2019-12-27 15:58:41.153] WSL2-shell-PID: 3806
[2019-12-27 15:58:41.153] Starting server: /home/dan/.vscode-server-insiders/bin/7c0095ee2d064033fc13184127a9adc603454729/server.sh  --port=0 --enable-remote-auto-shutdown --disable-telemetry
[2019-12-27 15:58:41.772]
[2019-12-27 15:58:41.772]
[2019-12-27 15:58:41.772] *
[2019-12-27 15:58:41.772] * Visual Studio Code Server
[2019-12-27 15:58:41.772] *
[2019-12-27 15:58:41.772] * Reminder: You may only use this software with Visual Studio family products,
[2019-12-27 15:58:41.772] * as described in the license https://aka.ms/vscode-remote/license
[2019-12-27 15:58:41.772] *
[2019-12-27 15:58:41.772]
[2019-12-27 15:58:41.772]
[2019-12-27 15:58:41.772] IP Address: 172.31***redacted***
[2019-12-27 15:58:41.772] Extension host agent listening on 40855
[2019-12-27 15:58:41.772]
[2019-12-27 15:58:41.772]
[2019-12-27 15:58:41.772] [10:58:41] Extension host agent started.
[2019-12-27 15:58:41.774] WSL resolver response: ::1:40855
[2019-12-27 15:58:41.774] To debug connection issues, open a local browser on http://[::1]:40855/version

While I have the same issue I am able to get rid of it by simply restarting WSL using PowerShell.
PowerShell command: wsl --shutdown; wsl No need to restart my system.

Thank a lot you suggestion helped me solve this issue.

/dupe #4636


Fix directory access when the running app has the All files access permission

Fixes https://github.com/godotengine/godot/issues/66571
3.x version

Thanks!

Cherry-picked for 4.0.2.


Fix bug when setting KS_GUI=1

Thanks to @Fryguy for educating me on ERB :+1:

@Fryguy This did not make it into Euwe branch. Please label euwe/yes or euwe/no, as appropriate.


Fixing of grammar and better queries

This PR addresses a couple of issues, both objective and subjective, where the grammar would fail on certain files in the awslabs/smithy repo, and where I found there to be inconsistent/improper grammar structure. I tried to adhere to the IDL as much as possible, as weird as it was as times.
I also fixed the queries up to more properly reflect nvim-treesitter's standards. I am hoping if this gets merged then this can be added to nvim-treesitter. I am willing to maintain the parsers/grammar.
In addition, I added a test, some examples, and a CI action to run tests.

Should I not hear from a maintainer for a while, or for whatever reason this wouldn't be merged, I would ideally add my fork to nvim-treesitter then rather than this

Should I not hear from a maintainer for a while

On a related note, @amaanq, I really don't understand this:

You created an issue on a repo asking to maintain it, even though it's clear there isn't much activity or backlog - not something that requires extra maintenance
You submit a PR and immediately (within 2 minutes of opening the PR) set an ultimatum that either this PR gets merged, or you submit your own fork.

I don't understand what gave you the impression that this repo is unmaintained, given that the PR to nvim-treesitter is handled by another person and is in progress.
More than happy to work with you on this PR and addition to nvim-treesitter, but this ultimatum tone is absolutely unnecessary.

I don't understand what gave you the impression that this repo is unmaintained, given that the PR to nvim-treesitter is handled by another person and is in progress.

The PR is pretty stale with zero activity from the person who submitted it

More than happy to work with you on this PR and addition to nvim-treesitter, but this ultimatum tone is absolutely unnecessary.

I agree, I apologize for my tone, in my head your response to my issue seemed like a denial for me to be a maintainer, which I understand as there is not much maintenance needed on this. So again, I do apologize for that.
That being said, either way I would love to get this added into nvim-treesitter :slightly_smiling_face:

do you mind if I add a CI and discord badge in the docs? like so:

with the latest commit escape sequences can be differentiated with a colorscheme like so

do you mind if I add a CI and discord badge in the docs? like so:
In my grammars I also have a publish action that is run on every tagged commit. See here: https://github.com/amaanq/tree-sitter-kdl/blob/f83f3943568c7e7b4f5e0de1b04d722223bd4d80/.github/workflows/publish.yml
So if a commit is tagged v0.4.0 or whatever and pushed, this CI action will be run then and only then, all you'd have to do is sync the git tag with the cargo and npm manifest versions.
This would be a good idea to add but totally your choice

@keynmol Thoughts on this? Seems like this is the last topic to discuss/resolve

@keynmol Thoughts on this? Seems like this is the last topic to discuss/resolve

Badges - go ahead ✅
With regards to publishing - I never really considered that (I also maintain tree-sitter-scala, which has a lot more users) - do you have any examples of applications/libraries that use NPM packages or crates?
I'd be happy to look into setting up the secrets for publishing, but it will be lower on priority list.

@keynmol Thoughts on this? Seems like this is the last topic to discuss/resolve

Badges - go ahead white_check_mark
With regards to publishing - I never really considered that (I also maintain tree-sitter-scala, which has a lot more users) - do you have any examples of applications/libraries that use NPM packages or crates?
I'd be happy to look into setting up the secrets for publishing, but it will be lower on priority list.

Those that want to write their own editor or tool to integrate tree-sitter parsing with tend to use the npm package or rust crate instead of the bare cli; I've had requests for publishing mine before as someone wanted that programmatic usage out of the parser.

In the current state it looks great - I'm especially impressed with the highlight queries and CI, thank you so much!

Thanks, glad I could contribute :)
For #8, I'm assuming that's so that the large diffs aren't rendered in someone's PR/commits? The .gitattributes file solves exactly that. If you mean in case someone forgets to generate when making changes, then of course I'm all for that, and that'd be a good idea to add to my parsers too...good idea :slightly_smiling_face:

For #8, I'm assuming that's so that the large diffs aren't rendered in someone's PR/commits? The .gitattributes file solves exactly that. If you mean in case someone forgets to generate when making changes, then of course I'm all for that, and that'd be a good idea to add to my parsers too...good idea 🙂

It's mostly for grammars with lots of traffic - you can read justification here: https://github.com/tree-sitter/tree-sitter-scala/issues/85
Basically it's to

Reduce PR conflicts - we had lots of PRs in parallel and they can be automatically resolved by git only on smaller, simpler files (like tests and grammar.js)
Test in a pristine (ish) CI environment - no user checked-in C code
If user checks in C code, verify that CI produces exactly the same one
(additionally) we also verify that the queries in nvim-treesitter aren't broken by the PRs in the grammar repo - to avoid breaking the users

IMO that's just better way to vendor C code generated by parsers, and make reviews easier as well. I shiver uncontrollably when I see diffs like this

and would rather set up a process where nobody has to check that the C code is correct :)

For #8, I'm assuming that's so that the large diffs aren't rendered in someone's PR/commits? The .gitattributes file solves exactly that. If you mean in case someone forgets to generate when making changes, then of course I'm all for that, and that'd be a good idea to add to my parsers too...good idea 🙂

It's mostly for grammars with lots of traffic - you can read justification here: https://github.com/tree-sitter/tree-sitter-scala/issues/85
Basically it's to

Reduce PR conflicts - we had lots of PRs in parallel and they can be automatically resolved by git only on smaller, simpler files (like tests and grammar.js)
Test in a pristine (ish) CI environment - no user checked-in C code
If user checks in C code, verify that CI produces exactly the same one
(additionally) we also verify that the queries in nvim-treesitter aren't broken by the PRs in the grammar repo - to avoid breaking the users

IMO that's just better way to vendor C code generated by parsers, and make reviews easier as well. I shiver uncontrollably when I see diffs like this

and would rather set up a process where nobody has to check that the C code is correct :)

That's awesome! But what if someone submitting a PR generated the code themselves without knowing about this, the diff would still be huge then right?

That's awesome! But what if someone submitting a PR generated the code themselves without knowing about this, the diff would still be huge then right?

Yeah, but then the CI can verify that C code is produced by the version of the grammar in the PR (as I care that they're in sync), and the PR author can just force-push and remove those files (when asked) :)
Being able to work with both the a) PRs that contain generated code and b) PRs without it, is key to flexible contribution process - and in the end you still uphold the guarantee that grammar and parser are fully in sync.
Overall it can involve an extra step if the PR author is used to the way it's done on other grammars, but IMO it's worth it to keep PRs individually revertible and cherry-pickable.

Thanks again for awesome contribution!

Just to double check, can I add you as a co-maintainer of smithy alongside me for nvim-treesitter?

Yep.


No Audio or Video on mobile

Hi, I am new to this and have limited coding skills hence looking for help here. I have cloned this on my ubuntu server and when started, I am able to  start the meeting but when I use the link in my Mobile - chrome on Android and IOS, there is no Audio nor video. The desktop cannot see the video from Mobile neither cannot hear, and the Mobile cannot see the video nor hear from desktop. although the camera and mic are allowed. Please help. However Desktop to desktop is working fine.

Audio/Video on mobile iOS is not supported by apple webkit. You should use safari, it works!

I am Having The Same Problem To
My Friend And I ware Testing the Server
I can't able to see his Video and Audio
He Can't able to get my Video and Audio
How to Fix It ?
We Both Are Testing is on Laptop


websocket::response_type fields are empty when using wss (TLS)

I need to extract the http::field::sec_websocket_protocol from a server's handshake response.
When using ws/http, I'm able to read all the included fields just fine.
[DEBUG]websocket_stream.cpp[122]: HandshakeHandler(): WebSocket handshake successful
Printing all fields:
Date = Thu, 10 Mar 2022 11:49:01 GMT
Connection = upgrade
Upgrade = websocket
Sec-WebSocket-Accept = CPSjBfUOHbnPHQ5t0ivK4Gg1Pn0=
Sec-WebSocket-Protocol = protocol1.5
HTTP Response: HTTP/1.1 101 Switching Protocols
Date: Thu, 10 Mar 2022 11:49:01 GMT
Connection: upgrade
upgrade: websocket
sec-websocket-accept: CPSjBfUOHbnPHQ5t0ivK4Gg1Pn0=
sec-websocket-protocol: protocol1.5

However, when using TLS, not a single field shows up. Only the HTTP response code can be printed by using the shift operator.
[DEBUG]websocket_stream.cpp[122]: HandshakeHandler(): WebSocket handshake successful
Printing all fields:
HTTP Response: HTTP/1.1 200 OK

terminate called after throwing an instance of 'boost::wrapexcept<std::out_of_range>'
  what():  field not found

I verified with another WS client that the server sets the fields correctly when using TLS.
Am I missing something essential? Does accessing the fields work differently between ws and wss connections?
Code snippets:
void WebsocketStream::AsyncHandshake() {
  auto server_handshake_response = std::make_shared<boost::beast::websocket::response_type>();
  websocket_->async_handshake_ex(
      *server_handshake_response, endpoint_information_.GetEndpoint(), endpoint_information_.target_,
      [&](boost::beast::websocket::request_type& m) {
        m.insert(http::field::sec_websocket_protocol, endpoint_information_.websocket_protocol_);
        if (endpoint_information_.credentials_) {
          m.insert(http::field::authorization, endpoint_information_.GetHttpBasicAuthString());
        }
      },
      [&, server_handshake_response](const boost::system::error_code& error) {
        HandshakeHandler(error, *server_handshake_response); });

  handshake_timeout_timer_.ReStart(SRC_LOC);
}

void WebsocketStream::HandshakeHandler(const boost::system::error_code& error,
                                       boost::beast::websocket::response_type server_handshake_response) {
  if (error) {
   // ...
  } else {
    LOG_DEBUG("WebSocket handshake successful");

    std::cout << "Printing all fields:\n";
    for(auto const& field : server_handshake_response) {
      std::cout << field.name() << " = " << field.value() << "\n";
    }

    std::cout << "HTTP Response: " << server_handshake_response;

    auto negotiated_protocol = server_handshake_response.at(http::field::sec_websocket_protocol).to_string();
  }
}

I think you forgot to capture the shared pointer to the response by value.in
the completion handler.
On Thu, 10 Mar 2022 at 12:53, Gomox11 @.***> wrote:

I need to extract the http::field::sec_websocket_protocol from a server's
handshake response.
When using ws/http, I'm able to read all the included fields just fine.
[DEBUG]websocket_stream.cpp[122]: HandshakeHandler(): WebSocket handshake successful
Printing all fields:
Date = Thu, 10 Mar 2022 11:49:01 GMT
Connection = upgrade
Upgrade = websocket
Sec-WebSocket-Accept = CPSjBfUOHbnPHQ5t0ivK4Gg1Pn0=
Sec-WebSocket-Protocol = protocol1.5
HTTP Response: HTTP/1.1 101 Switching Protocols
Date: Thu, 10 Mar 2022 11:49:01 GMT
Connection: upgrade
upgrade: websocket
sec-websocket-accept: CPSjBfUOHbnPHQ5t0ivK4Gg1Pn0=
sec-websocket-protocol: protocol1.5
However, when using TLS, not a single field shows up. Only the HTTP
response code can be printed by using the shift operator.
[DEBUG]websocket_stream.cpp[122]: HandshakeHandler(): WebSocket handshake successful
Printing all fields:
HTTP Response: HTTP/1.1 200 OK
terminate called after throwing an instance of 'boost::wrapexceptstd::out_of_range'
what():  field not found
I verified with another WS client that the server sets the fields
correctly when using TLS.
Am I missing something essential? Does accessing the fields work
differently between ws and wss connections?
Code snippets:
void WebsocketStream::AsyncHandshake() {
auto server_handshake_response = std::make_sharedboost::beast::websocket::response_type();
websocket_->async_handshake_ex(
*server_handshake_response, endpoint_information_.GetEndpoint(), endpoint_information_.target_,
[&](boost::beast::websocket::request_type& m) {
m.insert(http::field::sec_websocket_protocol, endpoint_information_.websocket_protocol_);
if (endpoint_information_.credentials_) {
m.insert(http::field::authorization, endpoint_information_.GetHttpBasicAuthString());
}
},
[&, server_handshake_response](const boost::system::error_code& error) {
HandshakeHandler(error, *server_handshake_response); });
handshake_timeout_timer_.ReStart(SRC_LOC);
}
void WebsocketStream::HandshakeHandler(const boost::system::error_code& error,
boost::beast::websocket::response_type server_handshake_response) {
if (error) {
// ...
} else {
LOG_DEBUG("WebSocket handshake successful");
std::cout << "Printing all fields:\n";
for(auto const& field : server_handshake_response) {
  std::cout << field.name() << " = " << field.value() << "\n";
}

std::cout << "HTTP Response: " << server_handshake_response;

auto negotiated_protocol = server_handshake_response.at(http::field::sec_websocket_protocol).to_string();

}
}
—
Reply to this email directly, view it on GitHub
https://github.com/boostorg/beast/issues/2397, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHOZSOGPFZI65HR5LYR7KLU7HPB3ANCNFSM5QMMYD3Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Richard Hodges
@.***
office: +44 2032 898 513
home: +376 861 195
mobile: +376 380 212

Hey @madmongo1,
this line in the above example should capture it by value, shouldn't it?
[&, server_handshake_response](const boost::system::error_code& error) {
```

The line you mentioned is only responsible for the decorator.

```
[&](boost::beast::websocket::request_type& m)
```

Also, since it works for HTTP, I would be confused if this would only cause issues only on HTTPS connections.

HTTP Response: HTTP/1.1 200 OK

That looks like a default constructed response

The line you mentioned is only responsible for the decorator.

You're absolutely right. I was too quick off the mark there.

Does accessing the fields work differently between ws and wss connections?

No, it's the same code - the websocket stream has the underlying stream type as a template parameter.
Which version is boost beast is this? I remember fixing a bug related to handshake at some point.

Yep.
Hmm. I've just committed version 329 to the master branch. Quite a bit of water has flown under the bridge since 189.
May I propose two immediate courses of action?

Boil the problem down to a reproducible test, compiled into a 1-file complete program. This allows me to debug it.
upgrade to latest boost to see if that cures it.

If not, then at least I have a way to find the bug in the latest version (assuming that item 1 does not reveal that it's an unrelated issue of UB).

Hey @madmongo1,
I created a minimal working example as you suggested and... it worked! That fact made me look at my actual source code again.
Thank you very much for your guidance! This issue can be closed now :)

Never fails ;-)