[BUG] System.Collections.Generic.KeyNotFoundException: The given key 'content-platform-dictionaries.zip' was not present in the dictionary.

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

Bloxstrap Version
2.8.0
What problem did you encounter?

Bloxstrap Log
2024-10-31T08:40:20Z [App::OnStartup] Starting Bloxstrap v4.2.0
2024-10-31T08:40:20Z [App::OnStartup] Compiled Thursday, 17 October 2024 at 7:46:36 AM from LUKECOMPUTER\minet
2024-10-31T08:40:20Z [App::OnStartup] Loaded from %UserProfile%\AppData\Local\Bloxstrap\Bloxstrap.exe
2024-10-31T08:40:20Z [App::OnStartup] Temp path is %UserProfile%\AppData\Local\Temp\Bloxstrap
2024-10-31T08:40:20Z [App::OnStartup] WindowsStartMenu path is %UserProfile%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
2024-10-31T08:40:20Z [LaunchSettings] Identifier 'player' is active with data
2024-10-31T08:40:20Z [Logger::Initialize] Initializing at %UserProfile%\AppData\Local\Bloxstrap\Logs\Bloxstrap_20241031T084020Z.log
2024-10-31T08:40:20Z [Logger::Initialize] Finished initializing!
2024-10-31T08:40:20Z [JsonManager<Settings>::Load] Loading from %UserProfile%\AppData\Local\Bloxstrap\Settings.json...
2024-10-31T08:40:20Z [JsonManager<Settings>::Load] Loaded successfully!
2024-10-31T08:40:20Z [JsonManager<State>::Load] Loading from %UserProfile%\AppData\Local\Bloxstrap\State.json...
2024-10-31T08:40:20Z [JsonManager<State>::Load] Loaded successfully!
2024-10-31T08:40:20Z [FastFlagManager::Load] Loading from %UserProfile%\AppData\Local\Bloxstrap\Modifications\ClientSettings\ClientAppSettings.json...
2024-10-31T08:40:20Z [FastFlagManager::Load] Loaded successfully!
2024-10-31T08:40:20Z [LaunchHandler::LaunchRoblox] Initializing bootstrapper
2024-10-31T08:40:20Z [LaunchHandler::LaunchRoblox] Initializing bootstrapper dialog
2024-10-31T08:40:20Z [Bootstrapper::Run] Running bootstrapper
2024-10-31T08:40:20Z [Bootstrapper::SetStatus] Connecting to Roblox...
2024-10-31T08:40:20Z [Deployment::TestConnection<https://setup.rbxcdn.com>] Connecting...
2024-10-31T08:40:20Z [HttpClientLoggingHandler::ProcessRequest] GET https://setup.rbxcdn.com/versionStudio
2024-10-31T08:40:20Z [Deployment::InitializeConnectivity] Testing connectivity...
2024-10-31T08:40:21Z [HttpClientLoggingHandler::ProcessResponse] 200 OK https://setup.rbxcdn.com/versionStudio
2024-10-31T08:40:21Z [Deployment::InitializeConnectivity] Got https://setup.rbxcdn.com as the optimal base URL
2024-10-31T08:40:21Z [Bootstrapper::Run] Connectivity check finished
2024-10-31T08:40:21Z [Bootstrapper::CheckForUpdates] Checking for updates...
2024-10-31T08:40:21Z [HttpClientLoggingHandler::ProcessRequest] GET https://api.github.com/repos/bloxstraplabs/bloxstrap/releases/latest
2024-10-31T08:40:21Z [HttpClientLoggingHandler::ProcessResponse] 200 OK https://api.github.com/repos/bloxstraplabs/bloxstrap/releases/latest
2024-10-31T08:40:21Z [Bootstrapper::CheckForUpdates] No updates found
2024-10-31T08:40:21Z [Bootstrapper::GetLatestVersionInfo] Got channel as production
2024-10-31T08:40:21Z [Deployment::GetInfo] Getting deploy info for channel production
2024-10-31T08:40:21Z [HttpClientLoggingHandler::ProcessRequest] GET https://clientsettingscdn.roblox.com/v2/client-version/WindowsPlayer
2024-10-31T08:40:21Z [HttpClientLoggingHandler::ProcessResponse] 200 OK https://clientsettingscdn.roblox.com/v2/client-version/WindowsPlayer
2024-10-31T08:40:21Z [RegistryKeyEx::SetValueSafe] Writing '' to HKEY_CURRENT_USER\SOFTWARE\ROBLOX Corporation\Environments\RobloxPlayer\Channel\www.roblox.com
2024-10-31T08:40:21Z [HttpClientLoggingHandler::ProcessRequest] GET https://setup.rbxcdn.com/version-b7eebc919e96477a-rbxPkgManifest.txt
2024-10-31T08:40:21Z [HttpClientLoggingHandler::ProcessResponse] 200 OK https://setup.rbxcdn.com/version-b7eebc919e96477a-rbxPkgManifest.txt
2024-10-31T08:40:21Z [Bootstrapper::SetStatus] Installing {product}...
2024-10-31T08:40:23Z [Bootstrapper::DownloadPackage.RobloxApp.zip] Package is already downloaded, skipping...
2024-10-31T08:40:23Z [Bootstrapper::ExtractPackage] Extracting RobloxApp.zip...
2024-10-31T08:40:23Z [Bootstrapper::DownloadPackage.content-avatar.zip] Package is already downloaded, skipping...
2024-10-31T08:40:23Z [Bootstrapper::ExtractPackage] Extracting content-avatar.zip...
2024-10-31T08:40:23Z [Bootstrapper::DownloadPackage.content-configs.zip] Package is already downloaded, skipping...
2024-10-31T08:40:23Z [Bootstrapper::ExtractPackage] Extracting content-configs.zip...
2024-10-31T08:40:23Z [Bootstrapper::DownloadPackage.content-fonts.zip] Package is already downloaded, skipping...
2024-10-31T08:40:23Z [Bootstrapper::DownloadPackage.content-models.zip] Package is already downloaded, skipping...
2024-10-31T08:40:23Z [Bootstrapper::DownloadPackage.content-sky.zip] Package is already downloaded, skipping...
2024-10-31T08:40:23Z [Bootstrapper::ExtractPackage] Extracting content-fonts.zip...
2024-10-31T08:40:23Z [Bootstrapper::ExtractPackage] Extracting content-models.zip...
2024-10-31T08:40:23Z [Bootstrapper::ExtractPackage] Finished extracting content-configs.zip
2024-10-31T08:40:23Z [Bootstrapper::ExtractPackage] Extracting content-sky.zip...
2024-10-31T08:40:23Z [Bootstrapper::ExtractPackage] Finished extracting content-avatar.zip
2024-10-31T08:40:23Z [Bootstrapper::ExtractPackage] Finished extracting content-models.zip
2024-10-31T08:40:23Z [Bootstrapper::DownloadPackage.content-sounds.zip] Package is already downloaded, skipping...
2024-10-31T08:40:23Z [Bootstrapper::ExtractPackage] Extracting content-sounds.zip...
2024-10-31T08:40:23Z [Bootstrapper::ExtractPackage] Finished extracting content-sounds.zip
2024-10-31T08:40:23Z [Bootstrapper::DownloadPackage.shaders.zip] Package is already downloaded, skipping...
2024-10-31T08:40:23Z [Bootstrapper::ExtractPackage] Extracting shaders.zip...
2024-10-31T08:40:23Z [Bootstrapper::ExtractPackage] Finished extracting content-sky.zip
2024-10-31T08:40:23Z [Bootstrapper::DownloadPackage.ssl.zip] Package is already downloaded, skipping...
2024-10-31T08:40:23Z [Bootstrapper::ExtractPackage] Extracting ssl.zip...
2024-10-31T08:40:23Z [Bootstrapper::ExtractPackage] Finished extracting ssl.zip
2024-10-31T08:40:24Z [Bootstrapper::DownloadPackage.content-textures2.zip] Package is already downloaded, skipping...
2024-10-31T08:40:24Z [Bootstrapper::ExtractPackage] Extracting content-textures2.zip...
2024-10-31T08:40:24Z [Bootstrapper::DownloadPackage.content-textures3.zip] Package is already downloaded, skipping...
2024-10-31T08:40:24Z [Bootstrapper::DownloadPackage.content-terrain.zip] Package is already downloaded, skipping...
2024-10-31T08:40:24Z [Bootstrapper::DownloadPackage.content-platform-fonts.zip] Package is already downloaded, skipping...
2024-10-31T08:40:24Z [Bootstrapper::DownloadPackage.content-platform-dictionaries.zip] Package is already downloaded, skipping...
2024-10-31T08:40:24Z [Bootstrapper::DownloadPackage.extracontent-places.zip] Package is already downloaded, skipping...
2024-10-31T08:40:24Z [Bootstrapper::DownloadPackage.extracontent-luapackages.zip] Package is already downloaded, skipping...
2024-10-31T08:40:24Z [Bootstrapper::DownloadPackage.extracontent-translations.zip] Package is already downloaded, skipping...
2024-10-31T08:40:25Z [Bootstrapper::ExtractPackage] Finished extracting content-fonts.zip
2024-10-31T08:40:25Z [Bootstrapper::ExtractPackage] Extracting content-textures3.zip...
2024-10-31T08:40:25Z [Bootstrapper::DownloadPackage.extracontent-models.zip] Package is already downloaded, skipping...
2024-10-31T08:40:25Z [Bootstrapper::DownloadPackage.extracontent-textures.zip] Package is already downloaded, skipping...
2024-10-31T08:40:25Z [Bootstrapper::DownloadPackage.WebView2.zip] Package is already downloaded, skipping...
2024-10-31T08:40:25Z [Bootstrapper::DownloadPackage.WebView2RuntimeInstaller.zip] Package is already downloaded, skipping...
2024-10-31T08:40:25Z [Bootstrapper::DownloadPackage.redist.zip] Package is already downloaded, skipping...
2024-10-31T08:40:25Z [Bootstrapper::SetStatus] Configuring {product}...
2024-10-31T08:40:25Z [Bootstrapper::ExtractPackage] Finished extracting content-textures3.zip
2024-10-31T08:40:25Z [Bootstrapper::ExtractPackage] Extracting content-terrain.zip...
2024-10-31T08:40:25Z [Bootstrapper::ExtractPackage] Finished extracting content-terrain.zip
2024-10-31T08:40:25Z [Bootstrapper::ExtractPackage] Extracting content-platform-fonts.zip...
2024-10-31T08:40:26Z [Bootstrapper::ExtractPackage] Finished extracting shaders.zip
2024-10-31T08:40:26Z [Bootstrapper::ExtractPackage] Extracting extracontent-places.zip...
2024-10-31T08:40:26Z [Bootstrapper::ExtractPackage] Finished extracting extracontent-places.zip
2024-10-31T08:40:26Z [Bootstrapper::ExtractPackage] Extracting extracontent-luapackages.zip...
2024-10-31T08:40:27Z [Bootstrapper::ExtractPackage] Finished extracting extracontent-luapackages.zip
2024-10-31T08:40:27Z [Bootstrapper::ExtractPackage] Extracting extracontent-translations.zip...
2024-10-31T08:40:28Z [Bootstrapper::ExtractPackage] Finished extracting extracontent-translations.zip
2024-10-31T08:40:28Z [Bootstrapper::ExtractPackage] Extracting extracontent-models.zip...
2024-10-31T08:40:28Z [Bootstrapper::ExtractPackage] Finished extracting extracontent-models.zip
2024-10-31T08:40:28Z [Bootstrapper::ExtractPackage] Extracting extracontent-textures.zip...
2024-10-31T08:40:28Z [Bootstrapper::ExtractPackage] Finished extracting content-platform-fonts.zip
2024-10-31T08:40:28Z [Bootstrapper::ExtractPackage] Extracting WebView2.zip...
2024-10-31T08:40:28Z [Bootstrapper::ExtractPackage] Finished extracting WebView2.zip
2024-10-31T08:40:28Z [Bootstrapper::ExtractPackage] Extracting redist.zip...
2024-10-31T08:40:29Z [Bootstrapper::ExtractPackage] Finished extracting redist.zip
2024-10-31T08:40:35Z [Bootstrapper::ExtractPackage] Finished extracting RobloxApp.zip
2024-10-31T08:40:36Z [Bootstrapper::ExtractPackage] Finished extracting extracontent-textures.zip
2024-10-31T08:40:40Z [Bootstrapper::ExtractPackage] Finished extracting content-textures2.zip
2024-10-31T08:40:40Z [LaunchHandler::LaunchRoblox] Bootstrapper task has finished
2024-10-31T08:40:40Z [LaunchHandler::LaunchRoblox] An exception occurred when running the bootstrapper
2024-10-31T08:40:40Z [App::FinalizeExceptionHandling] System.Collections.Generic.KeyNotFoundException: The given key 'content-platform-dictionaries.zip' was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Bloxstrap.Bootstrapper.ExtractPackage(Package package, List`1 files)
   at Bloxstrap.Bootstrapper.<>c__DisplayClass33_1.<UpgradeRoblox>b__6()
   at System.Threading.Tasks.Task.InnerInvoke()
   at System.Threading.Tasks.Task.<>c.<.cctor>b__272_0(Object obj)
   at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
   at Bloxstrap.Bootstrapper.UpgradeRoblox()
   at Bloxstrap.Bootstrapper.Run()
   at Bloxstrap.Bootstrapper.Run()

LMFAOO EXPLOITER
GTFO 😭😭

upgrade bloxstrap to 2.8.1

LMFAOO EXPLOITER GTFO 😭😭

huh?

LMFAOO EXPLOITER GTFO 😭😭

How do you find a exploiter?

How do you find a exploiter?

from LUKECOMPUTER\minet

Ahh


build: enable noUnusedParameters check in aot.

Re-enables the noUnusedParameters check in the e2eapp and demo-app (AOT).

Should be able to enable this one as well https://github.com/angular/material2/blob/dfe8091d959f1bb54cc33a8d942cbe7ea4e3fe56/src/universal-app/tsconfig-build.json#L8

Done.


Empty Provider

Hi,
Is this meant by you that it doesn't add or link to an existing WFP Provider ?
The rules do stand out due to this (for OPSEC perspective)
Regards
K4nfr3

The following code: https://github.com/netero1010/EDRSilencer/blob/main/EDRSilencer.c#L62 is used to manage the filter name with which rules are created. You can modify this with your custom (or existing) filter name.

Hi,
that's the filter rule name, not the provider name ;-)

Hi. I believe adding provider to the custom rule will help in OPSEC perspective. I will check if it is better to get existing provider or creating a new one. I will include this to my to-do list in the next update. Thanks @k4nfr3 and @pbssubhash.

Updated in version 1.2. A new WFP provider will be created for the custom WFP filter.


tracing configmap added

Fixes
Added a tracing configmap, so that the configAccessor in ReconcileKind can pick it up and expose traces on jaeger/zipkin like other sources.

Proposed Changes

Adds a configmap yaml in config during installation

Release Note

Docs

/assign @evankanderson

There is no written down conventions about where to deploy sources and how to share configmaps. The "trend" has been to install sources in knative-eventing, sharing configmaps with the other components.

related https://github.com/knative-sandbox/eventing-ceph/issues/195


Add versionable feature to td-agent-gem provider

In case someone wants to specify gem version, td-agent-gem provider must have :versionable feature added.

Thank you!


Add find odd integer program

Description
I created a function that takes an array and finds the integer which appears an odd number of times. I use Hashing array elements as key and their counts as value.
Issue No.- #143

Type issue number after hash(#)

Checklist

[x] Yes, this task assigned to me.
[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] My Filename is in camelCase format
[x] I have added Problem statement, Problem link in file.

Thanks for messaging but priority will give to issue-author(who created the issue)


Documentation improvements

See original issue on GitLab
In GitLab by [Gitlab user @knownexus] on Dec 12, 2017, 11:29
Writing docs for:

[ ]  I want to make my project work with Buildstream

[x]  I want to build a project, what do I do?

[x]  When I've finished building the  project, what can I do with it?
Post-build

[x]  How can I get the output?

[x]  Now I want to modify code and test the result
Modifying and Testing

[x]  How can I modify this module and test it against something which depends on it?

install buildstream

In GitLab by [Gitlab user @knownexus] on Dec 12, 2017, 11:34
mentioned in merge request !183

In GitLab by [Gitlab user @knownexus] on Dec 12, 2017, 11:40
changed the description

In GitLab by [Gitlab user @jonathanmaw] on Dec 12, 2017, 17:38
marked the task I want to make my project work with Buildstream as completed

In GitLab by [Gitlab user @jonathanmaw] on Dec 12, 2017, 17:38
marked the task I want to make my project work with Buildstream as incomplete

In GitLab by [Gitlab user @LaurenceUrhegyi] on Dec 19, 2017, 10:54
marked the task How can I modify this module and test it against something which depends on it? as completed

In GitLab by [Gitlab user @LaurenceUrhegyi] on Dec 19, 2017, 10:54
marked the task How can I modify this module and test it against something which depends on it? as incomplete

In GitLab by [Gitlab user @knownexus] on Dec 20, 2017, 17:50
marked the task I want to make my project work with Buildstream as completed

In GitLab by [Gitlab user @knownexus] on Dec 20, 2017, 17:50
marked the task I want to make my project work with Buildstream as incomplete

In GitLab by [Gitlab user @knownexus] on Dec 20, 2017, 17:50
marked the task I want to build a project, what do I do? as completed

In GitLab by [Gitlab user @knownexus] on Dec 20, 2017, 17:50
marked the task When I've finished building the  project, what can I do with it? as completed

In GitLab by [Gitlab user @knownexus] on Dec 20, 2017, 17:50
marked the task How can I get the output? as completed

In GitLab by [Gitlab user @knownexus] on Dec 20, 2017, 17:50
marked the task Now I want to modify code and test the result as completed

In GitLab by [Gitlab user @knownexus] on Dec 20, 2017, 17:50
marked the task How can I modify this module and test it against something which depends on it? as completed

In GitLab by [Gitlab user @tristanvb] on Dec 25, 2017, 04:51
Note, for documentation related to the yaml format and authoring of projects, #103 is relevant

In GitLab by [Gitlab user @knownexus] on Jan 12, 2018, 11:38
changed the description

In GitLab by [Gitlab user @knownexus] on Jan 12, 2018, 11:39
changed the description

In GitLab by [Gitlab user @knownexus] on Jan 12, 2018, 11:39
changed the description

In GitLab by [Gitlab user @LaurenceUrhegyi] on Jan 13, 2018, 17:17
changed the description

In GitLab by [Gitlab user @knownexus] on Mar 8, 2018, 14:24
changed the description

In GitLab by [Gitlab user @jennis] on Mar 9, 2018, 15:59
marked the task How can I modify this module and test it against something which depends on it? as incomplete

In GitLab by [Gitlab user @jennis] on Mar 9, 2018, 15:59
marked the task How can I modify this module and test it against something which depends on it? as completed

In GitLab by [Gitlab user @LaurenceUrhegyi] on Jun 1, 2018, 14:52
closing in favour of https://gitlab.com/BuildStream/buildstream/issues/103

In GitLab by [Gitlab user @LaurenceUrhegyi] on Jun 1, 2018, 14:52
closed


After enabling NavMesh in Advanced Import Settings it cannot be disabled again.

Tested versions
4.3[2e7fc81]
System information
Windows 11 - Vulkan - Nvidia RTX 4070 - intel i5 13600KF
Issue description
In the import dialog (glb or blend doesn't matter) if you set NavMesh to any options other than disabled and reimport then it's impossible to go back to disabled again (you can select it and reimport but the reimport doesn't do anything it stays at the last options you had).
Steps to reproduce

Add a gltf or a blender file with a mesh.
Double click it in the FileSystem dock.
Select the MeshInstance3D.
Change NavMesh setting to anything other then disabled.
Reimport.
Observe changes in the editor to ensure everything worked.
Do 2-5 again but use Disabled instead for the NavMesh Setting.
Observer nothing has changed

Minimal reproduction project (MRP)
You can use this one: NavigationBakeIssue.zip
It really doesn't matter what model you have or scripts or anything, this is a bug in the import settings so anything as long as it has the above mentioned settings goes.

Can't reproduce in 81f3d43

Yeah, can confirm it's gone in the today's master.

This bug is still in stable 4.3. Restarting the editor does not help, I had to delete the *.import file.


luci-app-opkg: Update Spanish translation

Update Spanish translation
Signed-off-by: Franco Castillo<EMAIL_ADDRESS>

Please merge this two commits

How do I do that?


failed to load system roots and no roots provided

time="2019-02-09T06:39:33Z" level=error msg="failed to define word: failed to make request to rae: Get https://dle.rae.es/srv/search?w=gato: x509: failed to load system roots and no roots provided"

Hi, this error is saying that the binary cannot find the root CA certificates that should be installed on every system. How are you running drae? Are you running the binary directly on you machine, the squat/drae container, or some other way? Also, what is your environment/os?

Closing due to no response. Please reopen if it's still and issue :)


Update README.md

Description
Slight update to README now that Psi4 1.3 is out.
Status

[x] Click when ready for review-and-merge

Codecov Report

Merging #78 into master will not change coverage.
The diff coverage is n/a.


lib: add callLocklessFlake

This is essentially a copy of the function of the same name, from
flake-compat. callLocklessFlake is useful when trying to utilise a
flake.nix without a lock file, often for when you want to create a
subflake from within a parent flake.
Co-authored-by: Tom Bereknyei<EMAIL_ADDRESS>Taken from: https://github.com/tomberek/relative/blob/0943a113c19e17b5f51c054de5233f2d3c97ce35/flake.nix#L32-L36
Inspired by: https://github.com/edolstra/flake-compat/blob/64a525ee38886ab9028e6f61790de0832aa3ef03/default.nix#L84-L88
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Should this be in flake-utils repo instead of here?

@Artturin It would be a real shame to depend on a library like flake-utils in any flake, than to be able to simply say nixpkgs.lib.callLocklessFlake. If this isn't merged, I'll just be using it in the let block of my outputs, like is the case in all of the examples https://github.com/NixOS/templates/blob/6296caa969420047c3de8b336f481106cf7af6f8/c-hello/flake.nix#L8

@roberth I've done as you requested. All that's left to do is add a test in lib/tests. I will do this shortly.

I've added what I think is a decent test, I'm not sure how i could do it better, so please advise on a better way to do it if there is one.

I think this is a very bad idea and I have reverted it in https://github.com/NixOS/nixpkgs/pull/173093.

I figured users of this function would anticipate breaking changes, as Flakes are clearly advertised to be experimental.
I do not think preemptively removing it is particularly productive, but I respect that other maintainers don't want to be responsible for this code.
https://github.com/NixOS/rfcs/pull/82 has been mentioned as a solution in the other thread. I've offered to shepherd it some time ago. If you're interested, please join.

I do not think it's fair to say that Flakes are experimental, given how many users there are, and the plan to stabilize them. They may be unstable, but I do not agree that they are experimental.

Flakes are deeply flawed when it comes to user facing design/implementation choices. If anything, they should be considered more experimental than they currently are. But maybe I should have more faith in upstream's courage to make (very) breaking changes.
That said, I'll reiterate:
I do not think preemptively removing it is particularly productive.

I don't mind the revert for now. I'm working on a better replacement for this that will be strictly speaking more compliant with flakes/subflakes as well as a bit more powerful (allow dynamically generated input + follows attrsets).

Usually, Nixpkgs cares about a strict subset of stable features of (non-latest, because all the interwoven release cycles) stable Nix. There are useful things easily doable in Nix but not expected to be done in Nixpkgs.

I do not think preemptively removing it is particularly productive.

Merging it in the first place set a bad precedent with far reaching implications for the stability expectation of all of lib.

Since this got reverted, I made a PR to add it to flake-utils. What do you think?

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/url-of-flake-inside-flake/32939/2


EventBridge integration

Is your feature request related to a problem? Please describe.
Feature request
Describe the solution you'd like
Would like an easy way to send events to EventBridge.
Like certain mutations in my AppSync schema... For example, an order that needs to be processed.
Describe alternatives you've considered
Build out custom resolvers that push the event into EventBridge.
Additional context
Let me know if you need more

I have added this to our backlog for prioritization, once this is prioritized we will work on this. Feel free to 👍 so this gets more visibility

@yuth In the meantime, is there any suggestions on how to incorporate eventbridge resources into an Amplify project?

Hi @yuth!
I think you can go with https://docs.amplify.aws/cli/usage/customcf.
You can create a custom CloudFormation template to create an event bridge. It's the only way for the moment before this feature request will be added.
Cheers.
Yu.

Hey! Any updates?


fyi - ld: library not found for -lsecp256k1 for architecture arm64

ld: warning: directory not found for option '-L/Users/johndpope/Documents/cryptoWorkspace/BitcoinKit/Libraries/crypto/lib'
ld: warning: directory not found for option '-L/Users/johndpope/Documents/cryptoWorkspace/BitcoinKit/Libraries/secp256k1/lib'
ld: library not found for -lsecp256k1 for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
seems like a mismatch on /lib subfolder.

ripping out the /lib allows compiles library

seems build script is tripping up.

do you have a bespoke Configure script?
./Configure iphoneos-cross no-shared no-dso no-hw no-engine no-ssl2 no-ssl3 no-comp no-idea no-asm no-dtls no-dtls1 no-threads no-err no-npn no-psk no-srp no-ec2m no-weak-ssl-ciphers -fembed-bitcode -miphoneos-version-min=8.0 --openssldir="$TARGETDIR"

so can see the configure script. some how the above script is losing context of where it is.

seems my script got a typo from fat fingering keyboard.

re-ran script am outputting results to txt. will post here - error with lib folder persists.

is there lib folder missing?

https://gist.github.com/johndpope/ee39028590bb26f480fec8d69460b4cb

I believe source of this is not correctly initialising things

carthage update --platform iOS --no-use-binaries


Documentation updates

Please ally my feedback.
BTW, when you will be updating DateTime (and if not in this PR, it is fine), can you please mention that it is std::chrono::time_point and link https://en.cppreference.com/w/cpp/chrono/time_point ?

DateTime was not in my assigned namespace.  If it hasn't been done by the owner I can look to help out later tonight

Part of https://github.com/Azure/azure-sdk-for-cpp/issues/2260


Vim9: ":disassemble" prints incomplete function header

Describe the bug
In Vim9 script, the header of a function is incomplete in the output of :disassemble.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    def Toggle(enable = !exists('#matchparen'))
    enddef
    disa Toggle
EOF
)

These lines are printed:
<SNR>1_Toggle
   0 JUMP_IF_ARG_SET arg[-1] -> 5
   1 PUSHS "#matchparen"
   2 BCALL exists(argc 1)
   3 INVERT (!val)
   4 STORE arg[-1]
   5 RETURN 0

Notice that the first line only prints the name of the function from the header.
<SNR>1_Toggle

Expected behavior
The first line prints the header in its entirety:
<SNR>1_Toggle(enable = !exists('#matchparen'))
             ^-------------------------------^

Environment

Vim version: 8.2 Included patches: 1-2786
OS: Ubuntu 16.04.7 LTS
Terminal: xterm(367)

Additional context
This would be especially useful when we use a complex expression in the value of an optional argument.  Otherwise, we might wonder where the generated instructions come from.  For example, in the previous snippet, if I don't look at the definition of Toggle() in its original script, I have no idea why Vim has generated a PUSHS instruction to push the string '#matchparen', nor why it has generated a BCALL instruction to call the builtin function exists():
1 PUSHS "#matchparen"
2 BCALL exists(argc 1)

I think we shouldn't have to look at the original source code to understand the purpose of the generated instructions; :disassemble should be understandable on its own.

Unrelated but could we get some documentation about the meaning/purpose of each generated instruction?

Never mind, :disa is for debugging and testing only.  I still keep the issue open because I think it would be nice for the header to be completely printed.


HTML served over socket.io connections missing template strings

Affects

Newly posted discussion comments missing reply box text

Added the missing l variable to template context rendered by the socket function


Refactor: Split members.json into separate files

Problem
The ecosystem database is in members.json, and is difficult to for humans to edit, and causes merge conflicts.
Proposed solution
@IceKhan13 and @1ucian0 have suggested splitting this out into different files (one file per repo).
Since manager.py seems to access repos exclusively by tier or URL, I suggest the following structure:
ecosystem/resources/members
├── Tier.yaml  # List of URLs of repos
└── organisation
    └── repo-name.yaml

For example:
ecosystem/resources/members
├── Community.yaml
├── Extensions.yaml
├── Main.yaml
├── Qiskit
│   ├── qiskit-finance.yaml
│   └── qiskit-nature.yaml
└── unitaryfund
    └── mitiq.yaml

This should immediately remove merge conflict problems, but should also make it easier to avoid the set-output feature (see #406) as each step in the action can modify a file.
Future work

Will still include a members.json as MVP, but eventually should have that compiled and released using an action. Actually I think releasing members.json should be in MVP.
Currently unsure how this fits with #228.

Don't you thing still having centralized files for url (Tier.yaml) will still favorized conflicts and so just moving the problem from a file to another ?
Why not having a folder per Tier and then inside having one yaml per project, something like :
ecosystem/resources/members
├── community
│   ├── my_super_project.yaml
│   ├── my_awesome_project.yaml
├── extensions
│   ├── my_super_extt.yaml
│   ├── my_awesome_ext.yaml
├── main
│   ├── qiskit-finance.yaml
│   └── qiskit-nature.yaml
└── index.yaml

The index.yaml would contains the list of the tier folders (community, extensions, main, ...). As the tier are static, we would not have any conflict this way.

Also what the difference between qiskit and main, from my understanding qiskit is purely main ?
I saw unitaryfund folder, do we need a folder per organisation or can we have a folder partners or something like ? If we create a folder per organization, we need to find a way to reference new folder without re-creating conflict.

About #228, i think we should close it and keep the work on this new one.
For the set-output, the problem is for the function in actions bash script as well. I think we need to review it more generally to have a better management of the vars.

Thanks for your reply!
I'm thinking ahead a bit, but since most uses of the DAO are accessing by URL, my idea was to order the files by URL (the part after github.com/). Then file access becomes trivial and we can rid of the DAO in the future. The only other access type is by tier, hence the Tier.yaml files. These merge conflicts would just be one line, but it's still not zero-touch, which I agree is a drawback.
In terms of how things currently are, your suggestion makes more sense as that's the way members.json is structured. Can I suggest something like this?
└── tier
    └── organisation
        └── repo.yaml

For example:
ecosystem/resources/members
├── community
│   └── unitaryfund
│       └── mitiq.yaml
├── extensions
│   └── qiskit-community
│       └── prototype-qrao.yaml
└── main
    ├── Qiskit
    │   └── qiskit_ibm_runtime.yaml
    └── openqasm
        └── openqasm.yaml

That way there are no problems if two repos have the same name.

...what the difference between qiskit and main...

I'm not 100% sure, but I think tier is just a level of endorsement. I can see that at least the openqasm/openqasm repo is considered "main", so main ≠ qiskit.

..do we need a folder per organisation... ...we need to find a way to reference new folder without re-creating conflict.

I think it would be good if filepath was unique to URL (e.g. github.com/unitaryfund/mitiq). We can just do an os.walk to find files; no index needed.

@AbdullahKazi500 I won't assign just yet as it's not clear what the best solution is.

@frankharkins indeed something like should work fine :)
Just in the community as most of the project doesn't have organization, how do you see them ? Inside a subfolder toto or directly inside the community mixed with the organizations folders ?

@mickahell After thinking on it a bit, I think the path of least resistance is to go with your original proposal. I think by trying to add more layers I was just making it more complicated.
Let's go with your original idea.
ecosystem/resources/members
├── community
│   ├── my_super_project.yaml
│   ├── my_awesome_project.yaml
├── extensions
│   ├── my_super_extt.yaml
│   ├── my_awesome_ext.yaml
├── main
│   ├── qiskit-finance.yaml
│   └── qiskit-nature.yaml
└── index.yaml

We need to find a simple way to stock this file, maybe more using artifact or something like

Yep I imagined either nightly or on push to main, an action would compile a JSON in the same form as we currently have, and add it as a release asset.

Probably even simpler is to have the file generated by the user, using a script, and checked in to version control. Then, qiskit.org points to that static URL.
Yes, there will be merge conflicts for the generated file. But the answer is to simply regenerate the generated file -- you should never try to manually fix the merge conflict.
This is how we generate our quite complex GitHub action YAML files for Pantsbuild. It's worked quite well for us! https://github.com/pantsbuild/pants/blob/main/src/python/pants_release/generate_github_workflows.py. It's nice being able to see in the PR how the final rendered asset will look.

Hmm ok, so we need a manual action to generate it. It's too much action for someone to git pull, git checkout and then git push and create a PR to do.
But It can also became the same problem as we have today and we will have so many branchs open (similar to the batch_check_ branchs)

The action can probably push directly to the submission-* branch, maybe triggering on PR approval.

I'm not following why we need a GitHub Action? When you change the YAML files, you are expected to also run a script to update the final JSON file. CI will check if the JSON file is out-of-date and error if so with instructions of how to run the script.
Yeah, that's a little manual. But keep it simple for now.

The action can probably push directly to the submission-* branch, maybe triggering on PR approval.

If we put the generated general file who ref every project we will have conflict as well because every submission gonna edit it with their url :/

I'm not following why we need a GitHub Action? When you change the YAML files, you are expected to also run a script to update the final JSON file. CI will check if the JSON file is out-of-date and error if so with instructions of how to run the script.

User never run any script, they only submitted issue and the Action does the who trick, then someone only need to validate the PR to add the project and so never no-one need to clone and commit anything so can't run any script. That's why we need an action to generated this file
Do you see what I mean ? I'm not sure to be totally clear ^^'

Or I'm wondering, can github Pages generated raw data html page by merging json ?
This way we would not have to store any general json file. And so we would not have any risk of conflict anymore. And no need any manual process to do.

@Eric-Arellano thanks! Yep I imagined either nightly or on push to main, an action would compile a JSON in the same form as we currently have, and add it as a release asset. Then qiskit.org can point to one link. I.e.
- https://raw.githubusercontent.com/qiskit-community/ecosystem/master/ecosystem/resources/members.json
+ https://github.com/qiskit-community/ecosystem/releases/latest/download/members.json

If my point just above is not possible. The solution you refer @frankharkins looks good to me 🙂
Doing that from the main branch in order to stock the general file in the latest tag assets, would allow to not have conflict and to always be up to date with the actual main branch. Only require at most to click on a single button (no script, no git cmd, ...)
We could even schedule the action to be launch every day or every week in order to be fully automatic 🤖

After trying to implement this, I've realised that we shouldn't have the "tier" information in two places. This is already causing problems: For example, qiskit-ibm-provider is "Main" on qiskit.org/ecosystem, but has the "Extension" badge.
In PR #426, I've gone with naming all TOML files the repo name, and having them all the same level.

Before closing this issue, just a quick question @frankharkins how do we manage the submission actually in PR :

#388
#390
#398
#402

For the #402, I can close it and regenerate it (it's my QAMP project) but for the other do we resubmit them by hand ?

I re-created each submission but I couldn't delete the old branches
Maybe we can also clean the batch branches in order to restarted from this new way to go. What do you think ?
Anyway we can close this issue :)


Update Cargo.toml

Updates dependency to the patch version of 0.9.8
Advisory

Hi, thanks for the MR!


Backend : Getting different case for entity type in data assets charts and web charts

Affected module
Does it impact the UI, backend or Ingestion Framework?
Backend
Describe the bug
A clear and concise description of what the bug is.
In the data insight report, we are getting a different case for entity type in the data assets chart and web charts.
For Example In data assets, we are getting DatabaseSchema as an entity type but in web analytics Databaseschema is an entity type.
To Reproduce
Screenshots or steps to reproduce
Expected behavior
A clear and concise description of what you expected to happen.
Entity Type should be the same in all the charts.
Version:

OS: [e.g. iOS]
Python version:
OpenMetadata version: [e.g. 0.8]
OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==XYZ]

Additional context
Add any other context about the problem here.

@TeddyCr can we make these consistent?

Fixed in #9239


Component: Package size selection (TJT shipping)

Why?
All of the views for the shipping selection in the ad input form is currently added to AdInsertion. Unfortunately, they're really tightly coupled together and we need to move these views around, so I'm working on moving a few of them to FinnUI to make that simpler.
First up is the package size selection. This view was not handling multitasking very well in the old implementation, so I've added support for that. I've tried to keep spacing similar to what we have today.
Also, I see now probably chose a bad name for this branch, since it only contains one component 🤷♂
What?

Added ShippingPackageSizeView, subviews and models.
Added demo + snapshot tests.
Copy images from AdInsertion.

Version Change
Minor. Only a new view.
UI Changes

iPhone
iPad
iPad with multitasking

This PR might be closed in favor of https://github.com/finn-no/FinniversKit/pull/1110. I got some time to implement the new design while waiting for the backend to become ready.

Closing this PR. This component is no longer needed.


dev: Refactor Adapty plugin to improve testability; Add linting; Upgrade versions constraints

Changelog:
2.0.0

BREAKING CHANGE: Adapty class is now singleton, that implements AdaptyPlugin contract (for future support for different platforms and testing).
BREAKING CHANGE: To ease migration, Adapty class, that contained static methods, had been renamed to AdaptyLegacy.
BREAKING CHANGE: Updated project structure. Use the following imports in dependent projects:

import 'package:adapty_flutter/adapty_flutter.dart';

// To avoid code changes in projects that are already using adapty_flutter,
// use the following import before migration:
import 'package:adapty_flutter/adapty_legacy.dart';

BREAKING CHANGE: AdaptyProfileParameterBuilder does not have map getter anymore, it is replaced with build() method and returns new instance of map that is copy of internal _params field.
BREAKING CHANGE: Change Dart version contraints: >=2.16.0 <3.0.0
BREAKING CHANGE: Change Flutter version SDK contraints: >=2.10.0 <3.0.0
Package is now been analyzed with lints package rules.
Most error codes now have document comments.

@x401om @iwitaly I need your help with the setup for example application!

Hello!
Thank you for the awesome PR! We have recently released a new version of our SDK, in which we tried to take into account a bunch of your suggestions. Unfortunately, merging is not possible at the moment. If you suddenly see some things that can be improved, please make a new one, or create an issue.


Jet2 757 livery.

so the engines and winglets should have text but idk where to put

I will figure it out for you tomorrow. (Now at me its quite late)

oki

I have find the winglets. The engines are half-half of the other part.
I forgot to tell that the bottom of the texture (under the fuselage) needs to be white for every texture.

The left winglet on the image is the left outer-right inner, the right one is the right outer, left inner.

ok

is one flipped???? @kolos26


[Doc] Release Note for ONE-vscode 0.3.0

This commit will add below.

Release Note for ONE-vscode 0.3.0

ONE-vscode-DCO-1.0-Signed-off-by: struss<EMAIL_ADDRESS>

This document comes from https://github.com/Samsung/ONE-vscode/issues/712#issuecomment-1138098574
if anything need to update on this, please add a review for this!

Could you let us know what docs/release/0.3.0/index.rst file is for?

Could you let us know what docs/release/0.3.0/index.rst file is for?

Um... I thought this document managed by those. but I think this also not needed, just put all release note on doc/release.
I will remove that fix structure of this.

um.... I think I will revise this contents to match with file in this, @jyoungyun what do you think about this?

what do you think about this?

Sure :)
If you want to use this file, you can fix the following workflow code:
https://github.com/Samsung/ONE-vscode/blob/0ab81b8de6561e885c9c2288a6de72769e29d353/.github/workflows/build-release.yml#L239
docs/release/release-note-${{ github.event.inputs.tag }}
I think, there is no need to keep the same file multiple places.

I think, there is no need to keep the same file multiple places.

I think this looks good. what about just keep release note on single file and track just in history?

PTAL

@jyoungyun
For me, release_note.md in the top directory only contains specific version.
So how about following process? :)

Version up, checklist, ...
Branch out (e.g. release/0.2.0)
Create release_note.md at release/0.2.0 branch

Do not create at main branch

Run workflow with release/0.2.0

AFAIK, when @jyoungyun created ONE-vscode/release_note.md, the purpose of file was to create info in release page by CI. So, this file is not supposed to provide general release info. :-)
Since this file is used by CI, how about put this file into ONE-vscode/infra/release/recent_release_note.md?
This will needs only one PR approval process and looks simple.

For me, release_note.md in the top directory only contains specific version.
So how about following process? :)

I agree with the part that you guys don't understand why the content for a specific release is written in the release_note.md file in main branch. So, I like this approach.
One concern is that in this case, it should be reviewed twice, main branch and release branch. I'm afraid this will slow down release process. :)

Since this file is used by CI, how about put this file into, e.g., ONE-vscode/infra/release/release_note.md?
This will need only one PR approval process and looks simple.

I like this approach too. It is simple and quite fast solution. :)

Since this file is used by CI, how about put this file into, e.g., ONE-vscode/infra/release/release_note.md?
This will need only one PR approval process and looks simple.

I like too :D

I mean, the name of the document is release_notes.md so I expected multiple release notes in this one document. :-D

@dayo09
How about ONE-vscode/infra/release/release_summary.md?

@jyoungyun if we change release_note.md to that position(infra/release/release_note.md), I think we need to update workflow on this
https://github.com/Samsung/ONE-vscode/blob/03cde18c86ac586cd1cfb39f723739eab961767d/.github/workflows/build-release.yml#L236-L241
am I right?

am I right?

Yes, right. Thank you :)

@dayo09 PTAL


suggestion: add "Why" to Readme

As a developer
I want known why
So that I can decide if I should use it or not
My own experience: I could only realize why you did it, when you mention nodejs lib, maybe for someone without that previous knowledge it would be harder.
Nice related content: https://sketchplanations.com/the-golden-circle
Sorry it should be a pull request, but I'm not confident with my English neither the why or pros/cons, of use your lib.

https://github.com/juancarlospaco/cpython#why  ?.
I will try to expand that section of the readme. 🙂


Allow to change Position2D gizmo size

Supposed to fix #7400
Adds gui/common/position2d_gizmo_size property to Project Settings (I wasn't sure where to put it). Unfortunately requires scene reload to refresh and, unless that's acceptable, I'd have to find a way to redraw Position2D on settings change.
@mateusak, is that enough? You also mentioned stuff like color and some inspector settings. Colors could be made configurable (although not sure if 2 additional settings are worth it), but adding node properties automatically saves them in scenes and I doubt anyone would want to keep separate gizmo size for each Position2D.
EDIT:
Well, I realized the color is already configurable via modulate property. So only length should be configurable.

Honestly, I'm kind of against adding another of those almost pointless settings. The settings are already a very bloated area, so for such a minor thing I would rather not add another setting.

Is there any way to make it configurable, other than Editor/Project Settings and inspector properties?

Is there any way to make it configurable, other than Editor/Project Settings and inspector properties?

No. But what I meant is that it should not be configurable.
If the gizmo is not visible / large enough, it's color and size should be automatically computed from the editor zoom or another already configured color. We need to simplify the editor settings, and adding settings for ultra specific things does go against it.

But there are people who prefer it having fixed size.
Not to mention that since 3.1, all 2D nodes have auto-scaling gizmos, which pretty much makes Position2D redundant in favor of simple Node2D...

But there are people who prefer it having fixed size.

Well maybe, but how many ? We have to balance the advantages vs drawback of having to add another setting.
IMHO, the vast majority of Godot users will keep the editor default settings, and will not care much about whether the 2D position gizmo has fixed size or not. If there are any problem with the current design (most likely that the gizmo might be hard to see, even if I think the color change is enough), there are other solutions than creating another cryptic setting, which would worsen the UX in the editor settings for everyone.

@groud Actually, the vast majority (at least of 2D) needs to mess with the project settings as it defaults to a game made in 2005 (default target resolution of 1024px? Really?). The issue with dynamic sizing is that it gets in front of the actual thing it holds when viewing from far. But if it's going to be implemented it needs to be a inspector setting, as not every Position2D is used for the same thing and shouldn't share size.

IMO it would be fine as a Position2D property as suggested by @mateusak, but definitely not as an project wide option.

IMO it would be fine as a Position2D property as suggested by @mateusak, but definitely not as an project wide option.

If we want it, what could be done is having it as an "_edit_gizmo_size" entry in the node's metadata.
Probably editable with a dedicated inspector property editor.

Ok, changed to property:

Not squashing commits until there's final agreement on the changes.

Seems good, could you squash the commits?

Squashed. Also since it's good, I documented the property.

As discussed on PR meeting, I changed the extents to be stored inside metadata, instead as regular property (though you can edit it normally, otherwise it wouldn't be visible in inspector).

As discussed on PR meeting, I changed the extents to be stored inside metadata, instead as regular property (though you can edit it normally, otherwise it wouldn't be visible in inspector).

Arf sorry, I tried to explain it in IRC, but was likely not clear. Sadly, I don't think you can register the property using ADD_PROPERTY, because this is exactly the part that allow the "saver" to recognize the fields that should be written into the tscn file. So if I am not mistaking, with this solution you end up with the property written both as a normal property and in the metadata dictionary.
To solve the problem, none of the functions should be bound to the ClassDB I believe. This requires to create a dedicated inspector plugin I guess, if we want things to be done cleanly.

OMG, you are right. It saves both values ;_;
I'll try to fix this later.

That's what I was referring to by property hints on IRC. PROPERTY_USAGE_DEFAULT | PROPERTY_USAGE_INTERNAL should let the property be displayed in the editor, but its value won't be saved in the scene file (and it shouldn't appear in the docs).

its value won't be saved in the scene file

The thing is that it has to be saved in the scene file. But should only be accessible from the editor (and from GDscript if and only if you use the tool keyword). But yeah, such property hint would be a blessing.

What I mean is that this PR's implementation (saving to metadata) + the property hints (not saving the property to scene) handles the use case just fine.

Turns out PROPERTY_USAGE_STORAGE is responsible for saving the property and is also part of PROPERTY_USAGE_DEFAULT. After some playing with flags I managed to make the extents stored only in meta. Not sure about documentation, as the property isn't there, but getter and setter are.

Added the hint range, not sure about the docs. gizmo_extents don't show there at all, so should I document setter/getter? Or remove PROPERTY_USAGE_INTERNAL to make it show in the docs (which still won't save it to the scene)? Or leave it like it's now, i.e. simply mentioning you can edit the value in inspector?

Right now the setter and getter would appeal in the docs if you run doctool. I just remembered that bound methods starting with _ are automatically ignored in the docs, so if you change set_gizmo_extends and get_gizmo_extents to prefix them with _ (at least in the binding, but I guess it's best to do it also in the C++ signature), it should work as intended (property in the inspector, not saved in tscn, nothing in the docs).

Yeah, the _ thing helped. Hopefully it's finished now.

Thanks!

Produce following compilation warning on macOS:
scene/2d/position_2d.h:40:36: warning: in-class initialization of non-static data member is a C++11 extension [-Wc++11-extensions]
        const float DEFAULT_GIZMO_EXTENTS = 10.0;


feat(http): added support for http2 without ssl

Summary:
SSL for http2 is now optional in this PR. user can spin up backend without cert and key fields
Issue Reference(s):
Fixes #812
/claim #812
Build & Testing:

[x] I ran cargo test successfully.
[x] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[ ] I have added relevant unit & integration tests.
[ ] I have updated the documentation accordingly.
[x] I have performed a self-review of my code.
[ ] PR follows the naming convention of <type>(<optional scope>): <title>

.

Can you resolve the conflicts

Can you resolve the conflicts

Sure

hi @ssddOnTop it's work is in progress.

Closing this for now. @ssddOnTop Let me know if you wish to pick this up.

I think I'll do it while upgrading hyper version


Fix chip_csr_mem_rw_with_rand_reset timeout

This PR contributes to resolving #16489.
The first commit fixes the waiting condition for rom_ctrl after reset (please see commit message for details). With that, the problems observed in #16489 are solved.
However, the test then consistently fails with (use util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -i chip_csr_mem_rw_with_rand_reset -r 28 to reproduce):
* `Offending '(cnt_o == $past(cnt_next_o))'` has 28 failures:
    * Test chip_csr_mem_rw_with_rand_reset has 28 failures.
        * 0.chip_csr_mem_rw_with_rand_reset.1629471500\
          Line 569, in log /home/dev/src/scratch/tlt-debug/chip_earlgrey_asic-sim-vcs/0.chip_csr_mem_rw_with_rand_reset/latest/run.log

                        Offending '(cnt_o == $past(cnt_next_o))'
                UVM_ERROR @ 2029.659897 us: (prim_count.sv:150) [ASSERT FAILED] CntNext_A
                UVM_INFO @ 2029.659897 us: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
                --- UVM Report catcher Summary ---

This assertion failure always occurs just after the second reset (i.e., not the reset at the start of simulation, but the reset triggered by the vseq).
Interestingly, this assertion does not fail on VCS when waves are being dumped (-w vpd), but Xcelium (-t xcelium) times out running the test with any seed.
The second commit, which should not be merged, replaces CntNext_A with a conditional error inside an always @(posedge clk_i) block. Interestingly, this conditional error does not fire and the test passes also in VCS without wave dumping and in Xcelium.
Could this be a simulation scheduling problem, where the assertion is somehow incorrectly scheduled w.r.t. clock and reset?
To solve this problem, should we disable this assertion before reset triggered by the vseq? Or does this error indicate a serious problem that should be debugged further?

I ran the test with your fix (1st commit only) with these settings. They're all passing with 50 seeds.

VCS w/o waves
VCS w/ FSDB
Xcelium w/o waves

This is the log of git ls. VCS version: 2021.09-SP2-1. Xcelium verison: 21-09-006.

874b24121 N - (HEAD -> rerun_pr_16629) [top_earlgrey/dv] Fix waiting for rom_ctrl after reset (6 hours ago)
63686d930 N - [sysrst_ctrl/cov] SYSRST_CTRL FSM coverage fix (13 hours ago)
a351098e1 N - [sysrst_ctrl/dv] Fix failures in sysrst_ctrl_edge_detect test (13 hours ago)
8e274cd2b N - [keymgr] Keymgr doc and dif fixes (13 hours ago)
c93221708 N - [chip-test, kmac] Extend KMAC sideload (13 hours ago)

Not sure if I miss something. If you can still reproduce the issue, perhaps LMK the exact commit ID and seed to reproduce it.

Same here. I reran this with VCS and Xcelium (both no waves) and did not run into this error.
Maybe try with a clean slate & rebase? Also, maybe there are other issues like unkilled simulation jobs conflicting with the same files (this happened to me several times by now)...

Thanks for cross-checking, @weicaiyang and @msfschaffner. I ran the simulation again with --prune and it passed for me, too.


Registry v2

adds controller gluecode for @ehazlett registry-client-api
fixes some view fields
merges with current master

refs https://github.com/shipyard/shipyard/issues/625

now ，we can add registry v2?

Thanks for the contribution.  I'll get it reviewed :)

I clone registry-v2 branch, and docker-compose up, but not support  v2?

still seems to call only v1-api.

We have a PR submitted for supporting V2, please check #852

I think this one can be close, #852 has been merged.

@ehazlett
Think we can close this as per @soninob's comment.


Unclear Storage performance (throughput)

In this page it states that General Purpose VM comes with Premium Storage.
The docs here say that Premium Storage is 3 IOPS per GB.
So, for 100GB you get 300 IOPS. another doc states that IOPS are computed using 256KB units (https://azure.microsoft.com/es-es/blog/introducing-premium-storage-high-performance-storage-for-azure-virtual-machine-workloads/).
So, 300IOPS is at max 300 * 256KB / 1024 = 75MB per second.
Reading the storage docs https://docs.microsoft.com/en-us/azure/virtual-machines/windows/disk-scalability-targets , these Disks are bound to 60MB per second.
Can you clarify calculations? I'm trying to understand how am I to calculate the IO throughput of a machine.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 038ee2b6-8a76-a678-1069-3eb7c2808d73
Version Independent ID: cd6cb2ea-9fff-9237-2168-a39eb24f2677
Content: Pricing tiers for Azure Database for PostgreSQL - Single Server
Content Source: articles/postgresql/concepts-pricing-tiers.md
Service: postgresql
GitHub Login: @jan-eng
Microsoft Alias: janeng

@danield137 Thank you for the detailed feedback.
This is being assigned to the content author to evaluate and update as appropriate.

@danield137, while we use VMs and Premium Storage under the covers, we are using special versions of these offers for our service. Hence the limits are different and so the math you are doing is not correct. There are also other factors playing a role, like the latency per I/O and the size of the I/O, which can vary bases on the workload running against RDBMs. That is why we do not publish these numbers. #please-close


Save resources from validation execution

Is your feature request related to a problem? Please describe.
Sub-task of #301:
In order to reproduce observations, the resources that provided the input to the validation need to be saved, as they are transient across time.
Describe the solution you'd like

Given resources would like to be saved from a lula validate run
When --save-resources is added
Then resources are saved

Describe alternatives you've considered
none
Additional context
none
Expected Deliverable
Adding the functionality to "save resources" to both remote files or the back-matter
Updating existing tests + adding new tests as necessary
Update CLI command docs

In what format would the resources be saved to the back matter? 1 observation == 1 resource item in the backmatter? How much complexity is involved in storing the item and retrieving it from the backmatter?
Similar for external file -> are we expecting to specify the file path?  Are we appending data to an existing default file?
Just to challenge intent here some - Do we need to put this data into the back-matter?

In what format would the resources be saved to the back matter? 1 observation == 1 resource item in the backmatter? How much complexity is involved in storing the item and retrieving it from the backmatter?
Similar for external file -> are we expecting to specify the file path? Are we appending data to an existing default file?
Just to challenge intent here some - Do we need to put this data into the back-matter?

All great questions - I definitely was opinionated on the implementation (see PR) - so I'll answer with what implementation I picked, but obviously subject to a larger discussion

The resources are in the backmatter where the description field is the json data -> they are linked via the link property on the related observation - so yes it's 1:1 observation:resource. Complexity I don't think is bad, I have an initial dev command to pull those resources from the backmatter (need to update for the remote case, see #621)
File path was a little more complicated, but I currently have an individual file output for each resource. It defaults to a directory at the same location as assessment-results called resources where all the .json resides. This was a little trickier, I thought for an initial POC this would suffice for dumping resources externally
Do we need to put the data into the back-matter - probably not.. but since that's the functionality I initially wrote I didn't want to discard it unless we are solidly in the camp of no resource in back-matter.


Add an option for using the jump list like tag stack

I am not able to reopen the previous PR (https://github.com/vim/vim/pull/7738).  So opening a new one.
Port the "jumpoptions" support from NeoVim:
https://neovim.io/doc/user/motion.html#jumplist-stack
https://github.com/neovim/neovim/commit/39094b3faedde9601160806901941e4808925410
https://github.com/neovim/neovim/pull/11530
https://vi.stackexchange.com/questions/18344/how-to-change-jumplist-behavior
Based on the feedback in the previous PR, it looks like many people like this option.
Bram wanted a much more elaborate infrastructure (similar to the undo tree) that is based on
timestamps to go back in time to different jump locations.  This will take quite a bit of effort
to implement.  So instead we can with this option for now.

thanks. sounds like there is some demand for this, so let me include this.

sounds like there is some demand for this,

not sure if i had readed or tried correctly, this seems made ctrl-i useless, was that really useful demand or it is a bug of this.

sounds like there is some demand for this,

not sure if i read or tried correctly, this seems made ctrl-i useless, was that really a useful demand or it is a bug of this.

sounds like there is some demand for this,

not sure if i read or tried correctly, this seems made ctrl-i useless, was that really a useful demand or it is a bug of this.

The CTRL-O/CTRL-I commands to browse the jump list still work.  Note that without this option, if you go back
in the jump list using CTRL-O and then jump to a new location, the new jump location will be added to the end
of the jump list.  Now if you press CTRL-O, it will go to a different location (confusing the users).  With this option,
the jump list will behave like the tag stack.  Please refer to the previous PR for the comments and also you can
try this option out in the latest Vim.

There is a thread in Vi stack exchange about this: https://vi.stackexchange.com/questions/18344/how-to-change-jumplist-behavior

as my understanding, the traditional one maybe a bit messed order after ctrl-o and new jump,
but this added 'stack' one may clear the record, i felt did not it make case be worse?
a.k.a bram said based on timestamp maybe was the right one IF really want to refine.

Think of it as using the browser based forward/backward navigations.
This may actually make me use the jumplist, because I always found it to be too confusing where to jump next.
Yes a timestamp based navigation (similar to the undo-stack) may be even more desirable, but we then have to think about additional commands to navigate into the different branches (and it may still be confusing then)

because I always found it to be too confusing where to jump next

yes, that traditional one sometime made me feel confused too,
but i may like keeping the jump list history there too, this added 'stack' one made me feel it worse.

well, if you don't have to use this option.

yes, i did not and would not set it.
but, hi, my point was let's keeping the style which bram or classic vim's style which preferred to add confirmed refined one, vs not a mid-stage of something, a.k.a not just someone said it is neovim or so-called IDE style then hurry to add it.
// and i doubt was this really a IDE style?


Bump<EMAIL_ADDRESS>& dogfood ref support throughout Evergreen

Overview
Now that ui-box officially uses forwardRef to enable ref support to underlying <Box /> components, this PR upgrade ui-box to next major, and updates any references to <Box innerRef={...} /> to <Box ref={...} />. In addition, it updates several callsites to directly pass ref through instead of innerRef,  especially now that a vast majority of Evergreen has forwardRef.
Screenshots (if applicable)
N/A -- looked through Storybook extensively, and component behavior seems intact.
Testing

[ ] Updated Typescript types and/or component PropTypes
[x] Added / modified component docs
[ ] Added / modified Storybook stories

@mshwery yep, that's the idea!

Any update here @akleiner2 ?

@mshwery Need to rebase on latest v5. @colinlohner will likely need to rebase his table PR too. Will push through today! thanks for the nudeg


Electron compatibility

This represents the few bits and bobs I had to change to get the shell to actually launch and render (cool!) on my machine. I couldn't figure out whether you were using a beta release of Electron or tracking master, but when I updated the package.json to depend on Electron v2.0.0-beta.1 it seemed to work.
I also added a rudimentary README to xray_electron with what I believe are accurate instructions for getting it built and running.

Awesome. Thanks for this. Early on, the only way to build was via a source build of Electron, but it seems like the latest beta works. I see you dropped the resize observer polyfill. We may need that eventually in order to ship a browser-compatible build. Alternatively, we can just require the embedder to manually signal that a resize has occurred.


heavy window

Describe the bug
The window can't be moved
To Reproduce
Use FrostedGlass
Try to move the window
Infomation (please complete the following information)
Discord channel: Stable/
OS: Windows
Mod: BetterDiscord
Discord language: English

Update: this seems to be a very obscure issue with the title bar, but dragging from the search bar can move the window. However, the window is not auto-sized at all

You have plenty of room to play with. I've tested this on multiple themes and all work just fine.
Example:
https://github.com/DiscordStyles/FrostedGlass/assets/20338746/6fd9c5cd-7ac7-40c1-b003-7b9f38d37636
But if you wish, you can add:
:root {
  --TB-bar-height: 15px;
}

To increase the height to make it easier to grab.


Preview8 query casting

Since preview6 query casting seems to have stopped working. In preview5 the following works:
 var uniqueItem = await someQuery
      .Cast<IEntityWithUniqueValue>()
      .Select(m => new { m.Id, m.Unique })
      .FirstOrDefaultAsync();

However, since preview6 and in the latest preview8 I'm getting:

Operation is not valid due to the current state of the object. ---> System.InvalidOperationException: Operation is not valid due to the current state of the object. at Microsoft.EntityFrameworkCore.Query.RelationalQueryableMethodTranslatingExpressionVisitor.TranslateWhere(ShapedQueryExpression source, LambdaExpression predicate) at Microsoft.EntityFrameworkCore.Query.QueryableMethodTranslatingExpressionVisitor.VisitMethodCall(MethodCallExpression methodCallExpression) at Microsoft.EntityFrameworkCore.Query.QueryableMethodTranslatingExpressionVisitor.VisitMethodCall(MethodCallExpression methodCallExpression) at Microsoft.EntityFrameworkCore.Query.QueryCompilationContext.CreateQueryExecutor[TResult](Expression query) at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.<>c__DisplayClass12_01.b__0() at Microsoft.EntityFrameworkCore.Query.Internal.CompiledQueryCache.GetOrAddQueryCore[TFunc](Object cacheKey, Func1 compiler) at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.ExecuteAsync[TResult](Expression query, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Query.Internal.EntityQueryProvider.ExecuteAsync[TResult](Expression expression, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ExecuteAsync[TSource,TResult](MethodInfo operatorMethodInfo, IQueryable1 source, Expression expression, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ExecuteAsync[TSource,TResult](MethodInfo operatorMethodInfo, IQueryable1 source, LambdaExpression expression, CancellationToken cancellationToken)

I can workaround this with dynamic where condition, but it would be nice to leverage the strongly typed properties.
Or is the Cast no longer supported this way?

Notes for triage: I misunderstood previously and thought general use of IQueryable<InterfaceType> was not working. In fact, it is only explicitly using Cast or OfType that is not working. Essentially a duplicate of #16429 but with different motivation.

Note for triage: this does work:
IQueryable untypedBlogs = context.Set<Blog>();

var blogs = (IQueryable<IEntityWithUniqueValue>)untypedBlogs;

var uniqueItem = blogs
    .Select(m => new { m.Id, m.Unique })
    .FirstOrDefault();


Add support for non-hermitian operators in AerPauliExpectation

Summary
QEOM creates a dictionary of operators to evaluate on the groundstate.
When using the noisy simulators (qasm_simulator or aer_simulator), one
could either use PauliExpectation (with noise) or AerPauliExpectation
(without noise). PauliExpectation works with non-hermitian operators
but internal methods of AerPauliExpectation raised an Error.
This is a workaround to this limitation.
Note that using include_custom=True on qasm allows the VQE to use a
local AerPauliExpectation without using the "expectation" input.
This does not apply to QEOM and one should explicitly define the
"expectation" input of the VQE for it to apply globally.

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

Hi Anthony, could you add a test that checks that the AerPauliExpectation now works with non-hermitian observables and returns the same value as the other expectation converters? 🙂 Also, could you add a releasenote? See here on how to do that.

I changed the line giving the pylint error (I thought It was only a warning at first). Basically just all(k.is_hermitian() for k in ...) instead of all([k.is_hermitian() for k in ...])

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

9 of 9 (100.0%)  changed or added relevant lines in 1 file are covered.
69 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.008%) to 83.724%

Files with Coverage Reduction
New Missed Lines
%

qiskit/utils/run_circuits.py
69
31.62%

Totals

Change from base Build<PHONE_NUMBER>:
0.008%

Covered Lines:
54002

Relevant Lines:
64500

💛  - Coveralls


build example images need to be updated

Link
https://buildtest.readthedocs.io/en/latest/build_subcommand/build.html#hello-world-c
Actual Content

What is the issue?
The two images need to updated because content of test script has changed. Need to rebuild test and generate image again

@vsoch
it may be easier to just remove this image and rewrite the docs once we have a new YAML schema.
I can take this task and resolve it.
The docs for build are depened upon completing #135 and #168

This task is complete


General expand function

Create an extendible expand function (similar to _expand) that can:

Find all holes
Take a function that picks a hole. This function should probably take the current program and the paths to the holes, similar to how the propagate function for constraints works.

Currently, the search can only fill the first child of a node.
The children of a rulenode are a vector, and once a child is expanded, a new RuleNode is pushed to this vector.
Therefore, we can only expand a hole once all 'sibling' holes on the left are filled.
To make this general expand function work, we need to change how this works.
I think the best way to solve this is by introducing a special 'hole' RuleNode, e.g. a rulenode with ind=0 that we can use as a placeholder or by instantiating the children as a vector filled with 'nothing'.

I agree it is a good idea to explicitly introduce a 'hole' node. RuleNodewith ind=0 is a good convention for that.
Do you expect that the ability to fill in holes in different orders will impact some of the methods significantly? We anyways cannot evaluate an expression until all of its 'hole' children are filled.

I don't think there will be a big impact on existing methods. Of course, the expand function has to be modified, and we do need to check existing functions for e.g. length(node.children). I know I have used this a couple of times to check whether all holes are filled, but I think this is mainly in the SpecificationExtraction repository.
It might also be a good idea to add a check to the rulenode2expr function for when you are trying to convert a partial tree to an expression. Right now you would probably get some index out of range exception.

Good idea! We should definitely make the holes more explicit.


platformio-ide-terminal cannot be installed

[x] I have reset Atom to defaults prior to submitting report.
[ ] I have not reset Atom to defaults prior to submitting report.

Description

Steps to reproduce

Expected behavior:
Actual behavior:
Reproduces how often:
Versions

> atom --version

> apm --version

OS name and version:
Platformio-ide-terminal version:
Additional Information

Empty tickets are closed and locked


swagger-output.json file isn't generated and no errors are thrown.

Hi, I was trying to add swagger-autogen to a newly started project, but the swagger-out.json file isn't generated and no errors are shown either. Is there any compatibility issue that I'm unaware of or am I just doing something wrong?
Node version: 16.17.0
Express: 4.18.1
Import Type: ES5 Module imports
Repo Link - https://github.com/NovelThoughts/iClass-BE
Thanks.

Hi @Apurva-Nagar! Thank you for opening the issue and for the sample project.
For now, the swagger-autogen doesn't recognise relative paths, so for now, you'll need to change your relative path ../index.js to ./index.js. But there is an opened issue about this #159 and I hope fix it as soon as possible.
Another thing it's the () missing on the function swaggerAutogen:
Instead of:
swaggerAutogen(outputFile, endpointsFiles, doc);
Change to:
swaggerAutogen()(outputFile, endpointsFiles, doc);
How it's a known issue, I'm going to close it, but if this changes doesn't work there, let me know.

Thanks, that worked 😃


Is it possible to add a command for editable installs?

I find myself repeating this workflow often when switching between branches:
./spin build -j 6 --clean
pip install --no-build-isolation --editable .

It's quite annoying because I always have to google to make sure I'm writing this pip install editable command correctly. I'm wondering if it's sensible to package this into a single command, install, which has the editable flag by default. Since this is a "developer tool" package, I assume this is reasonable.
Xref: https://meson-python.readthedocs.io/en/latest/how-to-guides/editable-installs.html

That'd be great, Adam! Yes, how about we put it in spin.cmds.pip.install?


Adjust all other models according to ticket 111 serialization/deserialization issue fix

In #109 Adjusted the most of the models except: \spaf\simputils\models\InitConfig and \spaf\simputils\models\PhpInfo
The \spaf\simputils\models\InitConfig should not be adjusted for that purpose due to it's potential complexity and lack of reason for it for now.
The \spaf\simputils\models\PhpInfo is not adjusted temporary, due to extreme complexity of implementation. It will be adjusted in the future. Such functionality for caching PHP Info data easily can be handy for many people!


GPU isn't being utilized when running MDX models

My GPU stays idle at 1% and CPU use jumps to 100% when I run any MDX models.

Tried to install a new version of cuda and it made the problem even worse, now I can't run the GPU conversion at all.
Last Error Received:

Process: MDX-Net

If this error persists, please contact the developers with the error details.

Raw Error Details:

RuntimeError: "D:\a\_work\1\s\onnxruntime\python\onnxruntime_pybind_state.cc:548 onnxruntime::python::CreateExecutionProviderInstance CUDA_PATH is set but CUDA wasn't able to be loaded. Please install the correct version of CUDA and cuDNN as mentioned in the GPU requirements page (https://onnxruntime.ai/docs/reference/execution-providers/CUDA-ExecutionProvider.html#requirements), make sure they're in the PATH, and that your GPU is supported.
"
Traceback Error: "
  File "UVR.py", line 4716, in process_start
  File "separate.py", line 280, in seperate
  File "onnxruntime\capi\onnxruntime_inference_collection.py", line 335, in __init__
  File "onnxruntime\capi\onnxruntime_inference_collection.py", line 381, in _create_inference_session
"

Error Time Stamp [2023-08-17 19:48:55]

Full Application Settings:

vr_model: Choose Model
aggression_setting: 10
window_size: 512
batch_size: Default
crop_size: 256
is_tta: False
is_output_image: False
is_post_process: False
is_high_end_process: False
post_process_threshold: 0.2
vr_voc_inst_secondary_model: No Model Selected
vr_other_secondary_model: No Model Selected
vr_bass_secondary_model: No Model Selected
vr_drums_secondary_model: No Model Selected
vr_is_secondary_model_activate: False
vr_voc_inst_secondary_model_scale: 0.9
vr_other_secondary_model_scale: 0.7
vr_bass_secondary_model_scale: 0.5
vr_drums_secondary_model_scale: 0.5
demucs_model: Choose Model
segment: Default
overlap: 0.25
shifts: 2
chunks_demucs: Auto
margin_demucs: 44100
is_chunk_demucs: False
is_chunk_mdxnet: False
is_primary_stem_only_Demucs: False
is_secondary_stem_only_Demucs: False
is_split_mode: True
is_demucs_combine_stems: True
demucs_voc_inst_secondary_model: No Model Selected
demucs_other_secondary_model: No Model Selected
demucs_bass_secondary_model: No Model Selected
demucs_drums_secondary_model: No Model Selected
demucs_is_secondary_model_activate: False
demucs_voc_inst_secondary_model_scale: 0.9
demucs_other_secondary_model_scale: 0.7
demucs_bass_secondary_model_scale: 0.5
demucs_drums_secondary_model_scale: 0.5
demucs_pre_proc_model: No Model Selected
is_demucs_pre_proc_model_activate: False
is_demucs_pre_proc_model_inst_mix: False
mdx_net_model: UVR-MDX-NET Voc FT
chunks: Auto
margin: 44100
compensate: Auto
is_denoise: False
is_invert_spec: False
is_mixer_mode: False
mdx_batch_size: 2
mdx_voc_inst_secondary_model: No Model Selected
mdx_other_secondary_model: No Model Selected
mdx_bass_secondary_model: No Model Selected
mdx_drums_secondary_model: No Model Selected
mdx_is_secondary_model_activate: False
mdx_voc_inst_secondary_model_scale: 0.9
mdx_other_secondary_model_scale: 0.7
mdx_bass_secondary_model_scale: 0.5
mdx_drums_secondary_model_scale: 0.5
is_save_all_outputs_ensemble: True
is_append_ensemble_name: False
chosen_audio_tool: Manual Ensemble
choose_algorithm: Min Spec
time_stretch_rate: 2.0
pitch_rate: 2.0
is_gpu_conversion: True
is_primary_stem_only: False
is_secondary_stem_only: False
is_testing_audio: False
is_add_model_name: False
is_accept_any_input: False
is_task_complete: False
is_normalization: False
is_create_model_folder: False
mp3_bit_set: 320k
save_format: WAV
wav_type_set: PCM_16
help_hints_var: False
model_sample_mode: False
model_sample_mode_duration: 30
demucs_stems: All Stems

Tried to install a new version of cuda and it made the problem even worse, now I can't run the GPU conversion at all.
Last Error Received:

Process: MDX-Net

If this error persists, please contact the developers with the error details.

Raw Error Details:

RuntimeError: "D:\a\_work\1\s\onnxruntime\python\onnxruntime_pybind_state.cc:548 onnxruntime::python::CreateExecutionProviderInstance CUDA_PATH is set but CUDA wasn't able to be loaded. Please install the correct version of CUDA and cuDNN as mentioned in the GPU requirements page (https://onnxruntime.ai/docs/reference/execution-providers/CUDA-ExecutionProvider.html#requirements), make sure they're in the PATH, and that your GPU is supported.
"
Traceback Error: "
  File "UVR.py", line 4716, in process_start
  File "separate.py", line 280, in seperate
  File "onnxruntime\capi\onnxruntime_inference_collection.py", line 335, in __init__
  File "onnxruntime\capi\onnxruntime_inference_collection.py", line 381, in _create_inference_session
"

Error Time Stamp [2023-08-17 19:48:55]

Full Application Settings:

vr_model: Choose Model
aggression_setting: 10
window_size: 512
batch_size: Default
crop_size: 256
is_tta: False
is_output_image: False
is_post_process: False
is_high_end_process: False
post_process_threshold: 0.2
vr_voc_inst_secondary_model: No Model Selected
vr_other_secondary_model: No Model Selected
vr_bass_secondary_model: No Model Selected
vr_drums_secondary_model: No Model Selected
vr_is_secondary_model_activate: False
vr_voc_inst_secondary_model_scale: 0.9
vr_other_secondary_model_scale: 0.7
vr_bass_secondary_model_scale: 0.5
vr_drums_secondary_model_scale: 0.5
demucs_model: Choose Model
segment: Default
overlap: 0.25
shifts: 2
chunks_demucs: Auto
margin_demucs: 44100
is_chunk_demucs: False
is_chunk_mdxnet: False
is_primary_stem_only_Demucs: False
is_secondary_stem_only_Demucs: False
is_split_mode: True
is_demucs_combine_stems: True
demucs_voc_inst_secondary_model: No Model Selected
demucs_other_secondary_model: No Model Selected
demucs_bass_secondary_model: No Model Selected
demucs_drums_secondary_model: No Model Selected
demucs_is_secondary_model_activate: False
demucs_voc_inst_secondary_model_scale: 0.9
demucs_other_secondary_model_scale: 0.7
demucs_bass_secondary_model_scale: 0.5
demucs_drums_secondary_model_scale: 0.5
demucs_pre_proc_model: No Model Selected
is_demucs_pre_proc_model_activate: False
is_demucs_pre_proc_model_inst_mix: False
mdx_net_model: UVR-MDX-NET Voc FT
chunks: Auto
margin: 44100
compensate: Auto
is_denoise: False
is_invert_spec: False
is_mixer_mode: False
mdx_batch_size: 2
mdx_voc_inst_secondary_model: No Model Selected
mdx_other_secondary_model: No Model Selected
mdx_bass_secondary_model: No Model Selected
mdx_drums_secondary_model: No Model Selected
mdx_is_secondary_model_activate: False
mdx_voc_inst_secondary_model_scale: 0.9
mdx_other_secondary_model_scale: 0.7
mdx_bass_secondary_model_scale: 0.5
mdx_drums_secondary_model_scale: 0.5
is_save_all_outputs_ensemble: True
is_append_ensemble_name: False
chosen_audio_tool: Manual Ensemble
choose_algorithm: Min Spec
time_stretch_rate: 2.0
pitch_rate: 2.0
is_gpu_conversion: True
is_primary_stem_only: False
is_secondary_stem_only: False
is_testing_audio: False
is_add_model_name: False
is_accept_any_input: False
is_task_complete: False
is_normalization: False
is_create_model_folder: False
mp3_bit_set: 320k
save_format: WAV
wav_type_set: PCM_16
help_hints_var: False
model_sample_mode: False
model_sample_mode_duration: 30
demucs_stems: All Stems

I solved this, took me long enough and I'm not sure which one of these steps was the correct one but here is basically everything I did:
I think the problem lied in a wrong CUDA version. You need to have cuda 11.6, check if your GPU is compatible here

Uninstall CUDA if you have it installed
Uninstall Ultimate Vocal Remover and be sure to delete the folder it lives in
Install CUDA version 11.6
Install cuDDN version <IP_ADDRESS> (Windows)
Install pytorch https://pytorch.org/get-started/locally/
reinstall ultimate vocal remover

install CUDA
https://developer.nvidia.com/cuda-downloads
how to install cuddn
https://docs.nvidia.com/deeplearning/cudnn/install-guide/index.html#installdriver-windows
and when u copy the cuddn .dll files to the CUDA folder be sure to put the lib files in both the lib/x64 folder and the lib folder.

I solved this, took me long enough and I'm not sure which one of these steps was the correct one but here is basically everything I did:
I think the problem lied in a wrong CUDA version. You need to have cuda 11.6, check if your GPU is compatible here

Uninstall CUDA if you have it installed
Uninstall Ultimate Vocal Remover and be sure to delete the folder it lives in
Install CUDA version 11.6
Install cuDDN version <IP_ADDRESS> (Windows)
Install pytorch https://pytorch.org/get-started/locally/
reinstall ultimate vocal remover

install CUDA https://developer.nvidia.com/cuda-downloads how to install cuddn https://docs.nvidia.com/deeplearning/cudnn/install-guide/index.html#installdriver-windows and when u copy the cuddn .dll files to the CUDA folder be sure to put the lib files in both the lib/x64 folder and the lib folder.

do you know, what if program will get cuda 12.2?


vim support

Hi, I can see that the Editor is powered by Monaco.
I'm using Vim mode in VSCode and very happy with it.
Can Rekit editor able to implement vim?

Maybe in future but not in the roadmap for now.


Why the calculation of anomaly_scores of test data need to use its groundtruth label?

In the trainner.test(), it seems the calculation of anomaly_scores of test data need to use its groundtruth label?  It may be unresonable?

Hey. As you can see here, the loss function ignores labels as long as the network is in eval mode, and, as you can see here, for testing the network indeed is in eval mode. So, no worries ;)

Hey. As you can see here, the loss function ignores labels as long as the network is in eval mode, and, as you can see here, for testing the network indeed is in eval mode. So, no worries ;)

My problems is solved. Thank you very much!


Automated cherry pick of #491: Bump aws sdk go to v1.44.107

Cherry pick of #491 on release-0.5.
#491: Bump aws sdk go to v1.44.107
For details on the cherry pick process, see the cherry pick requests page.

/ok-to-test

Hm, we must be missing some commits from this release branch.

/retest


Share and Path values

I'm having trouble getting this library to work.  I gotten it to the point where log4net is no longer complaining loading the appender, but it still isn't logging.  I'm wondering if it is the parameters that I'm setting.  Is Share supposed to be the container and Path the folder?  Are both required?

You must specify AzureStorageConnectionString, which you can get from the Azure portal in storage settings, either primary or secondary. It needs to be the full connection string, not just the key.
The ShareName must also be given. It's the name of the share within file storage I which the logs will be created. Example: "logs"
The path can be set to a folder within the share, example: "myapp"
You also need to specify the File, as the file name template.
Check out the README file for examples, this should get you going.


Bump to dj >4

This would close #2853; not tested manually.

So far I found 2 problems:

django-error-report is very much unmaintained. I made upgrades needed for 4.0 a while ago for something else so I switched to my fork for testing. We should consider moving to something else.
As far as I see, MPTT is unmaintained and not ready for Django 4.0. See their changelogs.

Ok the dependencies are solved mainly; a few functions need to be rewritten because they were removed with the switch to 4.0

And the next breaking change that needs to be included.

Ok down to one error after updating inventree-zapier for Django 4.0

We should be golden now. @SchrodingersGat I think we could take the plunge to Django 4.x with the LTS for 4.2 now released. Thoughts?

Discovered a fresh Django bug with Postgres: https://code.djangoproject.com/ticket/34459

We will need for 4.2.1 / probably May 1st for this to be mergeable

Not stale

With django-mptt unmaintained, what is your opinion on moving forward to django 4?

There multiple changes that would require rewriting and all replacements for mptt I looked at are less efficient so I would let this one go for now.

Is there an replacement library for mptt?

@wolflu05 there are a bunch of them with varying degree of maturity and user base. The query efficiency of mptt is just top-notch.

MPTT is a very good library - it is unfortunate that it is not receiving any active maintenance :'(


Can't upload immunarch formated table.

🐛 Bug

immunarch formated files are not being imported
To Reproduce
Steps to reproduce the behavior:
1.immdata = repLoad(.path = "AF.tsv", .format = 'immunarch')
2.
3.

Error in `[[<-.data.frame`(`*tmp*`, IMMCOL$cdr3nt, value = logical(0)) :
  replacement has 0 rows, data has 3

AF.tsv.zip
Expected behavior

I should be able to import it into an immdata object
Additional context

Hi @tiagobrc !
We published immunarch on CRAN and moved it to GitHub, feel free to install the latest versions and check if everything is OK. I'm closing this issue for now, please feel free to reopen it in case of more related questions.


transition news to using worldstate

workin on this with https://github.com/aliasfalse/warframe-worldstate-parser

available in dev, #33


ios get crash

When i select video to compress and minimize app while compressing in ios get crashed . But it working fine in android
getting below error
terminating with uncaught exception of type NSException
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '*** -[AVAssetReader startReading] cannot be called again after reading has already started'
terminating with uncaught exception of type NSException

how to make it work?


Thank you for your excellent work，I have some questions about this experimental analysis.

1.Baseline models such as DiffuSeq do not use the enhancement noise factor F during fast sampling, so they do not set K as low as your 20 during sampling. Did you set them equally to K=20 during the comparison process or did you leave the original model unchanged?
2.The score without the noise factor in the ablation experiment was only 2.85, so why is there such a huge gap?Does this cause include the factors present in the first question?
3.in 5.3 Ablation Experiments section, Figure 5 is a bit unclear to me.The dashed part is where you feed pure Gaussian noise to the denoiser at each diffusion step so that it predicts X0. The solid part is where you feed Gaussian noise only at T = 2000 steps and then iterate sequentially to get X0 each time?
Thank you!

Hi, thanks for your interest in our work, and sorry for the late response.

We leave the number of sampling steps for baselines unchanged.
We have further tuned the hyper-parameters under this condition, and this value should be updated to 21.46.
The dashed lines in Fig. 5 are like what you said. The solid lines are drawn by evaluating predicted z0_hat at each t during a whole generation process.

Hi, thanks for your interest in our work, and sorry for the late response.

We leave the number of sampling steps for baselines unchanged.
We have further tuned the hyper-parameters under this condition, and this value should be updated to 21.46.
The dashed lines in Fig. 5 are like what you said. The solid lines are drawn by evaluating predicted z0_hat at each t during a whole generation process.

Hello author, I have a few questions to ask you, thank you！
1.Whether the layer normalization directly uses the functions on fairseq's default Embedding？this is -> nn.init.normal_(self.word_embedding.weight , mean=0, std=self.in_channels ** -0.5)
2.Are parameters shared between the Word embedding and logits layers?
3.When I use your anchoring loss function, grid_norm starts with inf, then goes down, at some stage it gets big again, then goes down again, then gets big again, and then goes up all the way, whereas with round_loss it doesn't, can you give me some tips? thank you.
I am looking forward to your reply

The implementation of the embedding normalization lies here https://github.com/zhjgao/difformer/blob/62c7dd732a0494732847fbc21607366510114e5b/difformer/modules.py#L85
Yes, we tie the parameters of the embeddings and the output layer.
We have not encountered the phenomenon you mentioned. Modifications to --lr, --max-tokens, and --clip-norm may be helpful.


Unable to use three finger swipe with voiceover to swipe left or right.

Is this a bug report, a feature request, or a question?
Question

I am trying to swipe on the card using a three finger swipe while using voice over on iOS. I am not able to do so. Is there a way to implement this.
Have you followed the required steps before opening a bug report?
(Check the step you've followed - put an x character between the square brackets ([]).)

[] I have read the guidelines regarding bug report.
[x] I have reviewed the documentation in its entirety, including the dedicated documentations :books:.
[x] I have searched for existing issues and made sure that the problem hasn't already been reported.
[x] I am using the latest plugin version.
[] I am following the issue template closely in order to produce a useful bug report.

Have you made sure that it wasn't a React Native bug?
Yes

Is the bug specific to iOS or Android? Or can it be reproduced on both platforms?
(Write your answer here and specify the iOS/Android versions on which you've been able to reproduce the issue.)
Is the bug reproductible in a production environment (not a debug one)?
(Write your answer here.)

Environment

Environment:
"react-native": "^0.59.9",
"react-native-snap-carousel": "^3.8.0",
Target Platform:
iOS 12
iOS 13.1.2
Expected Behavior

To mimic single finger swipe when voice over isn't on
Actual Behavior

Nothing happens
Reproducible Demo
(Paste the link to a Snack example in which the issue can be reproduced. Please follow the guidelines for providing a Minimal, Complete, and Verifiable example.)

Steps to Reproduce

(Write your steps so that anyone can reproduce the issue in the Snack demo you provided.)

@anikasetia Are you able to get this working with a regular FlatList?

I was able to swipe and scroll flatlist and scrollview using 3 fingers

@bd-arc I have the same issue and FlatList is working correctly.
Environment:
"react-native": "0.61.2",
"react-native-snap-carousel": "3.8.4"
Also I had to manually set accessible status to renderItems. All renderItems were accessible and not only the current renderItem.

Sorry, please allow me to advertise for my open source library! ~
I think this library react-native-reanimated-carousel will solve your problem. It is a high performance and very simple component, complete with React-Native reanimated 2


Allow bindind values of all intrinsic integral types

Allow bindind values of all intrinsic integral types.
Allows direct binding of all intrinsic integral types without intermediate variables defined as int32_t or uint32_t, etc.
However, C++11 does not guarantee std::intXY_t are defined as aliases to intrinsic integral types, this commit assumes the aliases are not indifferent and shifts the priority towards the intrinsic types.

Regarding the last note above, C99/C++11 standards references can be found in answers to Are the fixed width integer types guaranteed to be typedefs for the standard built in types?

After a few iterations this PR is now ready to review.
@lexicalunit  What do you think of it?

Very cleanly done template metaprogramming. I agree and like this better than the std::intXY_t approach. Tests all pass and the code looks correct to me. 🎉

Great, thanks!


windows-2022 image does not include .NET 4.7 Targetting Pack

Description
The windows-2022 image does not include the .NET 4.7 Targetting Pack (compared to windows-2019). This causes issues in some of our multi-targetted libraries, that target net47.
Can you add it back?

windows-2022
vs
windows-2019

Virtual environments affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016
[ ] Windows Server 2019
[X] Windows Server 2022

Image version and build link
Environment: windows-2022
Version: 20211219.1
Included Software: https://github.com/actions/virtual-environments/blob/win22/20211219.1/images/win/Windows2022-Readme.md
Image Release: https://github.com/actions/virtual-environments/releases/tag/win22%2F20211219.1
Is it regression?
No response
Expected behavior
No response
Actual behavior
No response
Repro steps
Create a project that targets .NET 4.7 and try to build it on the image.

Hey, @Styxxy
Please provide a simple repo how to reproduce the issue.

@al-cheb Do you need me to create the most dummy basic .NET 4.7 repo?
Hereby the steps:

Open Visual Studio 2022 (make sure you have the .NET 4.7 Targetting Pack installed).
Create new project -> Console App (.NET Framework) -> choose .NET 4.7 as targetting platform.
Commit
Try building it on windows-2022.

@Styxxy , Could you check if the snippet above fix your issue?

@Styxxy , Could you check if the snippet above fix your issue?

It might work, but does add a lot of overhead to pipelines to include that snipped, rather than have it by default included in the image (like it was with windows-2019)?

@Styxxy , Could you check if the snippet above fix your issue?

It might work, but does add a lot of overhead to pipelines to include that snipped, rather than have it by default included in the image (like it was with windows-2019)?

We need to be sure that this fix the issue, maybe we will add some more components.

@Styxxy , Could you check if the snippet above fix your issue?

It might work, but does add a lot of overhead to pipelines to include that snipped, rather than have it by default included in the image (like it was with windows-2019)?

We need to be sure that this fix the issue, maybe we will add some more components.

Ok, will try to test tomorrow to make sure it works.

@Styxxy , Could you check if the snippet above fix your issue?

It might work, but does add a lot of overhead to pipelines to include that snipped, rather than have it by default included in the image (like it was with windows-2019)?

We need to be sure that this fix the issue, maybe we will add some more components.

I tested and it works, but ... It adds another 5 minutes to the execution time, which is not something I would consider as acceptable.

@Styxxy, I have create a https://github.com/actions/virtual-environments/pull/4874 PR to add Net.Component.4.7.TargetingPack component.  The new image will be deployed next week.

@Styxxy, I have create a #4874 PR to add Net.Component.4.7.TargetingPack component. The new image will be deployed next week.

Great, thanks!

@Styxxy, the image with Microsoft.Net.Component.4.7.TargetingPack on board has been deployed.
https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md

@jcansdale the minimal targeting pack for VS2022 is
Microsoft.Net.Component.4.5.2.TargetingPack
https://docs.microsoft.com/en-us/visualstudio/install/workload-component-id-vs-enterprise?view=vs-2022

Interesting. Thanks for taking a look!


feat: initial duck context api implementation

Description

Changes

Add initial api and documentation

Checklist

[x] This PR has updated documentation
[x] This PR has sufficient testing

Comments

Addition comments for reviewers

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: