Fix webhook conflict issue if installation is not successful

Please provide a description of this PR:
Fix https://github.com/istio/istio/issues/48112.
This occurs when the installation is either unsuccessful or interrupted. I'm not certain how to write a test for this, but the idea is to use the shared code in ProcessDefaultWebhook to check whether the webhook installed (like istio-sidecar-injector) will be processed after the installation. If it is to be processed, we will skip it advancely in case of a reported conflict, which will otherwise block the current installation.
This PR also optimizes the webhook analysis process, avoids the situation described here because the original code listed twice before running the fake client:
https://github.com/istio/istio/blob/09917748493f1e29389d6c5eb9dee0f99db796fc/pkg/kube/client.go#L238-L245
The change involves avoiding the use of kubeclient (which originally informed webhook and service changes) and includes listed in-cluster webhook resources from the client.

@hanxiaop: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a1973d98f41d900947125bcc325a7109d7be6ea4
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a1973d98f41d900947125bcc325a7109d7be6ea4
link
true
/test unit-tests-arm64

unit-tests_istio
a1973d98f41d900947125bcc325a7109d7be6ea4
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a1973d98f41d900947125bcc325a7109d7be6ea4
link
true
/test unit-tests-arm64

unit-tests_istio
a1973d98f41d900947125bcc325a7109d7be6ea4
link
true
/test unit-tests

gencheck_istio
a1973d98f41d900947125bcc325a7109d7be6ea4
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
a1973d98f41d900947125bcc325a7109d7be6ea4
link
true
/test unit-tests

gencheck_istio
a1973d98f41d900947125bcc325a7109d7be6ea4
link
true
/test gencheck

lint_istio
566c2790f8d9e4f53239bd2e0aea2500d653b20b
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
a1973d98f41d900947125bcc325a7109d7be6ea4
link
true
/test unit-tests

lint_istio
566c2790f8d9e4f53239bd2e0aea2500d653b20b
link
true
/test lint

gencheck_istio
566c2790f8d9e4f53239bd2e0aea2500d653b20b
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
566c2790f8d9e4f53239bd2e0aea2500d653b20b
link
true
/test gencheck

lint_istio
5445e45ebd73f8973245da4ad5cd62c7445bde93
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio/wg-environments-maintainers @istio/wg-user-experience-maintainers PTAL, thanks!
The important logic should just be:
https://github.com/istio/istio/blob/60e081386aba9a8e379b8cdf91f6780c38665a46/operator/pkg/helmreconciler/reconciler.go#L544-L555

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@hanxiaop: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
8514834753f1a7f326f34400dcc94dc13f79136e
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
8514834753f1a7f326f34400dcc94dc13f79136e
link
true
/test lint

unit-tests-arm64_istio
8514834753f1a7f326f34400dcc94dc13f79136e
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
8514834753f1a7f326f34400dcc94dc13f79136e
link
true
/test lint

unit-tests-arm64_istio
8514834753f1a7f326f34400dcc94dc13f79136e
link
true
/test unit-tests-arm64

gencheck_istio
8514834753f1a7f326f34400dcc94dc13f79136e
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
8514834753f1a7f326f34400dcc94dc13f79136e
link
true
/test lint

gencheck_istio
ae3175f880cd00c94f96b50071dcbc1fe6119273
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
ae3175f880cd00c94f96b50071dcbc1fe6119273
link
true
/test gencheck

lint_istio
ae3175f880cd00c94f96b50071dcbc1fe6119273
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn can you take a look at this? Thanks!


Builtin primitive types are not abbreviated in, say, "Implement missing members" assist

rust-analyzer version: 2020-04-13 (c388130)
To reproduce, invoke "Implement missing members" assist on the following program:
trait Foo {
    fn f(x: u32);
}
struct S;
impl Foo for S {}

Expected result:
impl Foo for S {
    fn f(x: u32) { todo!() }
}

Actual result:
impl Foo for S {
    fn f(x: std::primitive::u32) { todo!() }
}

If I explicitly add the use std::primitive::u32 use declaration, the assist will work as expected. But this use declaration is already implied, so it should work without it too.

Huh, is that in nightly? I can't see std::primitive on stable...

Yes.
> rustc --version --verbose
rustc 1.44.0-nightly (b543afca9 2020-04-05)
binary: rustc
commit-hash: b543afca9b90ad6e4689b6d613ab51f9d3ba15e7
commit-date: 2020-04-05
host: x86_64-pc-windows-msvc
release: 1.44.0-nightly
LLVM version: 9.0

I think this is actually in Beta already.

I think we need to teach find_path that the builtin types are always in scope :thinking:


[BUG] Dependabot config to update Maven dependencies is not working

Describe the bug
Currently there are no dependabot Pull requets created for Maven dependencies despite a config trying to do it in dependabot.yml file
Additional context
for instance https://mvnrepository.com/artifact/commons-io/commons-io/2.11.0 https://github.com/KaotoIO/kaoto-backend/blob/2a3ae570d7725524dfecc33d621242da0d974d29/metadata/pom.xml#L49

on https://github.com/KaotoIO/kaoto-backend/network/updates , we can notice that there isn't a pom dependabot job:

For comparison, there is specific pom.xml entry on this other repository:

ah it is because it was disabled in the dependabot file:

https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#disabling-dependabot-version-updates
https://github.com/KaotoIO/kaoto-backend/blob/0cd6e8d5b8d7e3f6e285685f1ea28dde6a88e78d/.github/dependabot.yml#L7
and based on comment, the intent was to be no limit https://github.com/KaotoIO/kaoto-backend/commit/2c0d261afff15cd682a8a08ca76750778d922d98 so a matter of updating it


