ChefDK 0.17.17 - `join': No live threads left. Deadlock?

Description
chef verify fails in 0.17.17 on OS X 10.10.5
ChefDK Version
Chef Development Kit Version: 0.17.17
chef-client version: 12.6.0
delivery version: master (f68e5c5804cd7d8a76c69b926fbb261e1070751b)
berks version: 4.3.5
kitchen version: 1.11.1
Platform Version
OS X 10.10.5
Replication Case

Completely remove the old version of ChefDK, including rm -rf ~/.chefdk and sudo rm -rf /opt/chefdk
Install v0.17.17 of ChefDK
Run chef verify

Stacktrace
Running verification for component 'berkshelf'
Running verification for component 'test-kitchen'
Running verification for component 'tk-policyfile-provisioner'
Running verification for component 'chef-client'
Running verification for component 'chef-dk'
Running verification for component 'chef-provisioning'
Running verification for component 'chefspec'
Running verification for component 'generated-cookbooks-pass-chefspec'
Running verification for component 'rubocop'
Running verification for component 'fauxhai'
Running verification for component 'knife-spork'
Running verification for component 'kitchen-vagrant'
Running verification for component 'package installation'
Running verification for component 'openssl'
Running verification for component 'inspec'
Running verification for component 'delivery-cli'
Running verification for component 'git'
Running verification for component 'opscode-pushy-client'
Running verification for component 'chef-sugar'
..........

Finished in 0.12592 seconds (files took 4.75 seconds to load)
0 examples, 0 failures

/Users/sneal/.chefdk/gem/ruby/2.1.0/gems/berkshelf-4.3.5/lib/berkshelf/installer.rb:27:in `join': No live threads left. Deadlock? (fatal)
    from /Users/sneal/.chefdk/gem/ruby/2.1.0/gems/berkshelf-4.3.5/lib/berkshelf/installer.rb:27:in `map'
    from /Users/sneal/.chefdk/gem/ruby/2.1.0/gems/berkshelf-4.3.5/lib/berkshelf/installer.rb:27:in `build_universe'
    from /Users/sneal/.chefdk/gem/ruby/2.1.0/gems/berkshelf-4.3.5/lib/berkshelf/installer.rb:161:in `install_from_universe'
    from /Users/sneal/.chefdk/gem/ruby/2.1.0/gems/berkshelf-4.3.5/lib/berkshelf/installer.rb:39:in `run'
    from /Users/sneal/.chefdk/gem/ruby/2.1.0/gems/berkshelf-4.3.5/lib/berkshelf/berksfile.rb:421:in `install'
    from /Users/sneal/.chefdk/gem/ruby/2.1.0/gems/berkshelf-4.3.5/lib/berkshelf/berksfile.rb:630:in `block in vendor'
    from /opt/chefdk/embedded/lib/ruby/2.1.0/tmpdir.rb:88:in `mktmpdir'
    from /Users/sneal/.chefdk/gem/ruby/2.1.0/gems/berkshelf-4.3.5/lib/berkshelf/berksfile.rb:628:in `vendor'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chefspec-4.7.0/lib/chefspec/berkshelf.rb:39:in `block in setup!'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/shell/basic.rb:20:in `mute'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chefspec-4.7.0/lib/chefspec/berkshelf.rb:35:in `setup!'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chefspec-4.7.0/lib/chefspec/berkshelf.rb:61:in `block (2 levels) in <top (required)>'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/rspec-core-3.5.2/lib/rspec/core/example.rb:443:in `instance_exec'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/rspec-core-3.5.2/lib/rspec/core/example.rb:443:in `instance_exec'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/rspec-core-3.5.2/lib/rspec/core/hooks.rb:350:in `run'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/rspec-core-3.5.2/lib/rspec/core/configuration.rb:1879:in `block in run_hooks_with'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/rspec-core-3.5.2/lib/rspec/core/configuration.rb:1879:in `each'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/rspec-core-3.5.2/lib/rspec/core/configuration.rb:1879:in `run_hooks_with'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/rspec-core-3.5.2/lib/rspec/core/configuration.rb:1835:in `with_suite_hooks'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/rspec-core-3.5.2/lib/rspec/core/runner.rb:112:in `block in run_specs'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/rspec-core-3.5.2/lib/rspec/core/reporter.rb:77:in `report'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/rspec-core-3.5.2/lib/rspec/core/runner.rb:111:in `run_specs'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/rspec-core-3.5.2/lib/rspec/core/runner.rb:87:in `run'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/rspec-core-3.5.2/lib/rspec/core/runner.rb:71:in `run'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/rspec-core-3.5.2/lib/rspec/core/runner.rb:45:in `invoke'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/rspec-core-3.5.2/exe/rspec:4:in `<top (required)>'
    from /opt/chefdk/embedded/bin/rspec:22:in `load'
    from /opt/chefdk/embedded/bin/rspec:22:in `<main>'

..
---------------------------------------------
Verification of component 'test-kitchen' succeeded.
Verification of component 'rubocop' succeeded.
Verification of component 'knife-spork' succeeded.
Verification of component 'openssl' succeeded.
Verification of component 'delivery-cli' succeeded.
Verification of component 'opscode-pushy-client' succeeded.
Verification of component 'berkshelf' succeeded.
Verification of component 'chef-client' succeeded.
Verification of component 'chefspec' succeeded.
Verification of component 'fauxhai' succeeded.
Verification of component 'inspec' succeeded.
Verification of component 'chef-sugar' succeeded.
Verification of component 'tk-policyfile-provisioner' succeeded.
Verification of component 'chef-provisioning' succeeded.
Verification of component 'kitchen-vagrant' succeeded.
Verification of component 'git' succeeded.
Verification of component 'chef-dk' succeeded.
Verification of component 'generated-cookbooks-pass-chefspec' failed.
Verification of component 'package installation' succeeded.

If I completely uninstall ChefDK 0.17.17 and install 0.16.28 chef verify succeeds without any errors.
Additional Info
Ignoring that chef verify fails and attempting to run kitchen verify produces a similar error with a different stack trace.
-----> Starting Kitchen (v1.11.1)
-----> Creating <tasks-windows-2012R2>...
       Bringing machine 'default' up with 'virtualbox' provider...
       ==> default: Importing base box 'mwrock/Windows2012R2'...
==> default: Matching MAC address for NAT networking...
       ==> default: Checking if box 'mwrock/Windows2012R2' is up to date...
       ==> default: A newer version of the box 'mwrock/Windows2012R2' is available! You currently
       ==> default: have version '0.5.2'. The latest is version '0.5.3'. Run
       ==> default: `vagrant box update` to update.
       ==> default: Setting the name of the VM: kitchen-visualstudio-tasks-windows-2012R2_default_1472059571686_79292
       ==> default: Clearing any previously set forwarded ports...
       ==> default: Clearing any previously set network interfaces...
       ==> default: Preparing network interfaces based on configuration...
           default: Adapter 1: nat
       ==> default: Forwarding ports...
           default: 5985 (guest) => 55985 (host) (adapter 1)
           default: 5986 (guest) => 55986 (host) (adapter 1)
       ==> default: Running 'pre-boot' VM customizations...
       ==> default: Booting VM...
       ==> default: Waiting for machine to boot. This may take a few minutes...
           default: WinRM address: <IP_ADDRESS>:55985
           default: WinRM username: vagrant
           default: WinRM execution_time_limit: PT2H
           default: WinRM transport: plaintext
       ==> default: Machine booted and ready!
       ==> default: Checking for guest additions in VM...
       ==> default: Machine not provisioned because `--no-provision` is specified.
/opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/command.rb:177:in `join': No live threads left. Deadlock? (fatal)
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/command.rb:177:in `map'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/command.rb:177:in `run_action'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/command/action.rb:39:in `block in call'
    from /opt/chefdk/embedded/lib/ruby/2.1.0/benchmark.rb:279:in `measure'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/command/action.rb:37:in `call'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/cli.rb:56:in `perform'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/cli.rb:185:in `block (2 levels) in <class:CLI>'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/cli.rb:326:in `invoke_task'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/bin/kitchen:13:in `block in <top (required)>'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/errors.rb:174:in `with_friendly_errors'
    from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/bin/kitchen:13:in `<top (required)>'
    from /opt/chefdk/bin/kitchen:18:in `load'
    from /opt/chefdk/bin/kitchen:18:in `<main>'

kitchen verify on ChefDK v0.16.28 works fine.

Hmm. On a completely fresh install with nuked user gems its odd that berkshelf is coming from /Users/sneal/.chefdk/gem/ruby/2.1.0/gems/berkshelf-4.3.5. One additional step to take to truly use chef-dk as your dedicated ruby is call chef shell-init: eval "$(/opt/chefdk/bin/chef shell-init bash)" to setup your shell environment correctly.

I'm having a similar error running 'kitchen converge'
-----> Starting Kitchen (v1.11.1) -----> Converging <default-ubuntu-1604>...        Preparing files for transfer        Preparing dna.json        Resolving cookbook dependencies with Berkshelf 4.3.5... /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/command.rb:177:in `join': No live threads left. Deadlock? (fatal)         from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/command.rb:177:in `map'         from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/command.rb:177:in `run_action'         from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/command/action.rb:39:in `block in call'         from /opt/chefdk/embedded/lib/ruby/2.1.0/benchmark.rb:279:in `measure'         from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/command/action.rb:37:in `call'         from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/cli.rb:56:in `perform'         from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/cli.rb:185:in `block (2 levels) in <class:CLI>'         from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'         from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'         from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/cli.rb:326:in `invoke_task'         from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'         from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'         from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/bin/kitchen:13:in `block in <top (required)>'         from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/errors.rb:174:in `with_friendly_errors'         from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/bin/kitchen:13:in `<top (required)>'         from /opt/chefdk/bin/kitchen:18:in `load'         from /opt/chefdk/bin/kitchen:18:in `<main>'

I was having the same issue running rspec tests on a cookbook.  Installing ChefDK v0.16.28 worked for me.

I'm seeing the same thing on a fresh install.

-----> Starting Kitchen (v1.11.1)
-----> Converging <default-centos-68>...
       Preparing files for transfer
       Preparing dna.json
       Resolving cookbook dependencies with Berkshelf 4.3.5...
/opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/command.rb:177:in `join': No live threads left. Deadlock? (fatal)
	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/command.rb:177:in `map'
	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/command.rb:177:in `run_action'
	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/command/action.rb:39:in `block in call'
	from /opt/chefdk/embedded/lib/ruby/2.1.0/benchmark.rb:279:in `measure'
	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/command/action.rb:37:in `call'
	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/cli.rb:56:in `perform'
	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/cli.rb:185:in `block (2 levels) in <class:CLI>'
	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/cli.rb:326:in `invoke_task'
	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/bin/kitchen:13:in `block in <top (required)>'
	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/lib/kitchen/errors.rb:174:in `with_friendly_errors'
	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.11.1/bin/kitchen:13:in `<top (required)>'
	from /opt/chefdk/bin/kitchen:18:in `load'
	from /opt/chefdk/bin/kitchen:18:in `<main>'

Issue seems to have resolved itself with the newest chefdk
Chef Development Kit Version: 0.18.26
chef-client version: 12.14.89
delivery version: master (d86679335580be3de22996ef294b20d525889d8d)
berks version: 5.1.0
kitchen version: 1.13.0

Upgraded chefdk from 0.19.6 to 1.1.16 today and now getting this same error trying to kitchen converge. Blowing away /path/to/cookbook/.kitchen/* and ~/.chefdk/gem hasn't made any difference.
This might(?) be something with more to do with berkshelf, because I can get a nearly identical error when I try to berks vendor:
$ berks vendor
Resolving cookbook dependencies...
Fetching 'vault-wrapper' from source at .
Fetching cookbook index from https://supermarket.chef.io...
/opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/berkshelf-5.2.0/lib/berkshelf/installer.rb:27:in `join': No live threads left. Deadlock? (fatal)
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/berkshelf-5.2.0/lib/berkshelf/installer.rb:27:in `map'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/berkshelf-5.2.0/lib/berkshelf/installer.rb:27:in `build_universe'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/berkshelf-5.2.0/lib/berkshelf/installer.rb:161:in `install_from_universe'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/berkshelf-5.2.0/lib/berkshelf/installer.rb:39:in `run'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/berkshelf-5.2.0/lib/berkshelf/berksfile.rb:422:in `install'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/berkshelf-5.2.0/lib/berkshelf/berksfile.rb:631:in `block in vendor'
	from /opt/chefdk/embedded/lib/ruby/2.3.0/tmpdir.rb:89:in `mktmpdir'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/berkshelf-5.2.0/lib/berkshelf/berksfile.rb:629:in `vendor'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/berkshelf-5.2.0/lib/berkshelf/cli.rb:399:in `vendor'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/thor-0.19.4/lib/thor/command.rb:27:in `run'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/thor-0.19.4/lib/thor/invocation.rb:126:in `invoke_command'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/thor-0.19.4/lib/thor.rb:369:in `dispatch'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/berkshelf-5.2.0/lib/berkshelf/cli.rb:52:in `dispatch'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/thor-0.19.4/lib/thor/base.rb:444:in `start'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/berkshelf-5.2.0/lib/berkshelf/cli.rb:27:in `execute!'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/berkshelf-5.2.0/bin/berks:5:in `<top (required)>'
	from /opt/chefdk/embedded/bin/berks:22:in `load'
	from /opt/chefdk/embedded/bin/berks:22:in `<main>'

This looks like a dup of berkshelf/berkshelf#1619 and it would be better to post new information over there to keep it all in one place for tracking.


[google_maps_flutter] Add support to select preferred renderer

Use case
Maps SDK for Android has ability to use New Map Renderer.

This renderer brings many improvements, including support for Cloud-based maps styling. You can opt-in to try the new renderer before it becomes the default renderer for Android devices, through a progressive rollout starting in June 2022 at the earliest.
The new renderer provides the following benefits:
Cloud-based maps styling features are available with the new renderer.
Advanced Polyline Customizations are available with the new renderer.
Reduced network load, processing demand, and memory consumption.
Improved gesture handling for better animations, plus smoother panning and zooming.
More fluid transitions and clearly positioned map labels.
A more stable and improved user experience.

Proposal
Add support to prefer either latest or legacy renderer for the flutter projects using google_maps_flutter plugin.

This feature is needed to support Cloud-based maps styling: flutter/flutter#67631


cargo-install unnecessarily rebuilds everything

Starting with rust 1.27, if I run cargo build --release then cargo install, the latter syncs its crates.io local copy and rebuilds everything.
This didn't happen with rust 1.26.
Might be related to the latest failure in https://github.com/rust-lang/rust/pull/51717#issuecomment-401370538 ?

I think this change was intentional, see #5327.  You should have gotten a warning:
warning: To build the current package use `cargo build`,
to install the current package run `cargo install --path .`

@ehuss I fail to see how that could be related.
I'm a distribution packager and our install phase doesn't have access to the network so resyncing crates.io breaks stuff, and rebuilding everything that was built just before during the compile phase doesn't seem necessary...

Actually, this is probably a duplicate of #5662

Ah, sorry, I misunderstood.  Indeed using cargo install in a workspace does not seem to be working as intended.

Indeed I believe this is a duplicate! Closing in favor of https://github.com/rust-lang/cargo/issues/5662


Datetime with no tzinfo will be considered UTC is spamming the logs

Describe the bug
when running
az storage blob delete-batch --source SOURCE_NAME --if-unmodified-since 2023-07-18T08:20Z -account-name ACCOUNT_NAME --account-key XXX

in the docker image 2.38.0+ the logs are spammed with Datetime with no tzinfo will be considered UTC for each blob
This is due to the python upgrade in #22864 and not happening in the docker image 2.37.0
Related command
az storage blob delete-batch
Errors
Datetime with no tzinfo will be considered UTC.
Datetime with no tzinfo will be considered UTC.
Datetime with no tzinfo will be considered UTC.
Datetime with no tzinfo will be considered UTC.
Datetime with no tzinfo will be considered UTC.
Datetime with no tzinfo will be considered UTC.
Datetime with no tzinfo will be considered UTC.
Datetime with no tzinfo will be considered UTC.
Datetime with no tzinfo will be considered UTC.
Datetime with no tzinfo will be considered UTC.
...

Issue script & Debug output
debug logs
docker run -ti --rm mcr.microsoft.com/azure-cli:2.38.0 az storage blob delete-batch --source SOURCE_NAME --if-unmodified-since 2023-07-18T08:20Z -account-name ACCOUNT_NAME --account-key XXX

...
urllib3.connectionpool: https://REDACTED.blob.core.windows.net:443 "DELETE /REDACTED/x.tar.gz HTTP/1.1" 412 252
cli.azure.cli.command_modules.storage.operations.blob: The condition specified using HTTP conditional header(s) is not met.
RequestId:REDACTED
Time:2023-08-01T08:47:26.4905364Z
ErrorCode:ConditionNotMet, HttpResponseError: Operation returned an invalid status 'The condition specified using HTTP conditional header(s) is not met.'
Content: <?xml version="1.0" encoding="utf-8"?><Error>ConditionNotMet<Message>The condition specified using HTTP conditional header(s) is not met.
RequestId:REDACTED
Time:2023-08-01T08:47:26.4905364Z</Message></Error>
msrest.serialization: Datetime with no tzinfo will be considered UTC.
urllib3.connectionpool: https://REDACTED.blob.core.windows.net:443 "DELETE /REDACTED/y.tar.gz HTTP/1.1" 412 252
cli.azure.cli.command_modules.storage.operations.blob: The condition specified using HTTP conditional header(s) is not met.
RequestId:REDACTED
Time:2023-08-01T08:47:26.6304558Z
ErrorCode:ConditionNotMet, HttpResponseError: Operation returned an invalid status 'The condition specified using HTTP conditional header(s) is not met.'
Content: <?xml version="1.0" encoding="utf-8"?><Error>ConditionNotMet<Message>The condition specified using HTTP conditional header(s) is not met.
RequestId:REDACTED
Time:2023-08-01T08:47:26.6304558Z</Message></Error>
msrest.serialization: Datetime with no tzinfo will be considered UTC.

Expected behavior
Datetime with no tzinfo will be considered UTC message should not be spamming the logs
Environment Summary
❯ docker run -ti --rm mcr.microsoft.com/azure-cli:2.38.0 az --version
azure-cli                         2.38.0 *

core                              2.38.0 *
telemetry                          1.0.6 *

Dependencies:
msal                            1.18.0b1
azure-mgmt-resource             21.1.0b1

Python location '/usr/local/bin/python'
Extensions directory '/root/.azure/cliextensions'

Python (Linux) 3.10.5 (main, Jun  7 2022, 19:23:05) [GCC 11.2.1 20220219]

and
❯ docker run -ti --rm mcr.microsoft.com/azure-cli:2.51.0 az --version
azure-cli                         2.51.0

core                              2.51.0
telemetry                          1.1.0

Dependencies:
msal                            1.24.0b1
azure-mgmt-resource             23.1.0b2

Python location '/usr/local/bin/python'
Extensions directory '/root/.azure/cliextensions'

Python (Linux) 3.10.12 (main, Jun 15 2023, 03:17:49) [GCC 12.2.1 20220924]

Legal docs and information: aka.ms/AzureCliLegal

Your CLI is up-to-date.

Additional context
No response

Thank you for opening this issue, we will look into it.

looks nice

Wanted to bump this issue - I am also seeing this when using the Azure DevOps Python API. The dates in the objects (like the creation_date field in an ADO Pull Request object) are formatted as a string in UTC. When I call this object's as_dict() function to convert it to a dictionary, the serialization seems to trigger this issue and the warning message is displayed.
Would it be possible to have these datetime values formatted as epoch seconds rather than a UTC string? I believe this would make parsing and conversion much easier while still maintaining the original timestamp. I can understand if that might break existing implementations that rely on the API; perhaps the simplest solution is to enforce the UTC timezone under the hood.


Fixed documentation warnings in  ObjC layer which cause XCode build to fail

Fixed documentation warnings in  ObjC layer which cause XCode build to fail when "Documentation Comments" build setting is "YES" for a build target.

Is this complete set? Are there any other issues that trigger documentation warnings? is there anything in the private modules that needs the same clean-up? If so, you need to clean it up in the modules, then push a zero-change commit id PR to upgrade the submodule to refer to latest.

Is this complete set? Are there any other issues that trigger documentation warnings? is there anything in the private modules that needs the same clean-up? If so, you need to clean it up in the modules, then push a zero-change commit id PR to upgrade the submodule to refer to latest.

@maxgolov , I did not find any other [-WDocumentattion] at any other place while building the code. So, this PR should address current set of documentation warnings.

@maxgolov , I did not find any other [-WDocumentattion] at any other place while building the code. So, this PR should address current set of documentation warnings.


Further development

Hello. I really think it's really neat how you got a system up and working quickly. Do you have plans to refine and improve the system? For example, I could suggest:
-- Adding pressure and airflow sensors. Purchase a few and evaluate performance.
-- Creating a 3d-printed turbine design with a quadcopter brushless motor.
-- Consider redundancy to improve reliabilty. Adding redundant turbines, power supplies etc.
-- Adding pressure relief valves to limit the maximum/minimum pressure in the pipe (to prevent lung damage in the event of firmware error).
-- Creating a custom motor control board based on STSPIN32F0 reference design, or perhaps something like: http://www.electronoobs.com/eng_arduino_tut91.php (there are many designs online). This could be more predictable that an hobby esc, that might have some odd modes (overheat shutdown or something), and could do better self-test routines (monitoring motor current etc.)
-- Creating a standard protocol for the motor control board, main control board, (perhaps sensors), and PC-based diagnostics software to communicate, over UART or perhaps something like CAN. These packets could perhaps optionally be relayed over a network to a central location, using an esp32 with wired or wireless connection. I am thinking something like mavproxy/wiimote protocol/AT commands.
-- Creating diagnostics software with Qt that show pretty graphs of pressure, airflow, motor current and rpm etc., useful for developping control algorithms and perhaps showing useful info for the doctor.
-- Develop improved methods to verify pressure and airflow.
Any of these could be investigated and developped by small teams of 2-3 people.

Please take a look at this document, it's a redacted version of yesterdays Slack discussion: https://docs.google.com/document/d/1KpPWYRb1A637Cp5KIhhKtuGFS8Cdm5fGra3TTwwrBKo/edit#


Add autoutils package

Add autoutils CMake modules package to ease the process of porting autotools builds to CMake.

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.3143
https://travis-ci.org/ingenue/hunter/builds/321435785?utm_source=github_status&utm_medium=notification

Uploading:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.3144
https://travis-ci.org/ingenue/hunter/builds/321442817?utm_source=github_status&utm_medium=notification

Released: https://github.com/ruslo/hunter/releases/tag/v0.19.211


fix: non-existing Namespace displays details/list

Description
Changes proposed in this pull request:

add TS to NamespaceRoutes & NotificationContext
move useHiddenNamespaces to shared hooks
add handler to check whether Namespace you want to interact exists, if not IncorrectPath component is displayed
adjust extensionsAtom to the above handler
set extensibility isEnabled to false <- I guess it should be false, for some reason it's true

Related issue(s)
Closes #2198

/retest

/retest

/retest

/retest


Bump to 0.2.5

PyPI pushed already

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Lgtm


Modifications

Added new example to demo shared consumers for both next and 2.7.0 docs

Verifying this change
site2/website && yarn start renders correctly for both master and 2.7.0 versioned sites in the page Using Pulsar as a message queue, urls:

http://localhost:3000/docs/en/next/cookbooks-message-queue
http://localhost:3000/docs/en/cookbooks-message-queue

@bithavoc thanks for your contribution. I've left some comments, PTAL.

@Anonymitaet ⭐  Comments should be resolved now, please review again.


Support inbound http/1.0 requests

Hi, thanks for a great tool. We're using contour in production and love the flexibility it provides.
We're noticed that contour 0.5 (and envoy 1.6.0) doesn't support inbound http/1.0 requests:
$ curl -v -0 http://example.com/health
> GET /health HTTP/1.0
> Host: example.com
> User-Agent: curl/7.60.0
> Accept: */*
>
< HTTP/1.1 426 Upgrade Required
< date: Tue, 10 Jul 2018 12:44:58 GMT
< server: envoy
< content-length: 0