unpacking source archive /nix/store/j93r3grj36pzbq4bz47qfximx7ffawgy-xtend-4.0.2.tgz
unpacking source archive /nix/store/ikpdr887y96sybx61gy4yag0lyrwky0q-yallist-2.1.2.tgz
pinpointing versions of dependencies...
patching script interpreter paths in .
./dat/bin/cli.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/bittorrent-dht/bin/update-authors.sh: interpreter directive changed from "/bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/node-gyp-build/bin.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/node-gyp-build/build-test.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/node-gyp-build/optional.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/sodium-native/configure: interpreter directive changed from "/bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/node_modules/node-gyp-build/bin.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/sodium-native/node_modules/node-gyp-build/build-test.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/sodium-native/node_modules/node-gyp-build/optional.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/sodium-native/libsodium/test/default/nacl-test-wrapper.sh: interpreter directive changed from " /bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/test/constcheck.sh: interpreter directive changed from " /bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/nativeclient-pnacl.sh: interpreter directive changed from " /bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/android-armv8-a.sh: interpreter directive changed from "/bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/android-build.sh: interpreter directive changed from " /bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/android-mips32.sh: interpreter directive changed from "/bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/msys2-win64.sh: interpreter directive changed from " /bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/generate-emscripten-symbols.sh: interpreter directive changed from " /bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/osx.sh: interpreter directive changed from " /bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/ios.sh: interpreter directive changed from " /bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/msys2-win32.sh: interpreter directive changed from " /bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/watchos.sh: interpreter directive changed from " /bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/nativeclient-x86.sh: interpreter directive changed from " /bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/android-mips64.sh: interpreter directive changed from "/bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/android-arm.sh: interpreter directive changed from "/bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/nativeclient-x86_64.sh: interpreter directive changed from " /bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/emscripten.sh: interpreter directive changed from " /bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/android-armv7-a.sh: interpreter directive changed from "/bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/android-x86_64.sh: interpreter directive changed from "/bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/dist-build/android-x86.sh: interpreter directive changed from "/bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/sodium-native/libsodium/autogen.sh: interpreter directive changed from " /bin/sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/rimraf/bin.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/ncp/bin/ncp: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/utp-native/ucat.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/utp-native/node_modules/node-gyp-build/bin.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/utp-native/node_modules/node-gyp-build/build-test.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/utp-native/node_modules/node-gyp-build/optional.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/nan/tools/1to2.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/is-ci/bin.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/async/support/sync-package-managers.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/dns-discovery/bin.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/semver/bin/semver: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/recursive-watch/bin.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/multicast-dns/cli.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/sshpk/bin/sshpk-conv: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/sshpk/bin/sshpk-verify: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/sshpk/bin/sshpk-sign: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/mime/cli.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/mime/src/build.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/dat-log/cli.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/network-address/cli.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/dat-doctor/cli.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/discovery-swarm/node_modules/utp-native/ucat.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/uuid/bin/uuid: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/rc/cli.js: interpreter directive changed from " /usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/which/bin/which: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/ajv/scripts/travis-gh-pages: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/bash"
./dat/node_modules/ajv/scripts/info: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/ajv/scripts/publish-built-version: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/bash"
./dat/node_modules/ajv/scripts/prepare-tests: interpreter directive changed from "/usr/bin/env sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/node_modules/mkdirp/bin/cmd.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/node_modules/winston/node_modules/async/support/sync-package-managers.js: interpreter directive changed from "/usr/bin/env node" to "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node"
./dat/package.sh: interpreter directive changed from "/usr/bin/env sh" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/sh"
./dat/download.sh: interpreter directive changed from "/bin/bash" to "/nix/store/mg4y1vjgvz508n4qrhcilz52j0iil1f2-bash-4.4-p23/bin/bash"
No package-lock.json file found, reconstructing...
Adding metadata fields to: node_modules/abstract-random-access/package.json
Adding metadata fields to: node_modules/ajv/package.json
Adding metadata fields to: node_modules/ansi-align/package.json
Adding metadata fields to: node_modules/ansi-diff/package.json
Adding metadata fields to: node_modules/ansi-regex/package.json
Adding metadata fields to: node_modules/ansi-split/package.json
Adding metadata fields to: node_modules/ansi-styles/package.json
Adding metadata fields to: node_modules/anymatch/package.json
Adding metadata fields to: node_modules/ap/package.json
Adding metadata fields to: node_modules/append-tree/package.json
Adding metadata fields to: node_modules/append-tree/node_modules/process-nextick-args/package.json
Adding metadata fields to: node_modules/append-tree/node_modules/varint/package.json
Adding metadata fields to: node_modules/arr-diff/package.json
Adding metadata fields to: node_modules/arr-flatten/package.json
Adding metadata fields to: node_modules/arr-union/package.json
Adding metadata fields to: node_modules/array-lru/package.json
Adding metadata fields to: node_modules/array-unique/package.json
Adding metadata fields to: node_modules/asn1/package.json
Adding metadata fields to: node_modules/assert-plus/package.json
Adding metadata fields to: node_modules/assign-symbols/package.json
Adding metadata fields to: node_modules/async/package.json
Adding metadata fields to: node_modules/asynckit/package.json
Adding metadata fields to: node_modules/atob/package.json
Adding metadata fields to: node_modules/atomic-batcher/package.json
Adding metadata fields to: node_modules/aws-sign2/package.json
Adding metadata fields to: node_modules/aws4/package.json
Adding metadata fields to: node_modules/balanced-match/package.json
Adding metadata fields to: node_modules/base/package.json
Adding metadata fields to: node_modules/base/node_modules/define-property/package.json
Adding metadata fields to: node_modules/bcrypt-pbkdf/package.json
Adding metadata fields to: node_modules/bencode/package.json
Adding metadata fields to: node_modules/bitfield-rle/package.json
Adding metadata fields to: node_modules/bitfield-rle/node_modules/varint/package.json
Adding metadata fields to: node_modules/bittorrent-dht/package.json
Adding metadata fields to: node_modules/bittorrent-dht/node_modules/debug/package.json
Adding metadata fields to: node_modules/blake2b/package.json
Adding metadata fields to: node_modules/blake2b-wasm/package.json
Adding metadata fields to: node_modules/body/package.json
Adding metadata fields to: node_modules/boxen/package.json
Adding metadata fields to: node_modules/brace-expansion/package.json
Adding metadata fields to: node_modules/braces/package.json
Adding metadata fields to: node_modules/braces/node_modules/extend-shallow/package.json
Adding metadata fields to: node_modules/buffer-alloc/package.json
Adding metadata fields to: node_modules/buffer-alloc-unsafe/package.json
Adding metadata fields to: node_modules/buffer-equals/package.json
Adding metadata fields to: node_modules/buffer-fill/package.json
Adding metadata fields to: node_modules/buffer-from/package.json
Adding metadata fields to: node_modules/bulk-write-stream/package.json
Adding metadata fields to: node_modules/bytes/package.json
Adding metadata fields to: node_modules/cache-base/package.json
Adding metadata fields to: node_modules/call-me-maybe/package.json
Adding metadata fields to: node_modules/camelcase/package.json
Adding metadata fields to: node_modules/capture-stack-trace/package.json
Adding metadata fields to: node_modules/caseless/package.json
Adding metadata fields to: node_modules/chalk/package.json
Adding metadata fields to: node_modules/chrome-dgram/package.json
Adding metadata fields to: node_modules/chrome-dns/package.json
Adding metadata fields to: node_modules/chrome-net/package.json
Adding metadata fields to: node_modules/ci-info/package.json
Adding metadata fields to: node_modules/circular-append-file/package.json
Adding metadata fields to: node_modules/class-utils/package.json
Adding metadata fields to: node_modules/class-utils/node_modules/define-property/package.json
Adding metadata fields to: node_modules/class-utils/node_modules/is-accessor-descriptor/package.json
Adding metadata fields to: node_modules/class-utils/node_modules/is-accessor-descriptor/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/class-utils/node_modules/is-data-descriptor/package.json
Adding metadata fields to: node_modules/class-utils/node_modules/is-data-descriptor/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/class-utils/node_modules/is-descriptor/package.json
Adding metadata fields to: node_modules/class-utils/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/cli-boxes/package.json
Adding metadata fields to: node_modules/cli-spinners/package.json
Adding metadata fields to: node_modules/cli-truncate/package.json
Adding metadata fields to: node_modules/cliclopts/package.json
Adding metadata fields to: node_modules/codecs/package.json
Adding metadata fields to: node_modules/collection-visit/package.json
Adding metadata fields to: node_modules/color-convert/package.json
Adding metadata fields to: node_modules/color-name/package.json
Adding metadata fields to: node_modules/colors/package.json
Adding metadata fields to: node_modules/combined-stream/package.json
Adding metadata fields to: node_modules/component-emitter/package.json
Adding metadata fields to: node_modules/concat-map/package.json
Adding metadata fields to: node_modules/concat-stream/package.json
Adding metadata fields to: node_modules/configstore/package.json
Adding metadata fields to: node_modules/connections/package.json
Adding metadata fields to: node_modules/content-types/package.json
Adding metadata fields to: node_modules/copy-descriptor/package.json
Adding metadata fields to: node_modules/core-util-is/package.json
Adding metadata fields to: node_modules/corsify/package.json
Adding metadata fields to: node_modules/count-trailing-zeros/package.json
Adding metadata fields to: node_modules/create-error-class/package.json
Adding metadata fields to: node_modules/cross-spawn/package.json
Adding metadata fields to: node_modules/crypto-random-string/package.json
Adding metadata fields to: node_modules/cycle/package.json
Adding metadata fields to: node_modules/dashdash/package.json
Adding metadata fields to: node_modules/dat-dns/package.json
Adding metadata fields to: node_modules/dat-doctor/package.json
Adding metadata fields to: node_modules/dat-encoding/package.json
Adding metadata fields to: node_modules/dat-ignore/package.json
Adding metadata fields to: node_modules/dat-json/package.json
Adding metadata fields to: node_modules/dat-link-resolve/package.json
Adding metadata fields to: node_modules/dat-log/package.json
Adding metadata fields to: node_modules/dat-log/node_modules/neat-log/package.json
Adding metadata fields to: node_modules/dat-node/package.json
Adding metadata fields to: node_modules/dat-registry/package.json
Adding metadata fields to: node_modules/dat-secret-storage/package.json
Adding metadata fields to: node_modules/dat-storage/package.json
Adding metadata fields to: node_modules/dat-swarm-defaults/package.json
Adding metadata fields to: node_modules/debug/package.json
Adding metadata fields to: node_modules/decode-uri-component/package.json
Adding metadata fields to: node_modules/decompress-response/package.json
Adding metadata fields to: node_modules/deep-equal/package.json
Adding metadata fields to: node_modules/deep-extend/package.json
Adding metadata fields to: node_modules/define-property/package.json
Adding metadata fields to: node_modules/delayed-stream/package.json
Adding metadata fields to: node_modules/diffy/package.json
Adding metadata fields to: node_modules/directory-index-html/package.json
Adding metadata fields to: node_modules/discovery-channel/package.json
Adding metadata fields to: node_modules/discovery-channel/node_modules/debug/package.json
Adding metadata fields to: node_modules/discovery-channel/node_modules/ms/package.json
Adding metadata fields to: node_modules/discovery-channel/node_modules/thunky/package.json
Adding metadata fields to: node_modules/discovery-swarm/package.json
Adding metadata fields to: node_modules/discovery-swarm/node_modules/utp-native/package.json
Adding metadata fields to: node_modules/dns-discovery/package.json
Adding metadata fields to: node_modules/dns-discovery/node_modules/debug/package.json
Adding metadata fields to: node_modules/dns-discovery/node_modules/lru/package.json
Adding metadata fields to: node_modules/dns-discovery/node_modules/ms/package.json
Adding metadata fields to: node_modules/dns-packet/package.json
Adding metadata fields to: node_modules/dns-socket/package.json
Adding metadata fields to: node_modules/dom-walk/package.json
Adding metadata fields to: node_modules/dot-prop/package.json
Adding metadata fields to: node_modules/duplexer3/package.json
Adding metadata fields to: node_modules/duplexify/package.json
Adding metadata fields to: node_modules/ecc-jsbn/package.json
Adding metadata fields to: node_modules/end-of-stream/package.json
Adding metadata fields to: node_modules/escape-string-regexp/package.json
Adding metadata fields to: node_modules/execa/package.json
Adding metadata fields to: node_modules/expand-brackets/package.json
Adding metadata fields to: node_modules/expand-brackets/node_modules/debug/package.json
Adding metadata fields to: node_modules/expand-brackets/node_modules/define-property/package.json
Adding metadata fields to: node_modules/expand-brackets/node_modules/extend-shallow/package.json
Adding metadata fields to: node_modules/expand-brackets/node_modules/is-accessor-descriptor/package.json
Adding metadata fields to: node_modules/expand-brackets/node_modules/is-accessor-descriptor/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/expand-brackets/node_modules/is-data-descriptor/package.json
Adding metadata fields to: node_modules/expand-brackets/node_modules/is-data-descriptor/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/expand-brackets/node_modules/is-descriptor/package.json
Adding metadata fields to: node_modules/expand-brackets/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/expand-brackets/node_modules/ms/package.json
Adding metadata fields to: node_modules/extend/package.json
Adding metadata fields to: node_modules/extend-shallow/package.json
Adding metadata fields to: node_modules/extend-shallow/node_modules/is-extendable/package.json
Adding metadata fields to: node_modules/extglob/package.json
Adding metadata fields to: node_modules/extglob/node_modules/define-property/package.json
Adding metadata fields to: node_modules/extglob/node_modules/extend-shallow/package.json
Adding metadata fields to: node_modules/extsprintf/package.json
Adding metadata fields to: node_modules/eyes/package.json
Adding metadata fields to: node_modules/fast-bitfield/package.json
Adding metadata fields to: node_modules/fast-deep-equal/package.json
Adding metadata fields to: node_modules/fast-json-stable-stringify/package.json
Adding metadata fields to: node_modules/fd-lock/package.json
Adding metadata fields to: node_modules/fd-lock/node_modules/napi-macros/package.json
Adding metadata fields to: node_modules/fd-read-stream/package.json
Adding metadata fields to: node_modules/figures/package.json
Adding metadata fields to: node_modules/fill-range/package.json
Adding metadata fields to: node_modules/fill-range/node_modules/extend-shallow/package.json
Adding metadata fields to: node_modules/flat-tree/package.json
Adding metadata fields to: node_modules/for-in/package.json
Adding metadata fields to: node_modules/forever-agent/package.json
Adding metadata fields to: node_modules/form-data/package.json
Adding metadata fields to: node_modules/fragment-cache/package.json
Adding metadata fields to: node_modules/from2/package.json
Adding metadata fields to: node_modules/fs.realpath/package.json
Adding metadata fields to: node_modules/get-stream/package.json
Adding metadata fields to: node_modules/get-value/package.json
Adding metadata fields to: node_modules/getpass/package.json
Adding metadata fields to: node_modules/glob/package.json
Adding metadata fields to: node_modules/global/package.json
Adding metadata fields to: node_modules/global-dirs/package.json
Adding metadata fields to: node_modules/got/package.json
Adding metadata fields to: node_modules/graceful-fs/package.json
Adding metadata fields to: node_modules/har-schema/package.json
Adding metadata fields to: node_modules/har-validator/package.json
Adding metadata fields to: node_modules/has-flag/package.json
Adding metadata fields to: node_modules/has-value/package.json
Adding metadata fields to: node_modules/has-values/package.json
Adding metadata fields to: node_modules/has-values/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/http-methods/package.json
Adding metadata fields to: node_modules/http-signature/package.json
Adding metadata fields to: node_modules/hypercore/package.json
Adding metadata fields to: node_modules/hypercore/node_modules/codecs/package.json
Adding metadata fields to: node_modules/hypercore/node_modules/unordered-set/package.json
Adding metadata fields to: node_modules/hypercore-crypto/package.json
Adding metadata fields to: node_modules/hypercore-protocol/package.json
Adding metadata fields to: node_modules/hypercore-protocol/node_modules/varint/package.json
Adding metadata fields to: node_modules/hyperdrive/package.json
Adding metadata fields to: node_modules/hyperdrive-http/package.json
Adding metadata fields to: node_modules/hyperdrive-network-speed/package.json
Adding metadata fields to: node_modules/hyperdrive-network-speed/node_modules/debug/package.json
Adding metadata fields to: node_modules/i/package.json
Adding metadata fields to: node_modules/import-lazy/package.json
Adding metadata fields to: node_modules/imurmurhash/package.json
Adding metadata fields to: node_modules/inflight/package.json
Adding metadata fields to: node_modules/inherits/package.json
Adding metadata fields to: node_modules/ini/package.json
Adding metadata fields to: node_modules/inspect-custom-symbol/package.json
Adding metadata fields to: node_modules/ip/package.json
Adding metadata fields to: node_modules/is-accessor-descriptor/package.json
Adding metadata fields to: node_modules/is-buffer/package.json
Adding metadata fields to: node_modules/is-ci/package.json
Adding metadata fields to: node_modules/is-data-descriptor/package.json
Adding metadata fields to: node_modules/is-descriptor/package.json
Adding metadata fields to: node_modules/is-extendable/package.json
Adding metadata fields to: node_modules/is-fullwidth-code-point/package.json
Adding metadata fields to: node_modules/is-function/package.json
Adding metadata fields to: node_modules/is-installed-globally/package.json
Adding metadata fields to: node_modules/is-npm/package.json
Adding metadata fields to: node_modules/is-number/package.json
Adding metadata fields to: node_modules/is-number/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/is-obj/package.json
Adding metadata fields to: node_modules/is-options/package.json
Adding metadata fields to: node_modules/is-path-inside/package.json
Adding metadata fields to: node_modules/is-plain-object/package.json
Adding metadata fields to: node_modules/is-redirect/package.json
Adding metadata fields to: node_modules/is-retry-allowed/package.json
Adding metadata fields to: node_modules/is-stream/package.json
Adding metadata fields to: node_modules/is-string/package.json
Adding metadata fields to: node_modules/is-typedarray/package.json
Adding metadata fields to: node_modules/is-windows/package.json
Adding metadata fields to: node_modules/isarray/package.json
Adding metadata fields to: node_modules/isexe/package.json
Adding metadata fields to: node_modules/isobject/package.json
Adding metadata fields to: node_modules/isstream/package.json
Adding metadata fields to: node_modules/iterators/package.json
Adding metadata fields to: node_modules/jsbn/package.json
Adding metadata fields to: node_modules/json-schema/package.json
Adding metadata fields to: node_modules/json-schema-traverse/package.json
Adding metadata fields to: node_modules/json-stringify-safe/package.json
Adding metadata fields to: node_modules/jsprim/package.json
Adding metadata fields to: node_modules/k-bucket/package.json
Adding metadata fields to: node_modules/k-rpc/package.json
Adding metadata fields to: node_modules/k-rpc/node_modules/k-bucket/package.json
Adding metadata fields to: node_modules/k-rpc-socket/package.json
Adding metadata fields to: node_modules/k-rpc-socket/node_modules/bencode/package.json
Adding metadata fields to: node_modules/keypress/package.json
Adding metadata fields to: node_modules/kind-of/package.json
Adding metadata fields to: node_modules/last-one-wins/package.json
Adding metadata fields to: node_modules/latest-version/package.json
Adding metadata fields to: node_modules/length-prefixed-message/package.json
Adding metadata fields to: node_modules/lodash.throttle/package.json
Adding metadata fields to: node_modules/lowercase-keys/package.json
Adding metadata fields to: node_modules/lru/package.json
Adding metadata fields to: node_modules/lru-cache/package.json
Adding metadata fields to: node_modules/make-dir/package.json
Adding metadata fields to: node_modules/map-cache/package.json
Adding metadata fields to: node_modules/map-visit/package.json
Adding metadata fields to: node_modules/memory-pager/package.json
Adding metadata fields to: node_modules/menu-string/package.json
Adding metadata fields to: node_modules/merkle-tree-stream/package.json
Adding metadata fields to: node_modules/micromatch/package.json
Adding metadata fields to: node_modules/mime/package.json
Adding metadata fields to: node_modules/mime-db/package.json
Adding metadata fields to: node_modules/mime-types/package.json
Adding metadata fields to: node_modules/mimic-response/package.json
Adding metadata fields to: node_modules/min-document/package.json
Adding metadata fields to: node_modules/minimatch/package.json
Adding metadata fields to: node_modules/minimist/package.json
Adding metadata fields to: node_modules/mirror-folder/package.json
Adding metadata fields to: node_modules/mixin-deep/package.json
Adding metadata fields to: node_modules/mixin-deep/node_modules/is-extendable/package.json
Adding metadata fields to: node_modules/mkdirp/package.json
Adding metadata fields to: node_modules/mkdirp/node_modules/minimist/package.json
Adding metadata fields to: node_modules/ms/package.json
Adding metadata fields to: node_modules/multi-random-access/package.json
Adding metadata fields to: node_modules/multicast-dns/package.json
Adding metadata fields to: node_modules/multistream/package.json
Adding metadata fields to: node_modules/mute-stream/package.json
Adding metadata fields to: node_modules/mutexify/package.json
Adding metadata fields to: node_modules/nan/package.json
Adding metadata fields to: node_modules/nanoassert/package.json
Adding metadata fields to: node_modules/nanobus/package.json
Adding metadata fields to: node_modules/nanoguard/package.json
Adding metadata fields to: node_modules/nanomatch/package.json
Adding metadata fields to: node_modules/nanoscheduler/package.json
Adding metadata fields to: node_modules/nanotiming/package.json
Adding metadata fields to: node_modules/napi-macros/package.json
Adding metadata fields to: node_modules/ncp/package.json
Adding metadata fields to: node_modules/neat-input/package.json
Adding metadata fields to: node_modules/neat-log/package.json
Adding metadata fields to: node_modules/neat-spinner/package.json
Adding metadata fields to: node_modules/neat-tasks/package.json
Adding metadata fields to: node_modules/nets/package.json
Adding metadata fields to: node_modules/network-address/package.json
Adding metadata fields to: node_modules/node-gyp-build/package.json
Adding metadata fields to: node_modules/normalize-path/package.json
Adding metadata fields to: node_modules/npm-run-path/package.json
Adding metadata fields to: node_modules/oauth-sign/package.json
Adding metadata fields to: node_modules/object-copy/package.json
Adding metadata fields to: node_modules/object-copy/node_modules/define-property/package.json
Adding metadata fields to: node_modules/object-copy/node_modules/is-accessor-descriptor/package.json
Adding metadata fields to: node_modules/object-copy/node_modules/is-data-descriptor/package.json
Adding metadata fields to: node_modules/object-copy/node_modules/is-descriptor/package.json
Adding metadata fields to: node_modules/object-copy/node_modules/is-descriptor/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/object-copy/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/object-visit/package.json
Adding metadata fields to: node_modules/object.pick/package.json
Adding metadata fields to: node_modules/once/package.json
Adding metadata fields to: node_modules/os-homedir/package.json
Adding metadata fields to: node_modules/p-finally/package.json
Adding metadata fields to: node_modules/package-json/package.json
Adding metadata fields to: node_modules/parse-headers/package.json
Adding metadata fields to: node_modules/pascalcase/package.json
Adding metadata fields to: node_modules/path-is-absolute/package.json
Adding metadata fields to: node_modules/path-is-inside/package.json
Adding metadata fields to: node_modules/path-key/package.json
Adding metadata fields to: node_modules/performance-now/package.json
Adding metadata fields to: node_modules/pify/package.json
Adding metadata fields to: node_modules/pkginfo/package.json
Adding metadata fields to: node_modules/posix-character-classes/package.json
Adding metadata fields to: node_modules/prepend-http/package.json
Adding metadata fields to: node_modules/prettier-bytes/package.json
Adding metadata fields to: node_modules/pretty-hash/package.json
Adding metadata fields to: node_modules/process/package.json
Adding metadata fields to: node_modules/process-nextick-args/package.json
Adding metadata fields to: node_modules/progress-string/package.json
Adding metadata fields to: node_modules/prompt/package.json
Adding metadata fields to: node_modules/protocol-buffers-encodings/package.json
Adding metadata fields to: node_modules/protocol-buffers-encodings/node_modules/varint/package.json
Adding metadata fields to: node_modules/pseudomap/package.json
Adding metadata fields to: node_modules/psl/package.json
Adding metadata fields to: node_modules/pump/package.json
Adding metadata fields to: node_modules/punycode/package.json
Adding metadata fields to: node_modules/qs/package.json
Adding metadata fields to: node_modules/random-access-file/package.json
Adding metadata fields to: node_modules/random-access-memory/package.json
Adding metadata fields to: node_modules/random-access-storage/package.json
Adding metadata fields to: node_modules/randombytes/package.json
Adding metadata fields to: node_modules/range-parser/package.json
Adding metadata fields to: node_modules/rc/package.json
Adding metadata fields to: node_modules/read/package.json
Adding metadata fields to: node_modules/readable-stream/package.json
Adding metadata fields to: node_modules/readable-stream/node_modules/safe-buffer/package.json
Adding metadata fields to: node_modules/recursive-watch/package.json
Adding metadata fields to: node_modules/regex-not/package.json
Adding metadata fields to: node_modules/registry-auth-token/package.json
Adding metadata fields to: node_modules/registry-url/package.json
Adding metadata fields to: node_modules/remove-array-items/package.json
Adding metadata fields to: node_modules/remove-trailing-separator/package.json
Adding metadata fields to: node_modules/repeat-element/package.json
Adding metadata fields to: node_modules/repeat-string/package.json
Adding metadata fields to: node_modules/request/package.json
Adding metadata fields to: node_modules/resolve-url/package.json
Adding metadata fields to: node_modules/ret/package.json
Adding metadata fields to: node_modules/revalidator/package.json
Adding metadata fields to: node_modules/rimraf/package.json
Adding metadata fields to: node_modules/run-series/package.json
Adding metadata fields to: node_modules/rusha/package.json
Adding metadata fields to: node_modules/safe-buffer/package.json
Adding metadata fields to: node_modules/safe-regex/package.json
Adding metadata fields to: node_modules/safer-buffer/package.json
Adding metadata fields to: node_modules/semver/package.json
Adding metadata fields to: node_modules/semver-diff/package.json
Adding metadata fields to: node_modules/set-value/package.json
Adding metadata fields to: node_modules/set-value/node_modules/extend-shallow/package.json
Adding metadata fields to: node_modules/shebang-command/package.json
Adding metadata fields to: node_modules/shebang-regex/package.json
Adding metadata fields to: node_modules/signal-exit/package.json
Adding metadata fields to: node_modules/signed-varint/package.json
Adding metadata fields to: node_modules/signed-varint/node_modules/varint/package.json
Adding metadata fields to: node_modules/simple-concat/package.json
Adding metadata fields to: node_modules/simple-get/package.json
Adding metadata fields to: node_modules/simple-sha1/package.json
Adding metadata fields to: node_modules/siphash24/package.json
Adding metadata fields to: node_modules/slice-ansi/package.json
Adding metadata fields to: node_modules/snapdragon/package.json
Adding metadata fields to: node_modules/snapdragon/node_modules/debug/package.json
Adding metadata fields to: node_modules/snapdragon/node_modules/define-property/package.json
Adding metadata fields to: node_modules/snapdragon/node_modules/extend-shallow/package.json
Adding metadata fields to: node_modules/snapdragon/node_modules/is-accessor-descriptor/package.json
Adding metadata fields to: node_modules/snapdragon/node_modules/is-accessor-descriptor/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/snapdragon/node_modules/is-data-descriptor/package.json
Adding metadata fields to: node_modules/snapdragon/node_modules/is-data-descriptor/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/snapdragon/node_modules/is-descriptor/package.json
Adding metadata fields to: node_modules/snapdragon/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/snapdragon/node_modules/ms/package.json
Adding metadata fields to: node_modules/snapdragon-node/package.json
Adding metadata fields to: node_modules/snapdragon-node/node_modules/define-property/package.json
Adding metadata fields to: node_modules/snapdragon-util/package.json
Adding metadata fields to: node_modules/snapdragon-util/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/sodium-javascript/package.json
Adding metadata fields to: node_modules/sodium-native/package.json
Adding metadata fields to: node_modules/sodium-native/node_modules/node-gyp-build/package.json
Adding metadata fields to: node_modules/sodium-universal/package.json
Adding metadata fields to: node_modules/sorted-array-functions/package.json
Adding metadata fields to: node_modules/sorted-indexof/package.json
Adding metadata fields to: node_modules/source-map/package.json
Adding metadata fields to: node_modules/source-map-resolve/package.json
Adding metadata fields to: node_modules/source-map-url/package.json
Adding metadata fields to: node_modules/sparse-bitfield/package.json
Adding metadata fields to: node_modules/speedometer/package.json
Adding metadata fields to: node_modules/split-string/package.json
Adding metadata fields to: node_modules/sshpk/package.json
Adding metadata fields to: node_modules/stack-trace/package.json
Adding metadata fields to: node_modules/static-extend/package.json
Adding metadata fields to: node_modules/static-extend/node_modules/define-property/package.json
Adding metadata fields to: node_modules/static-extend/node_modules/is-accessor-descriptor/package.json
Adding metadata fields to: node_modules/static-extend/node_modules/is-accessor-descriptor/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/static-extend/node_modules/is-data-descriptor/package.json
Adding metadata fields to: node_modules/static-extend/node_modules/is-data-descriptor/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/static-extend/node_modules/is-descriptor/package.json
Adding metadata fields to: node_modules/static-extend/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/stream-collector/package.json
Adding metadata fields to: node_modules/stream-each/package.json
Adding metadata fields to: node_modules/stream-parser/package.json
Adding metadata fields to: node_modules/stream-parser/node_modules/debug/package.json
Adding metadata fields to: node_modules/stream-parser/node_modules/ms/package.json
Adding metadata fields to: node_modules/stream-shift/package.json
Adding metadata fields to: node_modules/string-width/package.json
Adding metadata fields to: node_modules/string_decoder/package.json
Adding metadata fields to: node_modules/string_decoder/node_modules/safe-buffer/package.json
Adding metadata fields to: node_modules/strip-ansi/package.json
Adding metadata fields to: node_modules/strip-eof/package.json
Adding metadata fields to: node_modules/strip-json-comments/package.json
Adding metadata fields to: node_modules/subcommand/package.json
Adding metadata fields to: node_modules/supports-color/package.json
Adding metadata fields to: node_modules/term-size/package.json
Adding metadata fields to: node_modules/throttle/package.json
Adding metadata fields to: node_modules/thunky/package.json
Adding metadata fields to: node_modules/timed-out/package.json
Adding metadata fields to: node_modules/timeout-refresh/package.json
Adding metadata fields to: node_modules/to-buffer/package.json
Adding metadata fields to: node_modules/to-object-path/package.json
Adding metadata fields to: node_modules/to-object-path/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/to-regex/package.json
Adding metadata fields to: node_modules/to-regex-range/package.json
Adding metadata fields to: node_modules/toiletdb/package.json
Adding metadata fields to: node_modules/toiletdb/node_modules/debug/package.json
Adding metadata fields to: node_modules/toiletdb/node_modules/ms/package.json
Adding metadata fields to: node_modules/tough-cookie/package.json
Adding metadata fields to: node_modules/tough-cookie/node_modules/punycode/package.json
Adding metadata fields to: node_modules/township-client/package.json
Adding metadata fields to: node_modules/township-client/node_modules/is-number/package.json
Adding metadata fields to: node_modules/township-client/node_modules/kind-of/package.json
Adding metadata fields to: node_modules/ttl/package.json
Adding metadata fields to: node_modules/tunnel-agent/package.json
Adding metadata fields to: node_modules/tweetnacl/package.json
Adding metadata fields to: node_modules/typedarray/package.json
Adding metadata fields to: node_modules/uint64be/package.json
Adding metadata fields to: node_modules/union-value/package.json
Adding metadata fields to: node_modules/unique-string/package.json
Adding metadata fields to: node_modules/unixify/package.json
Adding metadata fields to: node_modules/unordered-array-remove/package.json
Adding metadata fields to: node_modules/unordered-set/package.json
Adding metadata fields to: node_modules/unset-value/package.json
Adding metadata fields to: node_modules/unset-value/node_modules/has-value/package.json
Adding metadata fields to: node_modules/unset-value/node_modules/has-value/node_modules/isobject/package.json
Adding metadata fields to: node_modules/unset-value/node_modules/has-values/package.json
Adding metadata fields to: node_modules/untildify/package.json
Adding metadata fields to: node_modules/unzip-response/package.json
Adding metadata fields to: node_modules/update-notifier/package.json
Adding metadata fields to: node_modules/uri-js/package.json
Adding metadata fields to: node_modules/urix/package.json
Adding metadata fields to: node_modules/url-parse-lax/package.json
Adding metadata fields to: node_modules/use/package.json
Adding metadata fields to: node_modules/util-deprecate/package.json
Adding metadata fields to: node_modules/utile/package.json
Adding metadata fields to: node_modules/utp-native/package.json
Adding metadata fields to: node_modules/utp-native/node_modules/node-gyp-build/package.json
Adding metadata fields to: node_modules/utp-native/node_modules/readable-stream/package.json
Adding metadata fields to: node_modules/utp-native/node_modules/unordered-set/package.json
Adding metadata fields to: node_modules/uuid/package.json
Adding metadata fields to: node_modules/varint/package.json
Adding metadata fields to: node_modules/verror/package.json
Adding metadata fields to: node_modules/which/package.json
Adding metadata fields to: node_modules/widest-line/package.json
Adding metadata fields to: node_modules/winston/package.json
Adding metadata fields to: node_modules/winston/node_modules/async/package.json
Adding metadata fields to: node_modules/winston/node_modules/colors/package.json
Adding metadata fields to: node_modules/winston/node_modules/pkginfo/package.json
Adding metadata fields to: node_modules/wrappy/package.json
Adding metadata fields to: node_modules/write-file-atomic/package.json
Adding metadata fields to: node_modules/xdg-basedir/package.json
Adding metadata fields to: node_modules/xhr/package.json
Adding metadata fields to: node_modules/xsalsa20/package.json
Adding metadata fields to: node_modules/xtend/package.json
Adding metadata fields to: node_modules/yallist/package.json