$ curl -v http://example.com/health
> GET /health HTTP/1.1
> Host: example.com
> User-Agent: curl/7.60.0
> Accept: */*
>
< HTTP/1.1 200 OK
< content-type: application/json
< x-content-type-options: nosniff
< content-length: 15
< x-envoy-upstream-service-time: 2
< date: Tue, 10 Jul 2018 12:49:05 GMT
< server: envoy
<
{"status":"ok"}

This isn't a deal breaker for us, but we're building an API product and expect at least some of our clients may attempt a http/1.0 request and it'd be nice to send them a 301 to a TLS URL.
I notice that envoy 1.6.0 added support for http/1.0 requests (https://github.com/envoyproxy/envoy/issues/170) but I haven't been able to find a way to enable it via contour. Am I missing a config option?

Thank you for raising this issue. TBH I'll have to refresh myself on the nuances of HTTP/1.0 requests and how they differ from HTTP/1.1. This looks like a pretty simple feature to add, and I think if its possible, we'll just turn it on for everyone.
One wrinkle that might come up, and i'm sketchy on the details because its' been so long, is the handling of the Host: header in http/1.0, something which might interact weirdly with Ingress's notion of the default vhost or ingress.

Thanks. As I say, it's not a deal breaker for us - I just wanted to capture the issue as a "nice to have".
Maybe it'll even save others a bit of research time if they wonder why ab tests don't work on a contour service (like I did.....)

Just need to tweak the envy config:
see https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/core/protocol.proto#core-http1protocoloptions

One way is off a cluster, set the http_protocol_options or did I miss something?

I’m honestly not sure, the original issue was envoy returning a 426 when it got a http/1.0 request. I haven’t dug into it at all, but it feels to me that this processing would happen before the request got to the point of choosing a cluster.

On 14 Jul 2018, at 12:46, Michael Fraenkel<EMAIL_ADDRESS>wrote:
One way is off a cluster, set the http_protocol_options or did I miss something?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

The other way is off the connection_manager which is a network filter, but I haven't figured out where that comes into play.

That’s where I’m thinking the change probably needs to sit.

On 14 Jul 2018, at 13:05, Michael Fraenkel<EMAIL_ADDRESS>wrote:
The other way is off the connection_manager which is a network filter, but I haven't figured out where that comes into play.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

You have the http_connection_manager already in the current config, now you just need to know when/what to set the http1 protocol config.

We should get this in, but it's not essential for 0.6.0 which is focused on wrapping up remaining IngressRoute CRD work.


[release-1.18] Manual update-common and update client/h2-timer# commits to latest

Replaces https://github.com/istio/ztunnel/pull/532 with an additional change for removed commit in github.com/howardjohn/hyper-util?branch=client/h2-timer. Moved to last commit on that branch.

Checking if cargo update -p hyper-util makes a different change.


feat: add zilliz component

Because

We want to integrate VDP with zilliz vector db
We want more vector db component choice

This commit

Add milvus component along with the basic tasks (vector search, upsert, ..)
Use api key authentication

Hi, though post or delete can be 200 for status code, I still hope you can re-confirm it!

Based on zilliz docs, every success request will have 0 status code, otherwise it will be considered fail. Same goes for milvus, difference is milvus use 200 status code instead


My Maps should zoom to show the most recent route

It currently zooms to show the last 10 saved spots only. Would be cool to show the most recent route from its begining.

[ ] When loading the map for the first time, zoom out to show last route only
[ ] When clicking 'View all spots' then we should zoom out to show all spots (currently it zooms out to shows only the last route)


Deploying the /src folder to a dev sandbox

I am trying to deploy the /src folder to a brand new sandbox and keep getting these errors.

Any thoughts on what I am dong wrong ?
Jay

Hi @jayonsoftware. We appreciate your interest in HEDA. However, in the future please post first at The Power of Us Hub (powerofus.force.com - it's free!) before opening a Github ticket.
We'd highly recommend installing the manage version of the package, which  you can obtain from mrbelvedere.salesforcefoundation.org/mpinstaller/hed. Among other things, that will guarantee automatic updates to the latest version. Also, the installer will take care of all requirements. One of the requirements is having at least one Account record type in the org. This is the requirement that is missing for you. If you are certain you want to install the unmanaged code, first create an Account record type in the org.
Thanks!


Provide a repository template

Description
As an ai model author, I want to spin up a new project with caikit, so that I can wrap my models in caikit interfaces to load in my applications
Discussion
@gkumbhat has some experience setting up slick repo templates.
We can probably get one going that does any boilerplatey stuff, though we should try to remove as much as possible.
Should we include docker image support to build an image that boots the runtime?
Acceptance Criteria

[ ] A template repo exists that users can quickly hack on to get a caikit project running

Closing as covered by #70


Remove appearance from date inputs

It seems https://github.com/twbs/bootstrap/issues/11266 is solved in the meantime and this was causing the inputs to shrink (date & time inputs):

@MartijnCuppens which iOS versions did you test?
https://github.com/twbs/bootstrap/blob/d79830c4ee407efdafd754aaf4dd729a33fe3a37/.browserslistrc#L10

Tangent, but saw the comment and figured I'd look up iOS distribution: https://developer.apple.com/support/app-store/. We can probably move to iOS 12+ given the browser share there. v4 covers us on older versions.

@MartijnCuppens Could you create before and after test cases?

Before
ios13:

ios12:

ios11:

ios9:

After
ios13:

ios12:

ios11:

ios9:

I can't reproduce the initial issue from back in 2013.

Shouldn't this be also backported?

Yes, made a separate PR since reboot changed a lot in v5

@MartijnCuppens Do you intend that this affect input style with .form-control class?
Before: https://codepen.io/fellows3/pen/BaNmvvN

After: https://codepen.io/fellows3/pen/RwPjEeO

In that case we should only change the appearance for .form-controls. I now pushed some changes and set the height of the ::-webkit-date-and-time-value pseudo selector to prevent it from collapsing.


Push 0.2.3 to Github

It looks like you published version 0.2.3 on 9-Feb-2019, but forgot to push the changes to GitHub.  Could you please?

ping.  Could you please push your latest changes to GitHub?

This has been done. The only actual change was updating the version in Cargo.toml to 0.2.3. The source code in 0.2.3 is the same as the current master branch of this Git repo.
Apologies for the long delay.


Documentation and examples for notifications

Is there any documentation or examples for using the Shoutrrr URL? Perhaps what variables to use, syntax, etc?
I used a webhook , which worked as a curl, but when I put it in as generic+, it failed.

There is a link to Shoutrrr documentation on Config page of WYL: https://containrrr.dev/shoutrrr/v0.8/

I followed the documentation and received the following error.
2024/09/17 13:46:44 ERROR Notification failed (shoutrrr):  ""="an error occurred while sending notification to generic webhook: server returned response status code 400 Bad Request"
my
generic+https://api.pushover.net/1/messages.json?token=<REDACTED>&user=<REDACTED>title=Unknown+host+detected&message=test+message
I don't use shoutrrr, so I used the "generic" nomenclature.
The command works perfectly fine if I curl it.
It would be great to have some examples and list the variables/info we can include in our message.

It would be great to have some examples and list the variables/info we can include in our message.
Here is an example for pushover:
https://containrrr.dev/shoutrrr/v0.8/services/pushover/

So this is to my point. The documentation says:

Link to any notification service supported by Shoutrrr (gotify, email, telegram and others) or Generic Webhook

The link goes to Shoutrrr
and says to use generic+
I'm not using Shoutrrr. So an example would be helpful for how to put in a generic webhook.

Shoutrrr is already inside WatchYourLAN as a module. You don't need to install it, just use the example in Shoutrrr doc.

Oh, definitely didn't realize that.
Are there variables we can reference for the message?

Are there variables we can reference for the message?

Not yet.


[FEATURE] Configuring ReRankingContentAggregator to Return Top Results

Does ReRankingContentAggregator support parameter configuration to return the maximum number of results with the highest scores? For example:
ContentAggregator contentAggregator = ReRankingContentAggregator.builder()
.scoringModel(scoringModel)
.minScore(reranking_min_score)
.maxResults(5)
.build();
Because ContentRetriever has already set maxResults in EmbeddingStoreContentRetriever, for example, if I want to recall 5 pieces of data, EmbeddingStoreContentRetriever also returns 5 results. If ReRankingContentAggregator filters the results based on minScore and only returns 3 results, the final output will have only 3 results, which does not match my expected result.
To address this, I want to increase the number of results recalled by EmbeddingStoreContentRetriever so that ReRankingContentAggregator can determine the final number of results. For example, I might set maxResults in EmbeddingStoreContentRetriever to a higher value, such as 10, to ensure that ReRankingContentAggregator has enough candidates to select from and can still return the desired number of top results.
// Example configuration for EmbeddingStoreContentRetriever
ContentRetriever contentRetriever = EmbeddingStoreContentRetriever.builder()
.maxResults(10)  // Increase the number of results to recall
.build();
// Example configuration for ReRankingContentAggregator
ContentAggregator contentAggregator = ReRankingContentAggregator.builder()
.contentRetriever(contentRetriever)
.scoringModel(scoringModel)
.minScore(reranking_min_score)
.maxResults(5)  // Desired number of final results
.build();

Hi @fmx0717, this is not supported yet, but should be very easy to implement. Would you like to open a PR please?


Matrix in Linear Reconstruction dynamic array replace by static array

Bug, Use of dynamic array inside Kokkos kernel fixed

merged and deleted branch


Many tests fail with: tried to access a dead local variable

Looks like something changed in rustc, and it now emits StorageDead/StorageLive differently.

I think it's purely related to the box keyword. The only related PR I've found is https://github.com/rust-lang/rust/pull/43772

Should be fixed by next nightly, as https://github.com/rust-lang/rust/pull/43859 fixes the issue.

Fixed upstream.


TestCafe not loading page in 2.2.0/2.3.0 version.

What is your Scenario?
Upgrade TestCafe to 2.2.0 or 2.3.0 and run test script with "yarn" or "npm run".
What is the Current behavior?
TestCafe session page is loaded but no further actions are taken

What is the Expected behavior?
Test should be finished
TestCafe in version 2.1.0 works ok.
What is your public website URL? (or attach your complete example)
https://testcafe.io/documentation/402635/getting-started
What is your TestCafe test code?
import { Selector } from "testcafe";
fixture`Simple test 1`
    .page('https://testcafe.io/documentation/402635/getting-started')

test('Simple test 1', async t => {
    await t.expect(Selector('#header').exists).ok();
    const value = await Selector('#what-is-testcafe__\\$').innerText;
    await t.expect(value).eql('What Is TestCafe?');

Steps to Reproduce

Run test script with yarn or npm run from directory with package.json file

TestCafe version
2.2.0/2.3.0
Node.js version
19.5.0
Command-line arguments
Package.sjon scirpt:
"simple": "testcafe chrome tests/simple.ts",
yarn simple
npm run simple
Browser name(s) and version(s)
Chrome 109
Platform(s) and version(s)
Windows 10.0.19044
Other
What is weird test script is executing from VS code terminal. VS code launch.json settings:
       {
            "type": "node",
            "request": "launch",
            "name": "Chrome: REGULAR",
            "program": "${workspaceFolder}/main/test/e2e/node_modules/testcafe/bin/testcafe.js",
            "args": [
                "chrome",
                "${file}"
            ],
            "console": "integratedTerminal",
            "cwd": "${workspaceFolder}",
            "smartStep": true,
            "skipFiles": [
                "${workspaceFolder}/main//test/e2e/node_modules/**/*.js",
                "${workspaceFolder}/main//test/e2e/node_modules/**/**/*.js",
                "${workspaceFolder}/main/test/e2e/node_modules/**/**/**/*.js",
                "${workspaceFolder}/main/test/e2e/node_modules/**/**/**/**/*.js",
               ],
            "sourceMaps": true
        }

I updated issue with new data. I hope it will help :)

I cannot reproduce the issue. I followed these steps:

Created these files in a new repo:

//package.json
{
  "name": "tests",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "scripts": {
    "simple": "testcafe chrome tests/simple.ts"
  },
  "dependencies": {
    "testcafe": "2.3.0"
  }
}

// tests/simple.ts

import { Selector } from "testcafe";

fixture`Simple test 1`
    .page('https://testcafe.io/documentation/402635/getting-started')

test('Simple test 1', async t => {
    await t.expect(Selector('#header').exists).ok();
    const value = await Selector('#what-is-testcafe__\\$').innerText;
    await t.expect(value).eql('What Is TestCafe?');
});

Installed the yarn:

yarn install

Run the commands:

node -v && testcafe -v && yarn simple

This is my console output:

Please check these steps and clarify what I miss.

What is weird test script is executing from VS code terminal. VS code launch.json settings:

As I see in your screenshots, you run the script in the Bash terminal. What does this have to do with VS code terminal?

I pointed out vscode terminal, because I can run my test with TestCafe 2.2.0/2.30 with vscode integrated terminal but not with yarn or npm run from bash.

The only difference I see is I do not have testcafe installed globally, only locally form package.json.

And it is working with testcafe 2.1.0

I tried it on both, GitBash and PowerShell, result is the same, page is loaded and no further actions are taken.

Did you create a new project as described? If so, please run the test like this:
export DEBUG="testcafe:*,hammerhead:*" && testcafe chrome tests/simple.ts 2> testcafe.log

And share the created testcafe.log here.


receive: add button for sharing QR-code of a wallet

This needs to link to the original issue that is being closed.

This needs to link to the original issue that is being closed.
This PR resolving issue - #178


Fix the Common Space type on listings list

What's to be fixed:

This was working fine and now it's not.
Questions:

When is this going to stop? When are we going to stop bringing bugs that were never there in the first place? Or bugs that had already been fixed and now they are back?

When are we going to have a process that guarantees that these things don't happen again? Why is staging not the cleanest of all versions, the most updated and the exact clone of master so when pushing to master we don't push crap to it?!

This does not help guys! Does not help with the first impression from users! Does not help with the first impression from the companies we are contacting! Does not help at all because users move away almost immediately from buggy products.
I'm not asking for everything to be perfect. I'm only asking for it to be clean and for these stresses to be removed from our work because they happen way too often!
What's the expected behaviour:
The message in those blue boxes must say "Common Space"
What happens in reality (screenshot):

Priority (tag accordingly): Urgent
Domain (tag accordingly): Frontend
Tested on: (platform, OS, browser, version) Windows, latest, Chrome, latest
Branch: hotfix-space-type-listing-list
Work on it

Derive the branch from master. Prefix it with hotfix-.
Tag with ongoing and move the card to ongoing.
Fix the issue
Commit your work
Create a PR and ask for validation. Move the card to staged.
Ask for validation.
Close the issue

** Validate **

Check on mobile and on desktop if the issue have been correctly fixed.
If everything is correct, move the card to accepted column.
If the issue isn't fixed, re-open the comment clearly what the problem is and what is the desired result. Move the card to have issues column.

Please follow https://github.com/Whichost/frontend/wiki/Git-workflow

I am working on it.
Work on it:

Place the card in ongoing column
Tag it with ongoing

What have been done: Add the missing translation
Tag somebody: @RohrerHope
Pushed on*:  master
Asking for validation:

Check on mobile and on desktop if the issue have been correctly fixed.
If everything is correct, move the card to accepted column.
If the issue isn't fixed, re-open the comment clearly what the problem is and what is the desired result.
Move the card to have issues column.
Merge (or express approval in) the corresponding PR if needed. Move the card to the launch column.


Get cloud deployment working

This now kind of works, so I want to go back to using branches and making the work more atomic.

whoops, meant to open this on my fork


snapshot support and multiple manifest files

First of all thanks for this lovely tool.
Currently we are evaluating alternatives to repo tool and this one here checks almost all the boxes and has readable code (🥳 ), which is a big plus.
Currently we work with a single file manifest, that has floating (just the branch) references to a few of our larger stack of repositories we need to assemble.
Once a change has passed CI we generate a fixed revision monolithic file as a release.
With that in mind #48 would be exactly the missing piece for us to entirely move on from repo.
After reading #235 I'm a bit confused to be honest.
Shall the snapshots be just a local feature?
I mean if the file name of the manifest is static (and I understand the reasoning behind that) do I need to run a second command (like snapshot load <something.yml>) to get to that frozen set again?
Or are those snapshots not meant to be put under version control?
To me the logical consequence (at least for our setup) would be to allow a configurable manifest file name - like manifest.dev.yml and manifest.release.yml.
Unfortunately branching won't do it for us, as, with up to 20 releases a day, we would end up with big pile of branches within a year (something that becomes unmanageable, if you think about that we require each of those releases to be immutable, hence using the branch protection feature of e.g. Github, which needs to be configured).
An alternative, as mentioned, would be to run this second command snapshot load <manifest.release.yml> after the initial init with the "normal" "dev" variant - but I'm not sure how well that goes in real life, considering that in our setup repos come and go, so there might be larger diff between those.
I would be happy if one of the maintainer of this tool could clarify the intent of the snapshot feature.
(btw we are willing to really invest into implementing that)

Hi @kwavnet ,
'snapshot' feature is no longer there. Do not know why, I have to look for it further.
In regarding of your use-case:
1.) you can use 'load-manifest' feature that can load any manifest you have even as some extra manifest in your manifest repository.
2.) if you have 20 release a day, then I see your point. So the feature request as I see it here is to allow for Manifest (for Workspace) to configure not only branch, but tag and SHA1 as well. This seems like a good idea. I had to look at it more.