><EMAIL_ADDRESS>install /nix/store/9pc5m1p4bc1jaid9m76pf3wqx09wq2d2-node_dat-13.13.1/lib/node_modules/dat/node_modules/discovery-swarm/node_modules/utp-native
> node-gyp-build

No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.

make: Entering directory '/nix/store/9pc5m1p4bc1jaid9m76pf3wqx09wq2d2-node_dat-13.13.1/lib/node_modules/dat/node_modules/discovery-swarm/node_modules/utp-native/build'
  CXX(target) Release/obj.target/libutp/deps/libutp/utp_internal.o
../deps/libutp/utp_internal.cpp:1970:34: warning: comparison of integers of different signs: 'int' and 'uint32' (aka 'unsigned int') [-Wsign-compare]
                if (conn->mtu_probe_seq && seq == conn->mtu_probe_seq) {
                                           ~~~ ^  ~~~~~~~~~~~~~~~~~~~
../deps/libutp/utp_internal.cpp:156:19: warning: unused variable 'flagnames' [-Wunused-const-variable]
static const cstr flagnames[] = {
                  ^
../deps/libutp/utp_internal.cpp:174:19: warning: unused variable 'statenames' [-Wunused-const-variable]
static const cstr statenames[] = {
                  ^
3 warnings generated.
  CXX(target) Release/obj.target/libutp/deps/libutp/utp_utils.o
  CXX(target) Release/obj.target/libutp/deps/libutp/utp_hash.o
  CXX(target) Release/obj.target/libutp/deps/libutp/utp_callbacks.o
  CXX(target) Release/obj.target/libutp/deps/libutp/utp_api.o
  CXX(target) Release/obj.target/libutp/deps/libutp/utp_packedsockaddr.o
  LIBTOOL-STATIC Release/utp.a
  CXX(target) Release/obj.target/utp/src/utp_uv.o
../src/utp_uv.cc:219:1: warning: unused function 'on_utp_schedule_ack' [-Wunused-function]
on_utp_schedule_ack (utp_callback_arguments *a) {
^
1 warning generated.
  CXX(target) Release/obj.target/utp/src/socket_wrap.o
../src/socket_wrap.cc:69:23: warning: 'Call' is deprecated [-Wdeprecated-declarations]
      this->on_drain->Call(ctx, 0, NULL);
                      ^
../../../../nan/nan.h:1717:3: note: 'Call' has been explicitly marked deprecated here
  NAN_DEPRECATED inline v8::Local<v8::Value>
  ^
../../../../nan/nan.h:104:40: note: expanded from macro 'NAN_DEPRECATED'
# define NAN_DEPRECATED __attribute__((deprecated))
                                       ^
../src/socket_wrap.cc:99:45: error: too few arguments to function call, single argument 'context' was not specified
  Local<Object> context = info[0]->ToObject();
                          ~~~~~~~~~~~~~~~~~ ^
/nix/store/9vxbybq7vhkl95389yp29xfd4wiw39ms-node-sources/deps/v8/include/v8.h:2754:3: note: 'ToObject' declared here
  V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject(
  ^
/nix/store/9vxbybq7vhkl95389yp29xfd4wiw39ms-node-sources/deps/v8/include/v8config.h:419:31: note: expanded from macro 'V8_WARN_UNUSED_RESULT'
#define V8_WARN_UNUSED_RESULT __attribute__((warn_unused_result))
                              ^
../src/socket_wrap.cc:113:43: error: too few arguments to function call, single argument 'context' was not specified
  Local<Value> buffer = info[0]->ToObject();
                        ~~~~~~~~~~~~~~~~~ ^
/nix/store/9vxbybq7vhkl95389yp29xfd4wiw39ms-node-sources/deps/v8/include/v8.h:2754:3: note: 'ToObject' declared here
  V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject(
  ^
/nix/store/9vxbybq7vhkl95389yp29xfd4wiw39ms-node-sources/deps/v8/include/v8config.h:419:31: note: expanded from macro 'V8_WARN_UNUSED_RESULT'
#define V8_WARN_UNUSED_RESULT __attribute__((warn_unused_result))
                              ^
../src/socket_wrap.cc:141:44: error: no matching member function for call to 'Get'
    Local<Value> buffer = Nan::Get(writes->Get(i)->ToObject(), chunk).ToLocalChecked();
                                   ~~~~~~~~^~~
/nix/store/9vxbybq7vhkl95389yp29xfd4wiw39ms-node-sources/deps/v8/include/v8.h:3594:43: note: candidate function not viable: requires 2 arguments, but 1 was provided
  V8_WARN_UNUSED_RESULT MaybeLocal<Value> Get(Local<Context> context,
                                          ^
/nix/store/9vxbybq7vhkl95389yp29xfd4wiw39ms-node-sources/deps/v8/include/v8.h:3597:43: note: candidate function not viable: requires 2 arguments, but 1 was provided
  V8_WARN_UNUSED_RESULT MaybeLocal<Value> Get(Local<Context> context,
                                          ^
../src/socket_wrap.cc:243:62: error: too few arguments to function call, single argument 'context' was not specified
  instance = Nan::NewInstance(constructorHandle->GetFunction()).ToLocalChecked();
                              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
/nix/store/9vxbybq7vhkl95389yp29xfd4wiw39ms-node-sources/deps/v8/include/v8.h:6283:3: note: 'GetFunction' declared here
  V8_WARN_UNUSED_RESULT MaybeLocal<Function> GetFunction(
  ^
/nix/store/9vxbybq7vhkl95389yp29xfd4wiw39ms-node-sources/deps/v8/include/v8config.h:419:31: note: expanded from macro 'V8_WARN_UNUSED_RESULT'
#define V8_WARN_UNUSED_RESULT __attribute__((warn_unused_result))
                              ^
1 warning and 4 errors generated.
make: *** [utp.target.mk:139: Release/obj.target/utp/src/socket_wrap.o] Error 1
make: Leaving directory '/nix/store/9pc5m1p4bc1jaid9m76pf3wqx09wq2d2-node_dat-13.13.1/lib/node_modules/dat/node_modules/discovery-swarm/node_modules/utp-native/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:210:5)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
gyp ERR! System Darwin 18.7.0
gyp ERR! command "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/bin/node" "/nix/store/859xy9v44my7l66cc4asmd5fy3dkpz2s-nodejs-13.2.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /nix/store/9pc5m1p4bc1jaid9m76pf3wqx09wq2d2-node_dat-13.13.1/lib/node_modules/dat/node_modules/discovery-swarm/node_modules/utp-native
gyp ERR! node -v v13.2.0
gyp ERR! node-gyp -v v5.0.5
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: `node-gyp-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!

Apparently dat was already in nixpkgs in node-packages-v10.json,but it does not compile


Create local debugging Auth middleware

Currently we only support debugging with ORY. This means you have to have access to our ory account and set up the proxy, It would be better if locally you can test without ory middleware.
To achieve this, the API service should have a new flag called DEBUGGING that can be set to true or false.
When in debugging mode there should be a new middleware and a new interface for authentication middleware called AuthMiddleware that should have a function called SessionMiddleware. The new debugging auth should effectively be a no-op. By default with no flag the ory auth should be enabled.
This is how a rout gets auth enforced https://github.com/null-channel/eddington/blob/a3c61d8ea180502d7252b62b5525d38f612fea28/api/main.go#L87C38-L87C47
This is where the middleware is created: https://github.com/null-channel/eddington/blob/a3c61d8ea180502d7252b62b5525d38f612fea28/api/main.go#L47C6-L47C6

i'll take this one.


fix: use non-deprecated getLatestBlockhash method

This method has been removed in Agave 2.0. Bumped the @solana/web3.js requirement to the oldest version that supports getLatestBlockhash.

Related: didn't test this at all. Also pretty sure that singleGossip and max commitments have been deprecated too.


eth_getFilterLogs doesn't work

I'm getting this when attempting to call eth_getFilterLogs through the extension:
MetaMask - RPC Error: results is not defined

I believe this is due to a missing const here: https://github.com/MetaMask/eth-json-rpc-filters/blob/5cbea3037b0655aa2c188d85b8ffe559a263dc0d/index.js?rgh-link-date=2022-12-14T22%3A35%3A20Z#L114

Should be fixed by #84


Adapt report views to show information about applied filters

Version used

AET 2.1.6

Context of the issue/feature
Please modify views of Status Codes, W3C and Accessibility reports to show information about filters applied to the tested url. View for JS Errors was already modified (directive filterInformation from code related to JS Errors should be easily reusable in those cases too).
Think about the best way to present data to the user (initial thought was to display everything in one table and add additional column with filter information - just like on JS Errors page).
Think over the data structure that is sent to the reporting app (collector, comparator, results)

It would be nice if some details regarding issues that have been filtered out would be presented. As for JS what I can see now is just the total number of JS Error filters with no details.


Inquiry about functionality

Hello, I've tried it and it's fantastic! Is it possible to use this library to trigger SF2 with my MIDI keyboard without Node.js?

Hi, I'm glad you like my project : )
Both the demo (spessasus.github.io/SpessaSynth) and the local (node.js) allow you to use your MIDI devices. You need to allow MIDI device access in the browser (it should automatically prompt you when you first load the website) and then open Spessasynth settings and select your MIDI keyboard as the input. If it doesn't show up, restart your browser. Once you've select your keyboard, spessasynth should respond to it.

Thank you for your very quick response! I tried your app and it works! What I really want is to use SpessaSynth without having to use Node.js; I would be interested in using SF2 with my MIDI keyboard directly. Congratulations on your work

I'm not sure if I understood. Spessasynth does not use Node.js. it only serves as a simple http server for the local version. It could be any other http server like XAMPP for example.
If you want to use this without installing Node.js, you can simply visit the demo website and you can use the MIDI keyboard from there as I described in the previous response. Simply upload your SF2 and connect the keyboard and you're good to go!
However if you meant using the SpessaSynth JavaScript library via your own code, you need to obtain the MIDI input via Web MIDI API and then simply connect the onmessage event to the .send() method of the Spessasynth, as described in the wiki.
I hope this helps.

Closing due to inactivity.


Returning a promise from requestListener so we know when processing is done

Description
Hooking bolt into next.js and got it working with:
import { App, HTTPReceiver, GenericMessageEvent } from '@slack/bolt'
import { NextApiRequest, NextApiResponse } from 'next';

const receiver = new HTTPReceiver({
  endpoints: ['/api/slack/events'],
  signingSecret: process.env.SIGNING_SECRET,
  processBeforeResponse: true
})

// Initializes your app with your bot token and the AWS Lambda ready receiver
const app = new App({
  token: process.env.ACCESS_TOKEN,
  receiver,
  ignoreSelf: true
});

app.message('hi', async ({ message, say }) => {
  const msg = message as GenericMessageEvent
  await say(`:wave<EMAIL_ADDRESS>})

export default receiver.requestListener;

export const config = {
  api: {
    bodyParser: false,
  }
}

Next.js will complain that:
API resolved without sending a response for /api/slack/events, this may result in stalled requests.

From here: https://github.com/vercel/next.js/issues/10439#issuecomment-583214126 we need to return a promise so it knows when to kill the function on it's end.
Instead of wrapping in an async closure, can we just return a promise?
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[x] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

This is an interesting idea. Returning a Promise would deviate from the function signature of the standard Node request listener. I'm not opposed to adjusting that signature a bit if it adds value and doesn't cause any issues.
Here's the issue I think it might cause: If a Promise is returned and the caller does nothing to handle it (no await, no .then()/.catch()), and the Promise rejects, then we could potentially crash the program due to an UnhandledPromiseRejectionWarning. Some of us may have seen this related warning in our consoles.

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.

Aside from that issue, I think it would technically be a breaking change. Currently, when the HTTPReceiver defers handling a specific request, it synchronously throws. Calling code would need to be adjusted to handle promise rejects (also known as async throws).
These problems both feel a little theoretical at this point, esp since this release shipped so recently. I'm open to your thoughts on it.
Meanwhile, I'm going to go create a little toy Next.js app to see if I have any bright ideas/suggestions. I'll report back.

This is an interesting idea. Returning a Promise would deviate from the function signature of the standard Node request listener. I'm not opposed to adjusting that signature a bit if it adds value and doesn't cause any issues.
Here's the issue I think it might cause: If a Promise is returned and the caller does nothing to handle it (no await, no .then()/.catch()), and the Promise rejects, then we could potentially crash the program due to an UnhandledPromiseRejectionWarning. Some of us may have seen this related warning in our consoles.

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.

Aside from that issue, I think it would technically be a breaking change. Currently, when the HTTPReceiver defers handling a specific request, it synchronously throws. Calling code would need to be adjusted to handle promise rejects (also known as async throws).
These problems both feel a little theoretical at this point, esp since this release shipped so recently. I'm open to your thoughts on it.
Meanwhile, I'm going to go create a little toy Next.js app to see if I have any bright ideas/suggestions. I'll report back.

I got a Next.js app working without the warning. Got it deployed to Vercel as well.
I split things up a bit so that the pages/api/slack/[...all].js file just sets up the HTTP receiver.
Then in lib/bolt.js i did all the normal Bolt things.
What do you think?

I got a Next.js app working without the warning. Got it deployed to Vercel as well.
I split things up a bit so that the pages/api/slack/[...all].js file just sets up the HTTP receiver.
Then in lib/bolt.js i did all the normal Bolt things.
What do you think?

Oh! I didn’t know about the externalResolver option.
That looks like it does it
On Thu, Jan 14, 2021 at 2:52 AM Ankur Oberoi<EMAIL_ADDRESS>wrote:

I got a Next.js app working without the warning. Got it deployed to Vercel
as well.
I split things up a bit so that the pages/api/slack/[...all].js
https://github.com/aoberoi/nextjs-examples-with-bolt/blob/2c9491537337a376b7162c1db9767963ebc64565/pages/api/slack/[...all].js
file just sets up the HTTP receiver.
Then in lib/bolt.js
https://github.com/aoberoi/nextjs-examples-with-bolt/blob/main/lib/bolt.js
i did all the normal Bolt things.
What do you think?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/slackapi/bolt-js/issues/755#issuecomment-760118723,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFMAUMNZXXKB7ICSBZQXOLSZ3EIHANCNFSM4WBZ2XRA
.

Oh! I didn’t know about the externalResolver option.
That looks like it does it
On Thu, Jan 14, 2021 at 2:52 AM Ankur Oberoi<EMAIL_ADDRESS>wrote:

I got a Next.js app working without the warning. Got it deployed to Vercel
as well.
I split things up a bit so that the pages/api/slack/[...all].js
https://github.com/aoberoi/nextjs-examples-with-bolt/blob/2c9491537337a376b7162c1db9767963ebc64565/pages/api/slack/[...all].js
file just sets up the HTTP receiver.
Then in lib/bolt.js
https://github.com/aoberoi/nextjs-examples-with-bolt/blob/main/lib/bolt.js
i did all the normal Bolt things.
What do you think?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/slackapi/bolt-js/issues/755#issuecomment-760118723,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFMAUMNZXXKB7ICSBZQXOLSZ3EIHANCNFSM4WBZ2XRA
.

If I understand the above discussion, it seems we can close this issue now. I will close this after waiting for a few more days.


Classification of Cyber Bulling using NLP

Pull Request for DL-Simplified 💡
Issue Title :

Info about the related issue (Aim of the project) :
Name:
GitHub ID:
Email ID:
Idenitfy yourself: (Mention in which program you are contributing in. Eg. For a JWOC 2022 participant it's, JWOC Participant)

Closes: #issue number that will be closed through this PR
Describe the add-ons or changes you've made 📃
Give a clear description of what have you added or modifications made
Type of change ☑
What sort of change have you made:

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Code style update (formatting, local variables)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

How Has This Been Tested? ⚙
Describe how it has been tested
Describe how have you verified the changes made
Checklist: ☑

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added things that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

Pull Request for DL-Simplified 💡
Issue Title :

Info about the related issue (Aim of the project) :
Name:
GitHub ID:
Email ID:
Idenitfy yourself: (Mention in which program you are contributing in. Eg. For a JWOC 2022 participant it's, JWOC Participant)

Closes: #issue number that will be closed through this PR
Describe the add-ons or changes you've made 📃
Give a clear description of what have you added or modifications made
Type of change ☑
What sort of change have you made:

[x]  Bug fix (non-breaking change which fixes an issue)
[x]  New feature (non-breaking change which adds functionality)
[x]  Code style update (formatting, local variables)
[x]  Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x]  This change requires a documentation update

How Has This Been Tested? ⚙
Describe how it has been tested Describe how have you verified the changes made
Checklist: ☑

[x]  My code follows the guidelines of this project.
[x]  I have performed a self-review of my own code.
[x]  I have commented my code, particularly wherever it was hard to understand.
[x]  I have made corresponding changes to the documentation.
[x]  My changes generate no new warnings.
[x]  I have added things that prove my fix is effective or that my feature works.
[x]  Any dependent changes have been merged and published in downstream modules.

Please fill up the details while submitting your PR.

Created a model using XlNet

Project structure should be followed.
Need to do a certain amount of EDA.
One model implementation will not work, you need to implement atleast 2-3 models for this project.

@UtkarshTrivedi2934


not really a issue just a question

do you know any grind craft fan games bc I cant find any

Well, except for my own I don't really know about any.
That's kinda why i made the tool ig, to at least make it easier for anyone that would want to do it


Update aws-sdk package to v3

AWS have notified that they will put aws-sdk into maintenance mode in September 2024 and stop supporting it completely in September 2025.
It would be great if we could update this plugin to use version 3 of the AWS libraries.
https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-javascript-v2/

Thanks for reporting! This has been a lingering doom for a bit and definitely something we should get on top of.

This should actually be resolved now as of https://github.com/segmentio/segment-backstage-plugins/pull/10! Sorry for not following up sooner here


Roll engine 540fc977bb6b..09adb1876c57 (2 commits)

git@github.com:flutter/engine.git/compare/540fc977bb6b...09adb1876c57
git log 540fc977bb6b..09adb1876c57 --no-merges --oneline
2019-10-15<EMAIL_ADDRESS>Roll src/third_party/skia 858cf233ef71..55f9cba6e2e7 (3 commits) (flutter/engine#13133)
2019-10-15<EMAIL_ADDRESS>Roll src/third_party/dart 70a7ef3f58..50f7ae9c5d (18 commits)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/5135057005576192 , https://cirrus-ci.com/task/6014666307796992

Commit queue failed; closing this roll.


--no-cassandra errors could not resolve any of the provided Cassandra contact points

I am getting following error while running pongo. All the tests run, pass and the error appears after the test run has completed with results.
Command
KONG_VERSION=2.8.1 POSTGRES=13 pongo run --no-cassandra

ERROR:-
my-pugin: (access) [#cassandra] lazy_setup
./spec/helpers.lua:392: could not resolve any of the provided Cassandra contact points (cassandra_contact_points = 'pongo-19daec31-cassandra.pongo-19daec31')
ERROR: 1

That is because you start the environment without Cassandra when passing --no-cassandra, yet in your plugins tests you still run the tests against Cassandra, and hence it will not be able to connect.
looks like you're using the plugin template. See this recent commit on disabling cassandra from the tests: https://github.com/Kong/kong-plugin/commit/05d55447ee4b94dedf7a109ece8da5114dc1a44e#diff-f1a7beab0ea3822e602403b6560d02dbbd14359ed5c5efaf9ec0d2983d173bd2

Yes removing the Cassandra part from helpers.all_strategies() solved the issue.


{communication} Fix Communication Rooms Readme Issue

Description
Update Readme to fix issue https://github.com/Azure/azure-sdk-for-python/issues/30875.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


project reorg and addition of schedule page

new schedule page has not been added to nav

This is all good, as you said we can add schedule to nav. Or just incorporate it into a section on the home page, tall pages are all the rage these days


wallet: Remove unused AskPassphraseDialog::Decrypt

Grabbed from #42 with an additional commit.
Fix #1.

Concept ACK.

Please remove bool encrypted as well

Updated f886a20b02094d657ddb3d792d561d50f2107f07 -> 4146a31ccbb012ff552f303113979b48c086532b (pr109.01 -> pr109.02, diff):

addressed @MarcoFalke's comment:

Please remove bool encrypted as well

ACK 4146a31ccbb012ff552f303113979b48c086532b


tests: fix failures from bump of transitive deps to urllib3 2.X

remove remove test_function_import_without_return_type_wrong_code

The entire logic of the test was based on scenario that server returns response of HTTP 204 No Content (which ends with HTTP Header) with some content in HTTP Body, which is breaking the HTTP protocol logic itself.
The Responses package generated such weird simulated response and was parsed with urllib 1.X in previous versions of Requests, but now, with being compatible with urllib3 2.x, breaking changes were introduced within this transitive dependency.
On the requests side, the bump to same urllib3 2.x means test failures with error:
requests.exceptions.ChunkedEncodingError: ('Connection broken: IncompleteRead(10 bytes read, -10 more expected)', IncompleteRead(10 bytes read, -10 more expected))

test_update_entity

Same rationale, removed invalid body for expected HTTP 204 simulated response
Additional info:
getsentry/responses#636
https://urllib3.readthedocs.io/en/latest/v2-migration-guide.html
RFC 2616  - HTTP 1.1 - 10.2.5 - 204 No Content
https://datatracker.ietf.org/doc/html/rfc2616#section-10.2.5

closes #250


[Compat/Integration Suggestion] Inverted Beds

I really like the concept of this mod, and I'm a making a modpack inspired by Eternal Descent. That being said I would like to help, I saw a mod by the name of Inverted Beds does just that by introducing inverted beds that in the Overworld lets you sleep during the day to the night it has a MIT license and is open source if this mechanic could be introduced by modifying vanilla beds (through mixins to prevent making new block entities) and to then allow beds to placed upside in the Ceilands to sleep during the night and the right-side up variant would block up in the Ceilands. Or possible integration with the mod itself, regardless it is just a suggestion and I want to say thank you and keep up the good work, this dimension stands out already.

I will keep that in mind, thank you for suggesting!
 There's still a lot of work needing to be done first.


RFC: Do not implement non-nil postfix ! operator.

This is a meta-RFC. I'd like to propose to remove the postfix ! operator from the language.
I'd like to argue that this operator will eventually become useless and can only be used incorrectly at some point in the future, and that there are likely ways for them to be sound without having to reach for the ! hammer.
With that, I present these counterarguments:
Shortcoming #1: Refinements does not apply to the block after return/break/continue.
if not x or not y then return end
-- both x and y are truthy

This will be solved by implementing control flow analysis where it'd apply the inverse of the condition leading up to the control transfer statement to the rest of the scope.
Shortcoming #2: Type checker is not aware of the actual state of various locations.
type Foo = { x: { y: number }? }?
local foo: Foo = { x = { y = 5 } }
print(foo.x.y) -- prints 5 at runtime, type checker warns on this

This will be solved by implementing type states where it would inspect the initialization sites as well as assignments to know their actual states. That is, rather than trusting the type annotation Foo as the state which gets us far enough, we'd start seeing these type annotations as a subtype constraint for the location foo.

If there are other use cases not covered here, we should talk about that and see if there exists an alternative direction that can solve these use cases soundly.

While improvements to control flow analysis would eliminate a number of the cases where I use a type assertion that could be replaced with a non-nil postfix, there is one use case I can think of for this:
local success, err = pcall(function()
    error("Some message")
end)
if not success then
    print(err!)
end

This use case could be eliminated if pcall had a type of (f: (A...) -> (R...), ...: A...)) -> (true, R...) | (false, string) and the control flow analysis were improved (not sure if this is already the case on this repository, since I'm only using Roblox Studio for my luau code).
So most of my use cases for this is where typings are not precise enough, or nilability is dependent on something that can't be expressed in the current type system.

For your case control flow analysis is not what we need here. For that, we need union type packs, which doesn't exist in the type inference engine yet. We also need the ability to tag a group of locals (success, err) points to this type pack (true, R...) | (false, string).  For soundness, we would also need the ability to break any lvalue from this group if it has been assigned to or used in some way that might cause its value to be changed.
The ! operator will not be helpful for this case because of a different reason: the returns of pcall is just boolean because the function passed into it does not return any values. This produces a warning if you tried to assign the result of the call to two locals. I've made a change to the type of pcall so err will have the type any now, which renders the ! useless.


Is textDocument/inlayHint supported?

I wonder if there is a support for textDocument/inlayHint. It looks like there is because I found this PR:  #465
However, when I try to request data I get:
Method not found: textDocument/inlayHint

Tracked in Apple’s issue tracker as rdar://123555008

In VSCode if you set the setting swift.sourcekit-lsp.server.trace to verbose you can see all the communication between the VSCode LSP client and SourceKit-LSP in the SourceKit-LSP output pane. Useful for debugging requests. Search for InlayHint and you should see the requests.


Pin assignments SPIS nrf52

Is your enhancement proposal related to a problem? Please describe.
A clear and concise description of what the problem is.
I'd like to use SPIS on the Particle Argon but I can't figure out the csn-pin to use. I believe boards > arm > particle_argon > dts > mesh_feather_spi_spi1.dtsi references the nrf52 pin assignments. This leads me to believe I need to look at nordic, however I'm struggling to see the relation between the dtsi file and nordic's documentation.
Could someone who knows something help with understanding the mapping of gpio1 15 -> 47, gpio1 13 -> 46, gpio1 14 -> 45 and my problem which is gpio0 31 -> ?, and how they got there?
&spi1 {
	compatible = "nordic,nrf-spis";
	status = "okay";
	sck-pin = <47>;
	mosi-pin = <45>;
	miso-pin = <46>;
        // cs-gpios = < &gpio0 31 GPIO_ACTIVE_LOW>;
	csn-pin = <?>;
	def-char = <0x00>;

	bt-hci@0 {
		compatible = "zephyr,bt-hci-spi-slave";
		reg = <0>;
		irq-gpios = <&gpio0 2 (GPIO_ACTIVE_HIGH | GPIO_PULL_DOWN)>;
	};
};

Describe the solution you'd like
A clear and concise description of what you want to happen.
Documentation/mesh_feather_spis_spi1.dtsi example

I'm unsure if this is correct but it seems like a pretty good guess. Since a GPIO bus goes from [0 ... 31] and gpio1 is the "next" bus the mapping is gpio1 14 = 31 + 14 = 45. So the pins are referencing the GPIO number plus whatever bus they are on. Hate when things seem obvious after the fact. I can't find documentation on this so I assume this is just a known convention I haven't come across before.


feat: make operations callable

Hey again :)
In my project I have a scenario where I'd like to mutate some values inside of a web worker. I can do this using the current implementation - however I need to create a QueryClient inside of my web worker and having the QueryClient there feels useless since it doesn't provide any benefits in my case. I was wondering how you'd feel about making it possible to make the fetch request by calling the operation itself e.g
qraft.pet.getPetById({
    path: { petId },
 })

I've written a first draft of this but wanted to get your opinion before continuing incase this isn't something you'd like to add.

@raducal, It's good to hear that you're trying to use Qraft even for things like using it on the Web Worker side.
Some thoughts on the advantages of using qraft.<operation>.fetchQuer and QueryClient: retry for requests is a useful thing, APIs, especially public ones, are often unstable. Many problems with client application stability can be solved by just request retry. QueryClient simplifies this with built-in mechanisms.
However, I understand that for a Web Worker QueryClient is overkill.
Back in the early days of implementing Qraft, I took care of a case like this - where a QueryClient is not needed:

qraft.<service>.<operation>.queryFn(...)
qraft.<service>.<operation>.mutationFn(...)

These methods are not documented, as I wasn't sure if anyone would need them. Also, their API seems complicated to me (maybe it will change). It is clear now that methods are needed and their support needs to be improved.

@raducal, yes, you are correct that making <operation> as callable is a tempting idea. I'll think of a way to do it.
Thanks for your feedback and ideas! It helps to know what direction to take Qraft in.

@raducal, that's awesome that you shared. Of course, the idea of making a generator and a client is what Qraft was intended for. As an MVP, I focused on the support of TanStack as it has the most advanced functionality in my opinion. Now, I will be splitting the packages into smaller pieces, to be able to create an ecosystem that can include SWR and maybe RTK support. Ideally, it would not be limited to React.

@raducal, can you describe your use case with Qraft? Do you use it for the React? Are you using TanStack/SWR?
I'm wondering if I should prioritize Qraft features like no TanStack dependencies at all (Web Workers/Service Workers/Whatever Lightweight), for example?

@raducal, just for interest, do you see any advantages of SWR compared to TanStack. I'm interested in the experience of developers who play for both sides.

@raducal, a very clear feedback. Just to understand, what kind of projects are you thinking of using Qraft for?
For example, Monite is integrating Qraft into their Fintech product. I'm curious, what projects are you working on?

The idea is quite clear, but unfortunately, TanStack does not have the functionality to implement it.
It seems to me that in this case, it will be more reliable to use your own implementation of the SSE listener and write data to the Query Client using the setQueryData Qraft's methods.


Game can be started mutiple times

I already have a small bugfix that solves the problem without changing much. I will submit as PR
How to reproduce it:

Result:

Yes i also stumbled across this issue but did not have time to look into this further - thank you for fixing this!!

What i also just realized is that we could disable user input during the 3 second wait time completely.

What i also just realized is that we could disable user input during the 3 second wait time completely.

I think this might even be the better solution.


Expectation value of a Hamiltonian

Hi all,
I am working on a new algorithm that is to be implementable in an actual experiment. In order to get the feeling about what is going on, I would need to compute the expectation value for a given Hamiltonian with shots and not with the exact wavefunction of the state. In other words, it would be like measuring in the real physical world. Is it possible?
Thank you all

Do you have references about this feature?

I do not have any, but I don't think it is necessary.
Let us think in the Z hamiltonian for one qubit. We can perform the state * hamiltonian * state matrix multiplication and obtain a number. But we could also measure with shots the probability of obtaining 0 (p0) and 1 (p1) and say Z = p0 - p1
Since we measure in the Z basis, it would be immediate in this case. For the X and Y basis, I would apply a Hadamard gate or the equivalent in Y to measure in another basis

Thanks for opening this, it is certainly not possible to do directly with Qibo. For now, I will try to find a temporary solution using custom code and will write here if I come up with something.
It would be great to add it as a feature. I agree that a reference is not needed, I am just not sure how easy it would be to implement this with the current representation we have for Hamiltonians, which is mainly based on numpy arrays. We may need redesign this a bit.

I found a relatively simple way to do this using our existing TrotterHamiltonian functionality. It may be considered cheating because the state vector is used in the calculation, however it may be possible to use it to emulate the "measurement noise" in the expectation value. I am not 100% sure if it is a good approach though. The idea is the following:
# construct the circuit that produces the measurements in the Z basis
c = models.Circuit(nqubits)
c.add(...) # all your gates
# measure all qubits in the Z basis
c.add(gates.M(*range(nqubits)))
# execute
result = c(nshots=nshots)
# get the decimal samples as np.array
measurements = result.samples(binary=False).numpy()
# get the final state vector as np.array
# note this is the state before the measurement (not collapsed)
final_state = c.final_state.numpy()

# construct your Hamiltonian as `TrotterHamiltonian`, eg.
ham = hamiltonians.TFIM(nqubits, trotter=True)

# calculate the EV using measurements
ev = 0
psiloc0 = final_state[measurements]
# add Hamiltonian terms one-by-one
for term in htrotter.terms():
    psiloc = term(np.copy(final_state)).numpy()[measurements]
    # np.copy is important here, otherwise the custom operator will alter the state
    # and the remaining terms will be wrong!
    ev += (psiloc / psiloc0).mean()

# (optional) calculate exact EV to compare
exact_ev = ham.expectation(final_state)

If you try this you will see that ev converges to exact_ev as you increase nshots which is what is expected. I used TFIM in this example but you can create your own Hamiltonian as TrotterHamiltonians relatively easily using sympy symbols (see our example).
Perhaps it is not exactly what we should implement in Qibo but let me know if it helps.

In order to make clearer what the code in the previous post does, the idea is based in the following equation for the expectation value of an arbitrary operator A:

Note that while \sum _\sigma denotes a sum over all possible bit-strings/spin configurations, the last sum is a sum over samples that follow the probability distribution defined by the wave function. This is the typical averaging approach used in Monte Carlo methods and in our case we can use the measurements as the MC samples (instead of doing the standard Metropolis). To be more explicit, in the code psiloc0 is the final state indexed by the measurement samples (that is <sigma | psi >) and psiloc the same after A has been applied (that is <sigma | A |psi >). So ev calculates the sum from the equation above using every local term of the Hamiltonian as your A.
As I said, this approach still uses the full state vector so it is not the one you would use in the quantum computer, however I think it can give an estimate of the statistical noise in the EV, since it is not an exact matrix multiplication calculation. It is also slightly easier to implement because it does not require rotating and re-measuring for every term like the pure quantum approach would require.

Thanks for your notes and your code Stavros, it is now clear to me. The fact that we need the state to compute the hamiltonian is not a problem for me, since we are simulating in the most efficient manner we are able to do.
I just have a question: you are using a hamiltonian TFIM which can be trotterized. What if we want to compute the expected value of a Hamiltonian that has not been defined in the same way? Can I just trotterize any hamiltonian (from a qibo perspective)

Thanks for checking this.

I just have a question: you are using a hamiltonian TFIM which can be trotterized. What if we want to compute the expected value of a Hamiltonian that has not been defined in the same way? Can I just trotterize any hamiltonian (from a qibo perspective)

Yes, you can trotterize (from the qibo perspective) any Hamiltonian. The TrotterHamiltonian name may be a bit deceptive, I guess we named it this way because we created with Trotter evolution in mind. However, when it comes down to the actual implementation it is just a Hamiltonian that is defined using local terms instead of the full 2^Nx2^N Hamiltonian. It has some methods (such as the .circuit) that are related to Trotter evolution, but if you don't use them you never actually perform any trotterization. The above application is an example of this.
I think the easiest way to define your custom Hamiltonian as TrotterHamiltonian is to write it using sympy symbols and use TrotterHamiltonian.from_symbolic, like the example I referred above. The symbols method is easy to use because you essentially use the Hamiltonian with the form you would write it on paper.


Add pip downloads

The badges bar is getting a bit crowded, should we remove the Waffle badge?

Yeah, or maybe a smaller version of the waffle badge?

Yeah, or maybe a smaller version of the waffle badge?

Yep, it should at least all fit into one line.


Update Deployment Script to Include File Pre-processing

Implement new capability in the Deployment Pipeline
This is associated with the Scope of:

Freeing the Tech Lead from the task of setting new content to production (i.e. automating the deployment pipeline)

Not needed after #64