Also 'apply-manifest' only take care of missing repos and filesystem operations of provided manifest.
It does not switch branch, tag or SHA1 of already existing repos. This may need to be updated as well by extending let us say with '--hard' option in which case even existing repos will get reset/checkout to requested branch, tag or SHA1 from provided Manifest file as well. It is just a thought.

Hi @kwavnet ,
In regards of my 2nd point of allowing Manifest to be set to Tag or SHA1 and not only to branch:
As I am looking into it, such change to be done properly it may took about 3 months for me to implement (and that is optimistic estimate when everything goes smoothly).


Fix typos

instalation => installation

 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.Mary Ann Brennan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@mabmierau this PR is approved, you can go ahead squash/merge.
Note, you'll have to check/approve the license agreement https://cla-assistant.io/newrelic/open-install-library?pullRequest=596


Update AuthorizesRequests.php

Use get_class() to get the full class name where implicit model binding is not utilized.

You must pass in a string, not an object, as the phpdoc says.


attempting to clean up 5xx errors

Description of the change: removing zeroclipboard javascript
Reason for the change: because it is no longer supported and seems to be causing 500 errors
Link to original source: on every page that has a code example

Hello @ksigler7,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


A wrong npm link

Operating system and version:

nvm debug output:
Downloading node.js version 10.10.0 (64-bit)...
Complete

Downloading npm version 6.4.1... Download failed. Rolling Back.
Rollback failed. remove C:\Users\xxx\AppData\Roaming\nvm\temp\npm-v6.4.1.zip: The process cannot access the file because it is being used by another process.
Could not download npm for node v10.10.0.
Please visit https://github.com/npm/npm/releases/tag/v6.4.1 to download npm.
It should be extracted to C:\Users\xxx\AppData\Roaming\nvm\v10.10.0

I guess i use a wrong link in<EMAIL_ADDRESS>Should it be update like following?
https://github.com/npm/cli/archive/v6.4.1.zip

nvm ls output:

How did you install nvm? (e.g. install script in readme, Homebrew):

What steps did you perform?

What happened?

What did you expect to happen?

Is there anything in any of your profile files (.bashrc, .bash_profile, .zshrc, etc) that modifies the PATH?

If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?

nvm doesn’t have a v1, and it only works on windows with BashOnWindows, the linux subsystem. I think you’re using nvm-windows, a different project.


Way to just run terraform validate in different directory

What problem are you facing?
I have a repository that has a terraform module that uses provider configuration aliases (see https://github.com/antonbabenko/pre-commit-terraform#terraform_validate).  Unfortunately, neither of the workarounds suggested are really what I want. If I exclude the root directory, then, if I understand how pre-commit exclude works, then it won't validate the example directory if I only make changes in the root directory.  But generating a provider file creates a stray file, and means that my local pre-commit hook works differently than the my CI job (which just validates the example directory).
How could pre-commit-terraform help solve your problem?
I'd like to have a way to validate in the example directory when there is a change to a file in the root directory.

Please show your

CI job (which just validates the example directory).

Well, you just hardcoded some path inside CI
You can do it in pre-commit too.
Provide something like
- id: terraform_validate
  files: ^examples/example1
  always: true

I finally got to work. Note: you need to use always_run not always


Missing book information in inbook citation

doi:10.1037/0000120-016
The following is its source JSON:
{
  "status": "ok",
  "message-type": "work",
  "message-version": "1.0.0",
  "message": {
    "indexed": {
      "date-parts": [
        [
          2022,
          3,
          29
        ]
      ],
      "date-time": "2022-03-29T21:49:31Z",
      "timestamp":<PHONE_NUMBER>265
    },
    "publisher-location": "Washington",
    "reference-count": 0,
    "publisher": "American Psychological Association",
    "content-domain": {
      "domain": [],
      "crossmark-restriction": false
    },
    "short-container-title": [],
    "published-print": {
      "date-parts": [
        [
          2019
        ]
      ]
    },
    "DOI": "10.1037/0000120-016",
    "type": "book-chapter",
    "created": {
      "date-parts": [
        [
          2018,
          12,
          6
        ]
      ],
      "date-time": "2018-12-06T14:14:50Z",
      "timestamp":<PHONE_NUMBER>000
    },
    "page": "345-359",
    "source": "Crossref",
    "is-referenced-by-count": 6,
    "title": [
      "Culinary arts: Talent and their development."
    ],
    "prefix": "10.1037",
    "author": [
      {
        "given": "Laurent",
        "family": "Aron",
        "sequence": "first",
        "affiliation": []
      },
      {
        "given": "Marion",
        "family": "Botella",
        "sequence": "additional",
        "affiliation": []
      },
      {
        "given": "Todd",
        "family": "Lubart",
        "sequence": "additional",
        "affiliation": []
      }
    ],
    "member": "15",
    "container-title": [
      "Psychology of high performance: Developing human potential into domain-specific talent."
    ],
    "original-title": [],
    "link": [
      {
        "URL": "http://psycnet.apa.org/books/16096/016.pdf",
        "content-type": "unspecified",
        "content-version": "vor",
        "intended-application": "similarity-checking"
      }
    ],
    "deposited": {
      "date-parts": [
        [
          2020,
          12,
          28
        ]
      ],
      "date-time": "2020-12-28T18:52:59Z",
      "timestamp":<PHONE_NUMBER>000
    },
    "score": 1,
    "resource": {
      "primary": {
        "URL": "http://content.apa.org/books/16096-016"
      }
    },
    "subtitle": [],
    "short-title": [],
    "issued": {
      "date-parts": [
        [
          2019
        ]
      ]
    },
    "references-count": 0,
    "alternative-id": [
      "2018-59444-016",
      "2018-59444-000"
    ],
    "URL": "http://dx.doi.org/10.1037/0000120-016",
    "relation": {},
    "published": {
      "date-parts": [
        [
          2019
        ]
      ]
    }
  }
}

The following is the generated Relaton XML:
<bibitem type="inbook" schema-version="v1.2.1" id="B">  <fetched>2022-12-10</fetched>
<title type="main" format="text/plain" language="en" script="Latn">Culinary arts: Talent and their development.</title>
  <uri type="DOI">http://dx.doi.org/10.1037/0000120-016</uri>  <docidentifier type="DOI" primary="true">10.1037/0000120-016</docidentifier>  <date type="created">    <on>2018-12-06</on>  </date>  <date type="issued">    <on>2019</on>  </date>  <date type="published">    <on>2019</on>  </date>  <contributor>    <role type="author"/>    <person>
<name>        <forename language="en" script="Latn">Laurent</forename>        <surname language="en" script="Latn">Aron</surname>      </name>
    </person>  </contributor>  <contributor>    <role type="author"/>    <person>
<name>        <forename language="en" script="Latn">Marion</forename>        <surname language="en" script="Latn">Botella</surname>      </name>
    </person>  </contributor>  <contributor>    <role type="author"/>    <person>
<name>        <forename language="en" script="Latn">Todd</forename>        <surname language="en" script="Latn">Lubart</surname>      </name>
    </person>  </contributor>  <contributor>    <role type="publisher"/>    <organization>
<name>American Psychological Association</name>
    </organization>  </contributor>  <place>    <city>Washington</city>    <region/>  </place></bibitem>

Again, we are missing host item information, and extent:
<bibitem>
<uri>http://psycnet.apa.org/books/16096/016.pdf</uri> # link.URL
....
<relation type="includedIn">
<bibitem type="book"> # inferred from inbook
<title>Psychology of high performance: Developing human potential into domain-specific talent</title> # container-title
<contributor/> # see below
</bibitem>
</relation>
<extent>
  <localityStack>
        <locality type="page"> # page
          <referenceFrom>345</referenceFrom>
          <referenceTo>359</referenceTo>
        </locality>
  </localityStack>
</extent>

We have an additional problem:
inbook, inproceedings, incollection works are expected to have an editor of the host item. (Only rarely does the host item have an author instead of an editor.) DOI, surprisingly, does not supply it: it only supplies the host item title. The actual citation of the chapter in APA style is:

Aron, L., Botella, M., & Lubart, T. (2019). Culinary arts: Talent and their development. In R. F. Subotnik, P. Olszewski-Kubilius, & F. C. Worrell (Eds.), The psychology of high performance: Developing human potential into domain-specific talent (pp. 345–359). American Psychological Association. https://doi.org/10.1037/0000120-016

In order to get the names of Subotnik, Olszewski-Kubilius and Worrell, we actually have to look up the matching book.
To my astonishment, CrossRef does not provide a link from the contained item to its host item. So you are going to have to do a search; and per https://www.crossref.org/documentation/retrieve-metadata/rest-api/tips-for-using-the-crossref-rest-api/ , they just want you to do a search using query.bibliographic . Include in the search: container-title, publisher, publisher-location, year, comma delimited. So:
http://api.crossref.org/works?query.bibliographic="Psychology of high performance: Developing human potential into domain-specific talent, American Psychological Association, Washington, 2019"&rows=2

(Rows 2 tells us if there is any ambiguity, but unfortunately, there will be. We just have to trust in the first result being the right one.)
That query retrieves
{
  "status": "ok",
  "message-type": "work-list",
  "message-version": "1.0.0",
  "message": {
    "facets": {},
    "total-results": 2011118,
    "items": [
      {
        "indexed": {
          "date-parts": [
            [
              2022,
              6,
              24
            ]
          ],
          "date-time": "2022-06-24T10:26:06Z",
          "timestamp":<PHONE_NUMBER>644
        },
        "publisher-location": "Washington",
        "reference-count": 0,
        "publisher": "American Psychological Association",
        "content-domain": {
          "domain": [],
          "crossmark-restriction": false
        },
        "published-print": {
          "date-parts": [
            [
              2019
            ]
          ]
        },
        "DOI": "10.1037/0000120-003",
        "type": "book-chapter",
        "created": {
          "date-parts": [
            [
              2018,
              12,
              6
            ]
          ],
          "date-time": "2018-12-06T14:14:50Z",
          "timestamp":<PHONE_NUMBER>000
        },
        "page": "23-58",
        "source": "Crossref",
        "is-referenced-by-count": 8,
        "title": [
          "High-performance talent development in golf."
        ],
        "prefix": "10.1037",
        "author": [
          {
            "given": "Steven T.",
            "family": "Portenga",
            "sequence": "first",
            "affiliation": []
          }
        ],
        "member": "15",
        "container-title": [
          "Psychology of high performance: Developing human potential into domain-specific talent."
        ],
        "link": [
          {
            "URL": "http://psycnet.apa.org/books/16096/003.pdf",
            "content-type": "unspecified",
            "content-version": "vor",
            "intended-application": "similarity-checking"
          }
        ],
        "deposited": {
          "date-parts": [
            [
              2020,
              12,
              28
            ]
          ],
          "date-time": "2020-12-28T18:52:41Z",
          "timestamp":<PHONE_NUMBER>000
        },
        "score": 65.82207,
        "resource": {
          "primary": {
            "URL": "http://content.apa.org/books/16096-003"
          }
        },
        "issued": {
          "date-parts": [
            [
              2019
            ]
          ]
        },
        "references-count": 0,
        "alternative-id": [
          "2018-59444-003",
          "2018-59444-000"
        ],
        "URL": "http://dx.doi.org/10.1037/0000120-003",
        "published": {
          "date-parts": [
            [
              2019
            ]
          ]
        }
      },
      {
        "indexed": {
          "date-parts": [
            [
              2022,
              10,
              18
            ]
          ],
          "date-time": "2022-10-18T07:56:04Z",
          "timestamp":<PHONE_NUMBER>459
        },
        "publisher-location": "Washington",
        "reference-count": 0,
        "publisher": "American Psychological Association",
        "content-domain": {
          "domain": [],
          "crossmark-restriction": false
        },
        "published-print": {
          "date-parts": [
            [
              2019
            ]
          ]
        },
        "DOI": "10.1037/0000120-002",
        "type": "book-chapter",
        "created": {
          "date-parts": [
            [
              2018,
              12,
              6
            ]
          ],
          "date-time": "2018-12-06T14:14:50Z",
          "timestamp":<PHONE_NUMBER>000
        },
        "page": "7-20",
        "source": "Crossref",
        "is-referenced-by-count": 8,
        "title": [
          "High performance: The central psychological mechanism for talent development."
        ],
        "prefix": "10.1037",
        "member": "15",
        "container-title": [
          "Psychology of high performance: Developing human potential into domain-specific talent."
        ],
        "link": [
          {
            "URL": "http://psycnet.apa.org/books/16096/002.pdf",
            "content-type": "unspecified",
            "content-version": "vor",
            "intended-application": "similarity-checking"
          }
        ],
        "deposited": {
          "date-parts": [
            [
              2020,
              12,
              28
            ]
          ],
          "date-time": "2020-12-28T18:52:41Z",
          "timestamp":<PHONE_NUMBER>000
        },
        "score": 65.55682,
        "resource": {
          "primary": {
            "URL": "http://content.apa.org/books/16096-002"
          }
        },
        "editor": [
          {
            "given": "Rena F.",
            "family": "Subotnik",
            "sequence": "first",
            "affiliation": []
          },
          {
            "given": "Paula",
            "family": "Olszewski-Kubilius",
            "sequence": "additional",
            "affiliation": []
          },
          {
            "given": "Frank C.",
            "family": "Worrell",
            "sequence": "additional",
            "affiliation": []
          }
        ],
        "issued": {
          "date-parts": [
            [
              2019
            ]
          ]
        },
        "references-count": 0,
        "alternative-id": [
          "2018-59444-002",
          "2018-59444-000"
        ],
        "URL": "http://dx.doi.org/10.1037/0000120-002",
        "published": {
          "date-parts": [
            [
              2019
            ]
          ]
        }
      }
    ],
    "items-per-page": 2,
    "query": {
      "start-index": 0,
      "search-terms": null
    }
  }
}

Which includes the editors we were looking for.
Yes, this is complex. But it is non-negotiable. We cannot exclude editor names from book chapters: a citation of this work which does not name Subotnik, Olszewski-Kubilius, & Worrell is simply incorrect.

(Rows 2 tells us if there is any ambiguity, but unfortunately, there will be. We just have to trust in the first result being the right one.)

@opoudjis do you mean the first result with editors? Why should we take the second row? It has even a different DOI.

Actually, it isn't ambiguous after all: query.bibliographic appears to ignore container-title and is only returning results where the string is a title. Together with the publisher and year, I think we'll be ok almost all of the time.

We need to be a bit careful about terminology here.
The DOI is an ISO standard with data managed by the DOI Foundation as the registration authority. It “does not” handle any bibliographic data. It only maps a DOI identifier to a URL.
There is another organization called CrossRef that is a registration agent of DOI (they pay DOI) which accepts bibliographic data when resolving DOI. Publishers who pay CrossRef are allowed to attach bibliographic data to map to their DOI identifiers when using the CrossRef system.
Technically, this gem is relaton-crossref, not relaton-doi, because it never actually talks to DOI’s systems.

You want the first result where (a) the container-title of the chapter have matches the title of what you find, and (b) the type is not book-chapter but book.
And of course the DOI is different. The chapter and the book including the chapter are different things.
You are by default indeed looking for an item with editors. But even if it has authors not editors, it is a match so long as the container-title of the chapter is the title of the item, the item is not a chapter but a book, and the other common attributes, year publisher publisher-location, all match.
Same goes for proceedings paper (however they call it) and proceedings.
If you haven't already done so, find a DOI item from one of each category we recognise, and include it in testing.

Almost, but not quite:
The editors you have retrieved, Subotnik, Olszewski-Kubilius and Worrell, are currently appended after the chapter authors. But they are the editors of the book, not the chapter. So they need to go inside /relation/bibitem:
  <relation type="includedIn">
    <bibitem>
      <title format="text/plain">Psychology of high performance: Developing human potential into domain-specific talent.</title>
  <contributor>
    <role type="editor"/>
    <person>
      <name>
        <forename language="en" script="Latn">Rena F.</forename>
        <surname language="en" script="Latn">Subotnik</surname>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="editor"/>
    <person>
      <name>
        <forename language="en" script="Latn">Paula</forename>
        <surname language="en" script="Latn">Olszewski-Kubilius</surname>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="editor"/>
    <person>
      <name>
        <forename language="en" script="Latn">Frank C.</forename>
        <surname language="en" script="Latn">Worrell</surname>
      </name>
    </person>
  </contributor>
    </bibitem>
  </relation>

OK, one more thing.
Books can have series. (I will need to find if Crossref models those at all.)
Chapters are included in books.
Articles are included in journals. BUT, INSTEAD, we model articles as being in series. That's a convention we're continuing with.
However, we do NOT model chapters as belonging in series.
So:

You are currently encoding the container-title twice, as series and as relation/bibitem/title. Don't:
chapter: no series, just includedIn
article: no includedIn, just series.
book: POTENTIALLY a distinct series field, if it exists, but I will find that out when I search for examples for you.


Add clair data migration in DB migrator

this commit to fix issue https://github.com/vmware/harbor/issues/5097, add the clair data migration.
[Usage]:
docker run -it -e DB_USR=root -e DB_PWD=${pwd} -v /data/database/:/var/lib/postgresql/data -v /data/clair-db/:/clair-db vmware/harbor-migrator:dev --db up
[Limitation]
For clair migration, there is a necessary precondition that you should not launch harbor before doing it, otherwise the migrator will give a waring message and stop the process.

Coverage increased (+0.006%) to 64.523% when pulling 2379123ff78e1f7aa6e4004a974522c27129b365 on wy65701436:migrate-clair into 01b012afaf6c432b2ddbfa08494b6e5e27f545e8 on vmware:master.


Broken source or what?

I investigated a little and everything works just fine until this commit: ae217413b73757c483cdd3c59751144768444726
I also managed to get a benchmark working with this one. And also you may notice
https://github.com/trueadm/inferno/blob/ae217413b73757c483cdd3c59751144768444726/build/inferno.js#L323-L368
This is all iteration through arrays. Updatefragment doesn't.
However, I got the benchmark running with this modified code:
function template1(fragment) {
  var root = document.createElement("div");
  fragment.dom = root;
  fragment.$e0 = root;
  fragment.valuesLength = 1;
  fragment.$t0 = Inferno.Type.LIST;
}

function template2(fragment) {
  var root = document.createElement("span");
  root.textContent = fragment.$v0;
  fragment.dom = root;
  fragment.$e0 = root;
  fragment.$t0 = Inferno.Type.TEXT;
}

function renderTree(nodes) {
  var children = [];
  var i;
  var e;
  var n;

  for (i = 0; i < nodes.length; i++) {
    n = nodes[i];
    if (n.children !== null) {
      children.push({dom: null, next: null, template: template1, templateKey: 0, key: n.key, $e0: null, $t0: 0, $v0: renderTree(n.children)});
    } else {
      children.push({dom: null, next: null, template: template2, templateKey: 1, key: n.key, $e0: null, $t0: 0, $v0: n.key.toString()});
    }
  }

  return children;
}

In the latest updates starting from 29 days ago. This all breaks, and if you try to run the same code, you will get in console.  NotFoundError: Node was not found
You may notice I didn't put an length in the template2 function. If I do so, we will run into another console error: TypeError: element is null. This happen because it can't find the element when trying to update two text nodes.
If I modify even more, a various console error messages are showing in the console.log.
However. This commit 3fa8c82f4116985aeb84cafdaae40553d2a03168 contains almost identical code, except that the updateFragment now also iterate through arrays. And here it seems to break!
For update from august 24, when I changed the variable names, I ran into this console.log error with the same code:
TypeError: Argument 1 of Node.appendChild is not an object.
And when I tried with the newest update the same, or I got messages telling me that the Node was not found and a whole lot of others.
Even if the newer updates have different names, but should have worked. But doesn't simply because all the newest updates include the same strange behaviour as mentioned.
I was investigating this because I was looking deeper into creating a createElement() function and PR. But figured out I will let you add that feature. I think it should be simple enough to add createElement() if you get everything sorted out first.
I also noticed that the performance seems to be worse with latest updates. However I couldn't test the latest commits because of the strange things I mentioned.
I tried to compare with t7 when I did this manually to see what did I do wrong. But as long as valueLength is there and set to 1, it should have found the first item in the array. Same as I see here in t7 code: https://github.com/trueadm/t7/blob/master/t7.js#L108-L199
A createElement() function shouldn't be harder then this, or what?
function createElement(root, container, parent) {

	// Array holding the value types
    var values = [];

	// Template function
    var frag = function(fragment) {

	    var t = document.createElement(root.tag);

        var children = root.children;

        fragment.dom = t;
        fragment.templateElement = t;

    // Iterate through the children or values here?
    // Anyhow, the idea was to push the values to the value array, and then count the length on it.

	    if (children != null) {

            if (root.children instanceof Array) {

                for (var i = 0; i < root.children.length; i++) {

                    var child = root.children[i];

                    if (typeof child === "string" && root.children.length === 1) {

                        if (typeof child === "string") {
                            if (!parent) {
                                fragment.templateElement.textContext = child;
                            } else {
                                parent.textContext = child;
                            }
                        }
                    } else if (typeof child === "string" && root.children.length > 1) {

                    } else if (child != null) {

                    }
                }
            }
        }
        if (values.length === 1) {
            fragment.templateValue = templateValues[0];
            fragment.templateElements = null;
            fragment.templateTypes = null;
        } else if (values.length > 1) {

            fragment.templateValues = [templateValues.join(", ")];
            fragment.templateElements = Array(templateValues.length);
            fragment.templateTypes = Array(templateValues.length);
        }
   }

    return {
        dom: null,
        templateElement: null,
        template: root.children.length > 0 ? frag : ""
    };
}

// How to:
createElement( { tag:"div", children:"hello, world!" }, document.body);

I didn't continue on this due to all the other mess, and you know the code best. So I guess you can handle it better then me :+1:  I was thinking to get the same result as you do with t7. Then you could use your existing render function as before.
Anyhow. I really liked your script, I did. But I'm forced to abondon this now.  Way to complicated for others I guess to contribute. Let's hope it will be better in the future!
And for now I remove my star.

I'm a bit confused why you claim the source is broken? I've updated the vdom benchmark:
http://vdom-benchmark.github.io/vdom-benchmark/
Hopefully that can clean up some of the problems you've had. If you'd like me to help you make this createElement function for your project, I'll be happy to help you via email<EMAIL_ADDRESS>or Skype (trueadm).

Neh source seems just fine now after you fixed it. It was broken, else I guess you didn't had to add all that extra code you pushed in the latest commits. Or I'm mistaken?

No, the vdom benchmark was working fine without the refactors (you can see in the main.js on the vdom bench test what you needed to put in the template functions to make them work). I simply added them to tidy the code up a bit.


Split large FeedContainer test into multiple ones

Fixes #558.
I'd be happy if someone could review my test descriptions: do they adequately explain what each sort-order does? Unfortunately, we got directions mixed up, so "ascending" and "descending" are sometimes confusing; that's why I tried to use different words in descriptions, to hopefully make it clear what the expected behaviour is. (I hope to fix "asc" and "desc" in 3.0 sometime in the future).
Will merge in three days.

Coverage decreased (-0.02%) to 57.033% when pulling 8108a9e076517b64dcf8e808b011c41f72f6ba85 on feature/558-split-feedcontainer-tests into fcf92ba345db6110b78630b2eee86503e68100da on master.


cannot install on rakudo-star-2015.09

$ panda install URI
==> Fetching URI
==> Building URI
==> Testing URI
t/escape.t ............... ok
t/november-urlencoded.t .. ok
Could not parse URI: ftp://ftp.is.co.za/rfc/rfc1808.txt
in block  at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/URI.pm:42
in regex unenc-pchar at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar/URI.pm:83
in regex pchar at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar/URI.pm:82
in regex segment-nz-nc at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar/URI.pm:77
in regex path-noscheme at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar/URI.pm:71
in regex relative-part at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar/URI.pm:23
in regex relative-ref at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar/URI.pm:20
in regex URI-reference at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar/URI.pm:16
in regex TOP at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar/URI.pm:13
in method parse at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar.pm:21
in method parse at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/URI.pm:37
in method new at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/URI.pm:135
in block  at t/rfc-3986-examples.t:6
t/rfc-3986-examples.t ....
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 22/22 subtests
Could not parse URI: http://example.com:80/about/us?foo#bar
in block  at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/URI.pm:42
in regex unenc-pchar at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar/URI.pm:83
in regex pchar at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar/URI.pm:82
in regex segment-nz-nc at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar/URI.pm:77
in regex path-noscheme at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar/URI.pm:71
in regex relative-part at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar/URI.pm:23
in regex relative-ref at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar/URI.pm:20
in regex URI-reference at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar/URI.pm:16
in regex TOP at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar/URI.pm:13
in method parse at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/IETF/RFC_Grammar.pm:21
in method parse at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/URI.pm:37
in method new at /Users/gabor/work/perl6-lwp-simple/.panda-work/1444478571_1/lib/URI.pm:135
in block  at t/01.t:10
Looks like you planned 46 tests, but ran 1
t/01.t ...................
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 45/46 subtests
Test Summary Report
t/rfc-3986-examples.t  (Wstat: 65280 Tests: 0 Failed: 0)
Non-zero exit status: 255
Parse errors: Bad plan.  You planned 22 tests but ran 0.
t/01.t                 (Wstat: 65280 Tests: 1 Failed: 0)
Non-zero exit status: 255
Parse errors: Bad plan.  You planned 46 tests but ran 1.
Files=4, Tests=25,  4 wallclock secs ( 0.05 usr  0.02 sys +  9.36 cusr  0.39 csys =  9.82 CPU)
Result: FAIL
test stage failed for URI: Tests failed
in method throw at /Users/gabor/rakudo-star-2015.09/install/share/perl6/runtime/CORE.setting.moarvm:1
in method install at /Users/gabor/rakudo-star-2015.09/install/share/perl6/lib/Panda.pm:142
in method resolve at /Users/gabor/rakudo-star-2015.09/install/share/perl6/lib/Panda.pm:219
in sub MAIN at /Users/gabor/rakudo-star-2015.09/install/bin/panda:18
in block  at /Users/gabor/rakudo-star-2015.09/install/bin/panda:95
Failure Summary
URI(
*test stage failed for URI: Tests failed)
air:perl6-lwp-simple gabor$ which perl6
/Users/gabor/rakudo-star-2015.09/install/bin/perl6

And travis says:

Can you confirm it is working?

Isn't that build passing on the latest rakudo from Git?
The problem I saw was on rakudo Start 2105.09
BTW could you please link to the Travis-CI page of this repo? I cannot seem to find it.

And then I just found it: https://travis-ci.org/perl6-community-modules/uri

@szabgab if you want a version of URI that works with 2015.09, use the one that was shipped with Rakudo Star 2015.09.
Sadly the push/append changes post 2015.09 make it very hard to make URI run on both, so I'm closing this issue as "won't fix".

OK


Vulnerability roundup 103: wordpress-5.6.4: 3 advisories [8.8]

search, files

[ ] CVE-2018-19296 CVSSv3=8.8 (nixos-20.09)
[ ] CVE-2021-29447 CVSSv3=6.5 (nixos-20.09)
[ ] CVE-2021-29450 CVSSv3=4.3 (nixos-20.09)

Scanned versions: nixos-20.09: 86d3781c390.
Cc @basvandijk

NixOS 20.09 is EOL, so this issue isn't actionable anymore (but fixed in 21.05).


Option to disable basic android function long tap

When using Fluid Player, user in mobile (Android) can easily direct download video by long tap on video, then a pop up showing user to download video directly.
How can I disable this?
Thank you.

@devsdocs I've just checked and couldn't reproduce this. Since this issue is quite old, can you test again, or close the issue?


Official GitHub Action

We have https://github.com/PyCQA/bandit-action
Shortly we will have an official image: https://github.com/PyCQA/bandit/pull/1088
Let's get the action work complete and publish to the marketplace.
cc: @JAORMX who I know is interested in working on this.

You can now find an official action on the marketplace: https://github.com/marketplace/actions/bandit-by-pycqa


feat: slack alert manager notification implementation & test & documentation for setting up slack webhook and how to set up climatik to send alerts

What has been changed?

feat: slack alert manager notification implementation & test & documentation for setting up slack webhook and how to set up climatik to send alerts

This is great! Thanks for making this happen!

This is great! Thanks for making this happen!

my pleasure :)
I am thinking about we can add an outcoming webhook trigger from slack to update power capping limit / CPU util / Memory Util from slack. This will make users easier to control the power consumption, even without the reach of a laptop: they can do it in slack app from phones.

that's could be something you can try. The webhook should have some built-in security features e.g. only reacting to certain slack ID, etc.

@zhifanl Can you also make a demo video and post it on the README too?

@zhifanl Can you also make a demo video and post it on the README too?

sure. I can. But currently the trigger only runs locally, and the CPU & Memory metrics are hard-coded. Tomorrow I will try to finish the query Prometheus' API to check actual metric values and integrate with the slack notification service

i see. We can add more info in the alert, including the past CPU power metrics from Prometheus so the webhook can use that info to help make decisions

i see. We can add more info in the alert, including the past CPU power metrics from Prometheus so the webhook can use that info to help make decisions

definitely, will do. I will see if we can generate a small plot embedded in message based on past n minutes/hours CPU power metrics


WIP: fix initialization of Artemis Eigen volume directions

@lassoan I am still working on this with the submitter of the data to make sure the orientation is correct. I will remove WIP from the issue title and ping you when I believe it is ready for integration.

@lassoan this should be ready to go - can we proceed with review and merge?

Thank you, merged. Setting origin and spacing then getting IJKToRAS and then applying rotations and setting again IJKToRAS is not elegant, but it's OK. Instead, it would have been nicer to create a vtkTransform, call Scale, Translate, Rotate, etc. methods on it and then set the resulting matrix in IJKToRAS.

Good point Andras. I am using VTK once in a blue moon, so I will be the first to admit I am not equipped to produce elegant solutions :-\


Create page Themes

Create page themes for Quokka, http://quokkaproject.org/themes/ like http://opthemes.com/

will be done with #229


.net Core Web Api with Implicit Flow?

I would ideally like to build a web api application that uses individual user accounts login with the following capabilities:

generating access tokens
generating refresh tokens
using social logins (google, facebook, ...)
local database for storing user's info
facilitating roll-based authorization

Is implicit flow the best option? if yes, how would one set it up to generate refresh tokens, etc? Any specific sample?

To improve discoverability of frequently asked and/or more general questions, we decided to move those questions to StackOverflow:
https://stackoverflow.com/questions/tagged/?tagnames=identityserver4&sort=newest
We actively monitor SO as well but hope to create a community there so questions can get answered faster when we are not available.


There is not Microsoft.Web.LibraryInstaller.Contracts NuGet package.

Functional impact
There is not Microsoft.Web.LibraryInstaller.Contracts NuGet package.
Minimal repro steps
As docs says:

Make sure the Visual Studio SDK is installed and then create a new extensibility project by creating a VSIX Project.
Open Package Manager Console and execute Install-Package Microsoft.Web.LibraryInstaller.Contracts

Expected result
Package should be installed
Actual result
Error: Unable to find package 'Microsoft.Web.LibraryInstaller.Contracts'
Further technical details
As you can see here https://www.nuget.org/packages?q=Microsoft.Web.LibraryInstaller.Contracts "0 packages returned for Microsoft.Web.LibraryInstaller.Contracts"

This page was old and referred to the initial prototype.
At this stage, there is no defined path for extending LibMan.
It's likely we will release one in the coming months.

I have removed the content from the Extensibility Wiki.


[spec] Leading + character when parsing amount

@chitalian and I are working on a Rust port of the @solana/pay JavaScript SDK. Many float implementations, including the one in the Rust standard library and the BigNumber library used by the official SDK, consider a leading + to be valid when parsing numbers. We noticed that the description in the spec does not address the behavior of a leading + character. For reference, it looks like the official SDK happens to forbid a leading +, although it's unclear from the code whether or not it's intentional. Forbidding a leading + feels like the correct choice, but it would be great to have that clarified in the spec.

Yes, forbidding a leading plus would be good. This was intentional in the reference implementation, but we could stand to make the spec more strict.
Also, awesome project! I can't view your Gitlab, so I'm guessing it's still private?

Since you're doing an awesome job of reviewing the spec and finding places where it's ambiguous or inconsistent, would you and @chitalian take a look at #77 and the latest spec there?
Transfer requests should be mostly the same, but transaction requests are new. Wallets are actively implementing this now, but it's still open for feedback!

Yes, forbidding a leading plus would be good. This was intentional in the reference implementation, but we could stand to make the spec more strict.

Sounds good :smile:

Also, awesome project! I can't view your Gitlab, so I'm guessing it's still private?

Yep, we're in the never-ending "almost ready to publish" phase :sweat_smile:
We'll be submitting it as an entry in the Riptide hackathon though, so it'll be up soon! You're welcome to add it to the Coming soon section Supporting Wallets in the meantime - we're using it for transfer requests.

would you and @chitalian take a look at https://github.com/solana-labs/solana-pay/pull/77 and the latest spec there?

I took a quick scan over it, I will add my thoughts there.


⚠ Spryr has degraded performance

In f6e0cab, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 6201 ms

Resolved: Spryr performance has improved in 55d3b2a after 7 minutes.


Make fast wrap befor punctuation

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Hello, I am always frustrated when I use fast wrap, the example is as below:
input: |hello, how are you;
| is where the cursor at, and now I input " at | then input  to fast wrap
output: 'helloq howwareeyou$
if I input $, the result will be
'hello, how are you;'
buf what I want is
'hello, how are you';
Describe the solution you'd like
A clear and concise description of what you want to happen.
put wrap before punctuation.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I have added %; to fast_wrap.pattern, but it can not help
Additional context
Add any other context or screenshots about the feature request here.

I am facing a similar issue with fast wrap, when making json objects I sometimes forget to wrap the properties in quotes so I wanna use fast wrap to fix it but I wants to add the quotes after the colon not before

I need this too, please give us this feature!

I need this too 🥺

This should be fixed, issue can be closed :)


Errors in log that kill the plugin

Describe The Bug:
Apparently there is no "label" attribute for refrigerator and freezer temperatures in some cases.  This kills the plugin.
To Reproduce:
Restart Homebridge
Expected behavior:
It should just work
Logs:
[12/07/2021, 10:17:30] [LGThinQ] Adding new accessory: Refrigerator
[Refrigerator@Fridge@Service Label Index] Characteristic not in required or optional characteristic section for service Thermostat. Adding anyway.
[Refrigerator@Freezer@Service Label Index] Characteristic not in required or optional characteristic section for service Thermostat. Adding anyway.
(node:14547) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'label' of undefined
    at RefrigeratorStatus.get freezerTemperature [as freezerTemperature] (/usr/lib/node_modules/homebridge-lg-thinq/src/devices/Refrigerator.ts:185:58)
    at Refrigerator.updateAccessoryCharacteristic (/usr/lib/node_modules/homebridge-lg-thinq/src/devices/Refrigerator.ts:73:93)
    at new Refrigerator (/usr/lib/node_modules/homebridge-lg-thinq/src/devices/Refrigerator.ts:58:10)
    at LGThinQHomebridgePlatform.discoverDevices (/usr/lib/node_modules/homebridge-lg-thinq/src/platform.ts:110:25)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at HomebridgeAPI.<anonymous> (/usr/lib/node_modules/homebridge-lg-thinq/src/platform.ts:49:7)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:14547) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 8)
(node:14547) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Plugin Config:
        {
            "username"<EMAIL_ADDRESS>            "password": "xxx",
            "country": "US",
            "language": "en-US",
            "thinq1": true,
            "washer_trigger": false,
            "platform": "LGThinQ"
        }

Screenshots:

Environment:

Plugin Version: v0.2.12
Homebridge Version:  v1.3.3
Node.js Version: v14.16.0
NPM Version: 7.19.1
Operating System: raspbain

I already released new version to fix this issue, please update


Investigate compressed 10-bit format

SVT-AV1 uses a bitplaned 10-bit format: https://github.com/OpenVisualCloud/SVT-AV1/blob/master/Docs/svt-av1_encoder_user_guide.pdf
We should look at if this makes any sense for us to do for speed.

vpmultishiftqb (_mm512_multishift_epi64_epi8) introduced in cannon lake could make this more efficient in the future.

The main problem I have with this is that the loop filters in svt-av1 are applied on planar 16 bit data. This means you end up with both a 8+2->16 and 16->8+2 copy per frame. If you just wanted 8 bit mc, you could do a single 16->8 copy instead and it would be less memory bandwidth.


Update upload event hub metadata to include file properties

Whenever an upload occurs the metadata associated with that upload is relayed to an event hub.  The goal of this ticket is to expand on the event message data to include some of the blob properties, including:

blob url
last updated
creation date
file size

The content of the event hub events will be JSON in the following format:
{
   "Properties":{
      "ContentLength":10485760,
      "LastModified":"2023-03-30T14:10:08.0000000",
      "CreatedOn":"2023-03-30T14:10:08.0000000",
      "BlobUrl":"https://mbkdataexchange.blob.core.windows.net/ndlp-routineimmunization/2023/03/30/10MB-test-file_638157822075310841"
   },
   "Metadata":{
      "orig_filename":"10MB-test-file",
      "meta_destination_id":"ndlp",
      "meta_ext_entity":"DD2",
      "meta_ext_event":"routineImmunization",
      "meta_ext_filename":"10MB-test-file",
      "meta_ext_objectkey":"78c9c86f-55d7-43a9-9ee5-0f119ac69686",
      "meta_ext_source":"IZGW",
      "meta_ext_sourceversion":"V2022-12-31",
<EMAIL_ADDRESS>      "tus_tguid":"4bc83fbbbed7128d58154ec3a3d15174"
   },
   "EventProcessedUtcTime":"2023-03-30T14:10:30.4886763Z",
   "PartitionId":1,
   "EventEnqueuedUtcTime":"2023-03-30T14:10:12.7240000Z"
}

Updates complete and deployed to DEV.
Blocker:  I do not have permissions in Azure portal to "preview" the event hub data to verify content.

Labeled "customer support" because...

Enables PulseNet UAT
Is a trivial change (no app or ops changes, just a config update)


Added pr templates

Do you mean in both templates @garak ?

Do you mean in both templates @garak ?

Yes, I guess that it makes sense for both


(v4.2.2stable) Using "Pick Color" on a color changes all the colors with the same value (even commented ones) in the same line of code

Tested versions

Tested in Godot v4.2.2stable

System information
macOS Big Sur v11.7.10 - Godot v4.2.2stable
Issue description
modifying a color using "Pick Color" in the editor changes the commented version in the same line of code
Steps to reproduce
A)
1: In script editor, create a new array with one Color
  var a = [Color(0.3, 0.3, 0.3, 1.0)]

  2: copy the color and paste it as a new element of the array in the same line

  var a = [Color(0.3, 0.3, 0.3, 1.0), Color(0.3, 0.3, 0.3, 1.0)]

  3: right click on the first "Color"

 var a = [Color(0.3, 0.3, 0.3, 1.0), Color(0.3, 0.3, 0.3, 1.0)]
                  ^
       right click here

  4: select "Pick Color" in the menu that appears

 var a = [Color(0.3, 0.3, 0.3, 1.0), Color(0.3, 0.3, 0.3, 1.0)]
        __________________
        | Undo
        | Redo
        | Cut
        | Copy
        | Paste
        | Select All
        | Indent
        | Unindent
        | Toggle Comment
        | Toggle Bookmark
        | Lookup Symbol
        | Pick Color <-------- select this

  5: Select any other color in the color picker menu that appears and it will also change the other one

  var a = [Color(0.5, 0.8, 0.13, 0.21), Color(0.5, 0.8, 0.13, 0.21)] <--- this one shouldn't change!

B)
1: In script editor, create a new color
  var c = Color(0.3, 0.3, 0.3, 1.0)

  2: copy the color and paste it as a comment at the end of the line

  var c = Color(0.3, 0.3, 0.3, 1.0)#Color(0.3, 0.3, 0.3, 1.0)

  3: right click on the first "Color"

  var c = Color(0.3, 0.3, 0.3, 1.0)#Color(0.3, 0.3, 0.3, 1.0)
                  ^
       right click here

  4: select "Pick Color" in the menu that appears

  var c = Color(0.3, 0.3, 0.3, 1.0)#Color(0.3, 0.3, 0.3, 1.0)
        __________________
        | Undo
        | Redo
        | Cut
        | Copy
        | Paste
        | Select All
        | Indent
        | Unindent
        | Toggle Comment
        | Toggle Bookmark
        | Lookup Symbol
        | Pick Color <-------- select this

  5: Select any other color in the color picker menu that appears and it will also change the commented one

  var c = Color(0.5, 0.8, 0.13, 0.21)#Color(0.5, 0.8, 0.13, 0.21) <--- this one shouldn't change!

Minimal reproduction project (MRP)
colorPickerIssue.zip

Sorry for any grammatical error!


Minor correction - removed special characters within code example

Fixes an issue under the "Pages" section

It looks like the top part of the example, *** TestCases *, is outside of the code block and truncated.

@all-contributors please add emanlove for doc.

Thanks to Ed