[Task]: Update Electron

Task description
Update Electron to major version >=12.
Issue: To expose the wallet API, we create a Proxy object, which allows us to intercept calls to the wallet API and store callbacks or override them. We then expose this object to the renderer process here. Since these are two isolated JS contexts, the structured clone algorithm is used to copy objects between them. The catch is that functions and other complex properties will not be cloned, according to the spec. The reason we’re able to do this now seems to be because Electron 11 deviated from the spec.
Requirements

[x] Determine if it is worth considering a later Electron version than 12 (the more recent the better) i.e. with minimal breaking changes (see Snyk chart here)
[x] Test on all desktop platforms:

[x] Linux
[x] Windows
[x] MacOS

Acceptance criteria

Electron PR merged and released in 1.4.0

Creation checklist

[X] I have assigned this task to the correct people
[X] I have added the most appropriate labels
[X] I have linked the correct milestone and/or project

I'm reopening this, since we the new bindings should be compatible with the new major versions of electron.


add default timeout

Description
An attempt at fixing flaky action
Type of change

Bug fix (non-breaking change which fixes an issue)

So looks like sccache is taking a long time to start... Then I don't entirely understand this - the link you posted has the failing action take around 1:47, seems like sccache --start-server has some timeout of its own that's maybe around 1 minute. So seems to me like adding a 5 minute timeout on the action as a whole is not going to do anything?

I agree, there are various reports on GH but nothing super specific: https://github.com/mozilla/sccache/issues/739
We could increase logging and monitor, but closing for now.


Remove SwiftTryCatch from the dependencies

While i was trying to import Sourcery via SPM i've got this message

I had a quick look and i saw that SwiftTryCatch was used only on Sourcery.swift and no one of the two blocks that i changed was actually throwing, then I think it was not even working as expected.
Then my proposal is just remove the dependency.
SPM can now import my forked branch as dependency

SwiftTryCatch is for catching objective-c exceptions, those functions are throwing and you can't just remove it because it will break functionality we rely on

Ok, thank you @krzysztofzablocki

          1 Error

:no_entry_sign:
Any changes to library code need a summary in the Changelog.

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger


Issue 31 docker

https://github.com/tesla-local-control/tesla_ble_mqtt_docker/issues/31
Two corrections:

the command sentry-mode was non existing in listen_to_mqtt.sh
mqtt sends uppercase ON/OFF, which is not parsed by tesla-control --> forced lowercase in listen_to_mqtt.sh

Approved but still 1 failing check

Will fix Changelog of sw-heater


Adding a space before the search term is giving totally different results

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Login to E.cash
Open any chat
Click the emoji picker
Add a space and start typing any letter (Eg. t )

Expected Result:
Should have got these results

Actual Result:

Workaround:
NA
Platform:
Where is this issue occurring?
Web :heavy_check_mark:
iOS
Android
Desktop App :heavy_check_mark:
Mobile Web
Version Number:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
View all open jobs on Upwork

Triggered auto assignment to @arielgreen (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

Triggered auto assignment to @robertjchen (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Triggered auto assignment to @JmillsExpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Just merged the PR

I think this issue is covered in the https://github.com/Expensify/App/issues/4155. Thus can be closed.

Yes!


Allow servers to select compression level via initial MD & overall compression cleanup

Setting the newly added compression_level field of grpc_op::send_initial_metadata by a server now has the effect of applying that compression level for the subsequent call messages leaving the server. The ultimate meaning of the level depends on the client's supported compression algorithms.

I thought the point of adding memset everywhere was to memset the whole op to 0 when it is created, so that we would never have to do this again.

That was the intent.
On Mon, May 9, 2016 at 8:59 AM Michael Lumish<EMAIL_ADDRESS>wrote:

I thought the point of adding memset everywhere was to memset the whole
op to 0 when it is created, so that we would never have to do this again.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/6481#issuecomment-217907211

Yes, agreed. Unintentional omission (current state was just easier to grep for as a starting point). Fixing.
In any case the most review-worthy part of the code is the changes to surface/call.c.

It seems like using the default value of CompressionLevel=None as a default for the send initial metadata operation is problematic if you also allow setting compression level/algorithm at the channel or server level.
e.g. If you set a channel-wide setting of default level being "LOW" let's say,   does   CompressionLevel=None in the send metadata operation means you want to disable compression for that call or that you wanna go with the default channel-wide setting? "LOW" here.
Looks like we would be better of with data.send_initial_metadata.compression_level  being nullable.

@jtattermusch addressesed on latest commit f210b43. PTAL.

The fix itself looks fine to me.
There's a build error:
[CXX]     Compiling src/cpp/client/client_context.cc
In file included from include/grpc++/impl/call.h:37:0,
                 from include/grpc++/channel.h:39,
                 from src/cpp/client/channel.cc:34:
include/grpc++/impl/codegen/call.h: In member function 'void grpc::CallOpSendInitialMetadata::AddOp(grpc_op*, size_t*)':
include/grpc++/impl/codegen/call.h:205:36: error: 'struct grpc_op::<anonymous union>::<anonymous>' has no member named 'compression_level'
     op->data.send_initial_metadata.compression_level = compression_level_;
                                    ^
Makefile:2126: recipe for target '/var/local/git/grpc/objs/dbg/src/cpp/client/channel.o' failed
make: *** [/var/local/git/grpc/objs/dbg/src/cpp/client/channel.o] Error 1
make: *** Waiting for unfinished jobs....
Command exited with non-zero status 2
real 15.01
user 18.24
sys 3.12

FAILED: make [ret=2, pid=590]

@jtattermusch Fixed.

Failure is flaky

Ping :)

Fixes #6219

Had one minor comment which is fixed in the latest commit.
LGTM!..

test this please

Known flakes: run_ruby and openloop


Build fails because the used node-gyp version does not support python 3

Building the sqlite3 package during the installation process fails with the following message:
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| linux | x64
gyp info ok
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| linux | x64
gyp ERR! configure error
gyp ERR! stack Error: Command failed: /usr/bin/python3.8 -c import sys; print "%s.%s.%s" % sys.version_info[:3];
gyp ERR! stack   File "<string>", line 1
gyp ERR! stack     import sys; print "%s.%s.%s" % sys.version_info[:3];
gyp ERR! stack                       ^
gyp ERR! stack SyntaxError: invalid syntax
gyp ERR! stack
gyp ERR! stack     at ChildProcess.exithandler (child_process.js:308:12)
gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
gyp ERR! stack     at maybeClose (internal/child_process.js:1048:16)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
gyp ERR! System Linux 4.19.128-microsoft-standard

The problem is that the used node-gyp version defined in the package.json (3.x) is from 2018 and does not work with python 3, See issue #1965 from the node-gyp project. Changing the version (to use the current version at this moment 7.1.2) built with no errors.
If it still doesn't work and you see the following line /bin/sh: 1: python: not found,  you may need to set the PYTHON env variables, configure python in your npm config file or install sudo apt install python-is-python3
By the way the package node-pre-gyp is deprecated, this is the new one.

I replaced the no-pre-gyp package with mapbox/node-pre-gyp and I forked a new version with it. It works fine.
https://github.com/JapArt/node-sqlite3
Meanwhile I submitted a pull request for updating.

This was fixed in 1441

not fixed....
error /Users/v0/Projects/Authing/authing-server/node_modules/sqlite3: Command failed.
Exit code: 1
Command: node-pre-gyp install --fallback-to-build
Arguments:
Directory: /Users/v0/Projects/Authing/authing-server/node_modules/sqlite3
Output:
node-pre-gyp info it worked if it ends with ok
node-pre-gyp info using<EMAIL_ADDRESS>node-pre-gyp info using<EMAIL_ADDRESS>| darwin | arm64
node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp info check checked for "/Users/v0/Projects/Authing/authing-server/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64/node_sqlite3.node" (not found)
node-pre-gyp http GET https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v5.0.2/napi-v3-darwin-arm64.tar.gz
node-pre-gyp http 403 https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v5.0.2/napi-v3-darwin-arm64.tar.gz
node-pre-gyp WARN Tried to download(403): https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v5.0.2/napi-v3-darwin-arm64.tar.gz
node-pre-gyp WARN Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v93 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp http 403 status code downloading tarball https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v5.0.2/napi-v3-darwin-arm64.tar.gz
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| darwin | arm64
gyp info ok
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| darwin | arm64
gyp ERR! configure error
gyp ERR! stack Error: Command failed: /usr/bin/python3 -c import sys; print "%s.%s.%s" % sys.version_info[:3];
gyp ERR! stack   File "<string>", line 1
gyp ERR! stack     import sys; print "%s.%s.%s" % sys.version_info[:3];
gyp ERR! stack                       ^
gyp ERR! stack SyntaxError: invalid syntax
gyp ERR! stack
gyp ERR! stack     at ChildProcess.exithandler (node:child_process:397:12)
gyp ERR! stack     at ChildProcess.emit (node:events:390:28)
gyp ERR! stack     at maybeClose (node:internal/child_process:1064:16)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
gyp ERR! System Darwin 21.4.0
gyp ERR! command "/Users/v0/.nvm/versions/node/v16.13.0/bin/node" "/Users/v0/Projects/Authing/authing-server/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/Users/v0/Projects/Authing/authing-server/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64/node_sqlite3.node" "--module_name=node_sqlite3" "--module_path=/Users/v0/Projects/Authing/authing-server/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64" "--napi_version=8" "--node_abi_napi=napi" "--napi_build_version=3" "--node_napi_label=napi-v3"
gyp ERR! cwd /Users/v0/Projects/Authing/authing-server/node_modules/sqlite3
gyp ERR! node -v v16.13.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/Users/v0/.nvm/versions/node/v16.13.0/bin/node /Users/v0/Projects/Authing/authing-server/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/Users/v0/Projects/Authing/authing-server/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64/node_sqlite3.node --module_name=node_sqlite3 --module_path=/Users/v0/Projects/Authing/authing-server/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64 --napi_version=8 --node_abi_napi=napi --napi_build_version=3 --node_napi_label=napi-v3' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/Users/v0/Projects/Authing/authing-server/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (node:events:390:28)
node-pre-gyp ERR! stack     at maybeClose (node:internal/child_process:1064:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
node-pre-gyp ERR!  Extracting by manifest.
540 silly tarball no local data for mime-types@https://registry.npmjs.org/mime-types/-/mime-types-2.1.35.tgz. Extracting by manifest.
541 silly tarball no local data for needle@https://registry.npmjs.org/needle/-/needle-2.9.1.tgz. Extracting by manifest.
542 silly tarball no local data for minimist@https://registry.npmjs.org/minimist/-/minimist-1.2.6.tgz. Extracting by manifest.
543 silly tarball no local data for npm-packlist@https://registry.npmjs.org/npm-packlist/-/npm-packlist-1.4.8.tgz. Extracting by manifest.
544 silly tarball no local data for graceful-fs@https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.10.tgz. Extracting by manifest.
545 silly tarball no local data for mkdirp@https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.6.tgz. Extracting by manifest.
546 silly tarball no local data for sqlite3@https://registry.npmjs.org/sqlite3/-/sqlite3-5.0.2.tgz. Extracting by manifest.
547 silly tarball no local data for node-addon-api@https://registry.npmjs.org/node-addon-api/-/node-addon-api-3.2.1.tgz. Extracting by manifest.
548 silly tarball no local data for node-pre-gyp@https://registry.npmjs.org/node-pre-gyp/-/node-pre-gyp-0.11.0.tgz. Extracting by manifest.
549 timing reifyNode:node_modules/fs-minipass Completed in 149ms
550 timing reifyNode:node_modules/chownr Completed in 148ms
551 timing reifyNode:node_modules/ansi-regex Completed in 148ms
552 timing reifyNode:node_modules/code-point-at Completed in 149ms
553 timing reifyNode:node_modules/is-fullwidth-code-point Completed in 149ms
554 timing reifyNode:node_modules/number-is-nan Completed in 149ms
555 timing reifyNode:node_modules/oauth-sign Completed in 148ms
556 timing reifyNode:node_modules/process-nextick-args Completed in 148ms
557 timing reifyNode:node_modules/ini Completed in 148ms
558 timing reifyNode:node_modules/os-tmpdir Completed in 148ms
559 timing reifyNode:node_modules/strip-json-comments Completed in 148ms
560 timing reifyNode:node_modules/os-homedir Completed in 148ms
561 timing reifyNode:node_modules/strip-ansi Completed in 148ms
562 timing reifyNode:node_modules/string-width Completed in 148ms
563 timing reifyNode:node_modules/has-unicode Completed in 148ms
564 timing reifyNode:node_modules/aproba Completed in 148ms
565 timing reifyNode:node_modules/object-assign Completed in 148ms
566 timing reifyNode:node_modules/wide-align Completed in 148ms
567 timing reifyNode:node_modules/abbrev Completed in 147ms
568 timing reifyNode:node_modules/npm-bundled Completed in 147ms
569 timing reifyNode:node_modules/ignore-walk Completed in 147ms
570 timing reifyNode:node_modules/ms Completed in 148ms
571 timing reifyNode:node_modules/wrappy Completed in 148ms
572 timing reifyNode:node_modules/inflight Completed in 148ms
573 timing reifyNode:node_modules/path-is-absolute Completed in 148ms
574 timing reifyNode:node_modules/once Completed in 148ms
575 timing reifyNode:node_modules/brace-expansion Completed in 148ms
576 timing reifyNode:node_modules/osenv Completed in 147ms
577 timing reifyNode:node_modules/minizlib Completed in 152ms
578 timing reifyNode:node_modules/minipass Completed in 152ms
579 timing reifyNode:node_modules/block-stream Completed in 151ms
580 timing reifyNode:node_modules/assert-plus Completed in 150ms
581 timing reifyNode:node_modules/is-typedarray Completed in 151ms
582 timing reifyNode:node_modules/tunnel-agent Completed in 151ms
583 timing reifyNode:node_modules/forever-agent Completed in 150ms
584 timing reifyNode:node_modules/caseless Completed in 150ms
585 timing reifyNode:node_modules/core-util-is Completed in 150ms
586 timing reifyNode:node_modules/set-blocking Completed in 150ms
587 timing reifyNode:node_modules/aws-sign2 Completed in 150ms
588 timing reifyNode:node_modules/console-control-strings Completed in 150ms
589 timing reifyNode:node_modules/signal-exit Completed in 150ms
590 timing reifyNode:node_modules/inherits Completed in 150ms
591 timing reifyNode:node_modules/yallist Completed in 154ms
592 timing reifyNode:node_modules/combined-stream Completed in 152ms
593 timing reifyNode:node_modules/util-deprecate Completed in 152ms
594 timing reifyNode:node_modules/balanced-match Completed in 151ms
595 timing reifyNode:node_modules/rimraf Completed in 150ms
596 timing reifyNode:node_modules/fs.realpath Completed in 151ms
597 timing reifyNode:node_modules/getpass Completed in 154ms
598 timing reifyNode:node_modules/delayed-stream Completed in 153ms
599 warn deprecated<EMAIL_ADDRESS>this library is no longer supported
600 timing reifyNode:node_modules/har-validator Completed in 154ms
601 timing reifyNode:node_modules/deep-extend Completed in 153ms
602 timing reifyNode:node_modules/string_decoder Completed in 153ms
603 timing reifyNode:node_modules/safe-buffer Completed in 153ms
604 timing reifyNode:node_modules/which Completed in 152ms
605 timing reifyNode:node_modules/minimatch Completed in 152ms
606 timing reifyNode:node_modules/npmlog Completed in 151ms
607 timing reifyNode:node_modules/punycode Completed in 156ms
608 timing reifyNode:node_modules/bcrypt-pbkdf Completed in 156ms
609 timing reifyNode:node_modules/json-schema Completed in 156ms
610 timing reifyNode:node_modules/isarray Completed in 154ms
611 timing reifyNode:node_modules/sax Completed in 154ms
612 timing reifyNode:node_modules/node-pre-gyp/node_modules/safe-buffer Completed in 154ms
613 timing reifyNode:node_modules/concat-map Completed in 155ms
614 timing reifyNode:node_modules/delegates Completed in 156ms
615 timing reifyNode:node_modules/verror/node_modules/core-util-is Completed in 158ms
616 timing reifyNode:node_modules/isexe Completed in 159ms
617 timing reifyNode:node_modules/jsprim Completed in 159ms
618 timing reifyNode:node_modules/isstream Completed in 158ms
619 timing reifyNode:node_modules/extend Completed in 157ms
620 timing reifyNode:node_modules/aws4 Completed in 157ms
621 timing reifyNode:node_modules/safer-buffer Completed in 156ms
622 timing reifyNode:node_modules/are-we-there-yet Completed in 157ms
623 timing reifyNode:node_modules/detect-libc Completed in 156ms
624 timing reifyNode:node_modules/verror Completed in 160ms
625 timing reifyNode:node_modules/jsbn Completed in 160ms
626 timing reifyNode:node_modules/node-pre-gyp/node_modules/nopt Completed in 156ms
627 timing reifyNode:node_modules/semver Completed in 156ms
628 timing reifyNode:node_modules/glob Completed in 156ms
629 timing reifyNode:node_modules/ecc-jsbn Completed in 161ms
630 timing reifyNode:node_modules/extsprintf Completed in 161ms
631 timing reifyNode:node_modules/json-stringify-safe Completed in 160ms
632 timing reifyNode:node_modules/json-schema-traverse Completed in 160ms
633 timing reifyNode:node_modules/debug Completed in 159ms
634 timing reifyNode:node_modules/asn1 Completed in 162ms
635 timing reifyNode:node_modules/fast-deep-equal Completed in 161ms
636 timing reifyNode:node_modules/nopt Completed in 159ms
637 timing reifyNode:node_modules/dashdash Completed in 163ms
638 timing reifyNode:node_modules/rc Completed in 161ms
639 timing reifyNode:node_modules/tough-cookie Completed in 164ms
640 timing reifyNode:node_modules/http-signature Completed in 166ms
641 timing reifyNode:node_modules/form-data Completed in 165ms
642 timing reifyNode:node_modules/asynckit Completed in 167ms
643 timing reifyNode:node_modules/performance-now Completed in 167ms
644 timing reifyNode:node_modules/npm-normalize-package-bin Completed in 165ms
645 timing reifyNode:node_modules/fast-json-stable-stringify Completed in 167ms
646 warn deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
647 timing reifyNode:node_modules/uuid Completed in 169ms
648 timing reifyNode:node_modules/har-schema Completed in 169ms
649 timing reifyNode:node_modules/tweetnacl Completed in 170ms
650 timing reifyNode:node_modules/gauge Completed in 168ms
651 timing reifyNode:node_modules/fstream Completed in 168ms
652 timing reifyNode:node_modules/qs Completed in 172ms
653 timing reifyNode:node_modules/readable-stream Completed in 172ms
654 warn deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
655 timing reifyNode:node_modules/request Completed in 170ms
656 timing reifyNode:node_modules/psl Completed in 174ms
657 timing reifyNode:node_modules/node-pre-gyp/node_modules/tar Completed in 170ms
658 timing reifyNode:node_modules/iconv-lite Completed in 172ms
659 timing reifyNode:node_modules/sshpk Completed in 177ms
660 timing reifyNode:node_modules/uri-js Completed in 181ms
661 timing reifyNode:node_modules/ajv Completed in 188ms
662 warn deprecated<EMAIL_ADDRESS>This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
663 timing reifyNode:node_modules/tar Completed in 188ms
664 timing reifyNode:node_modules/node-gyp Completed in 189ms
665 http fetch GET 200 https://registry.npmjs.org/minimist/-/minimist-1.2.6.tgz 222ms (cache miss)
666 timing reifyNode:node_modules/minimist Completed in 248ms
667 http fetch GET 200 https://registry.npmjs.org/npm-packlist/-/npm-packlist-1.4.8.tgz 232ms (cache miss)
668 timing reifyNode:node_modules/npm-packlist Completed in 259ms
669 http fetch GET 200 https://registry.npmjs.org/mime-types/-/mime-types-2.1.35.tgz 241ms (cache miss)
670 timing reifyNode:node_modules/mime-types Completed in 265ms
671 http fetch GET 200 https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.10.tgz 239ms (cache miss)
672 timing reifyNode:node_modules/graceful-fs Completed in 267ms
673 http fetch GET 200 https://registry.npmjs.org/node-pre-gyp/-/node-pre-gyp-0.11.0.tgz 236ms (cache miss)
674 warn deprecated<EMAIL_ADDRESS>Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
675 timing reifyNode:node_modules/node-pre-gyp Completed in 271ms
676 http fetch GET 200 https://registry.npmjs.org/needle/-/needle-2.9.1.tgz 448ms (cache miss)
677 timing reifyNode:node_modules/needle Completed in 474ms
678 http fetch GET 200 https://registry.npmjs.org/mime-db/-/mime-db-1.52.0.tgz 648ms (cache miss)
679 timing reifyNode:node_modules/mime-db Completed in 671ms
680 http fetch GET 200 https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.6.tgz 740ms (cache miss)
681 timing reifyNode:node_modules/mkdirp Completed in 769ms
682 http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/advisories/bulk 897ms
683 timing auditReport:getReport Completed in 900ms
684 silly audit report {
684 silly audit report   tar: [
684 silly audit report     {
684 silly audit report       id: 1067734,
684 silly audit report       url: 'https://github.com/advisories/GHSA-qq89-hq3f-393p',
684 silly audit report       title: 'Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links',
684 silly audit report       severity: 'high',
684 silly audit report       vulnerable_versions: '<4.4.18',
684 silly audit report       cwe: [Array],
684 silly audit report       cvss: [Object]
684 silly audit report     },
684 silly audit report     {
684 silly audit report       id: 1067731,
684 silly audit report       url: 'https://github.com/advisories/GHSA-5955-9wpr-37jh',
684 silly audit report       title: 'Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization',
684 silly audit report       severity: 'high',
684 silly audit report       vulnerable_versions: '<4.4.18',
684 silly audit report       cwe: [Array],
684 silly audit report       cvss: [Object]
684 silly audit report     },
684 silly audit report     {
684 silly audit report       id: 1067737,
684 silly audit report       url: 'https://github.com/advisories/GHSA-9r2w-394v-53qc',
684 silly audit report       title: 'Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links',
684 silly audit report       severity: 'high',
684 silly audit report       vulnerable_versions: '<4.4.16',
684 silly audit report       cwe: [Array],
684 silly audit report       cvss: [Object]
684 silly audit report     },
684 silly audit report     {
684 silly audit report       id: 1067767,
684 silly audit report       url: 'https://github.com/advisories/GHSA-3jfq-g458-7qm9',
684 silly audit report       title: 'Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization',
684 silly audit report       severity: 'high',
684 silly audit report       vulnerable_versions: '<3.2.2',
684 silly audit report       cwe: [Array],
684 silly audit report       cvss: [Object]
684 silly audit report     },
684 silly audit report     {
684 silly audit report       id: 1067771,
684 silly audit report       url: 'https://github.com/advisories/GHSA-r628-mhmh-qjhw',
684 silly audit report       title: 'Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning',
684 silly audit report       severity: 'high',
684 silly audit report       vulnerable_versions: '<3.2.3',
684 silly audit report       cwe: [Array],
684 silly audit report       cvss: [Object]
684 silly audit report     }
684 silly audit report   ]
684 silly audit report }
685 timing metavuln:packument:tar Completed in 1ms
686 timing metavuln:cache:get:security-advisory:tar:9fCpHzYQDt6/279Ukg2ZXFXMglUrGwxbNicHsd4J1Z/goqUTOwGqLEJtH40hwrcXHzh/ZasDnm+E4OyQiedXcA== Completed in 2ms
687 timing metavuln:load:security-advisory:tar:1067734 Completed in 5ms
688 timing metavuln:cache:get:security-advisory:tar:LGNpIzs2mH9XBi2mIftUzBCnZdQGwNe6Yz6M07r8S9KPT8S7NHhp8QgxhRg0PydzD18H6KHGntGF+k9ycD49qQ== Completed in 7ms
689 timing metavuln:load:security-advisory:tar:1067731 Completed in 5ms
690 timing metavuln:cache:get:security-advisory:tar:UQnNosBtZfHHkOQcVUKYNPiU0PB/uNif2cbvnrzKbzCEyfB9pW6JZR0xSaGSkCQj2Rvcpx7WgYvcwRe9X8/XSA== Completed in 12ms
691 timing metavuln:load:security-advisory:tar:1067737 Completed in 2ms
692 timing metavuln:cache:get:security-advisory:tar:A8ImuLv3PmHkbpv9X1ifoxqAnyDnPy8K7sEkyfb1iRSOiZ9OFMyNgaF+clYyOCD7Q0QgxfIz2bPDZD6fyLC9kw== Completed in 15ms
693 timing metavuln:load:security-advisory:tar:1067767 Completed in 3ms
694 timing metavuln:cache:get:security-advisory:tar:fhqFzz90bxoq7DaGDlMK7t7CjkJNFn2vuRIo+17L7EtXkYoVaFkn8vve3AzvhxKJeEreLM52fhjseseedPLuJA== Completed in 18ms
695 timing metavuln:load:security-advisory:tar:1067771 Completed in 1ms
696 timing metavuln:cache:put:security-advisory:tar:fhqFzz90bxoq7DaGDlMK7t7CjkJNFn2vuRIo+17L7EtXkYoVaFkn8vve3AzvhxKJeEreLM52fhjseseedPLuJA== Completed in 3ms
697 timing metavuln:calculate:security-advisory:tar:1067771 Completed in 22ms
698 timing metavuln:cache:put:security-advisory:tar:UQnNosBtZfHHkOQcVUKYNPiU0PB/uNif2cbvnrzKbzCEyfB9pW6JZR0xSaGSkCQj2Rvcpx7WgYvcwRe9X8/XSA== Completed in 8ms
699 timing metavuln:calculate:security-advisory:tar:1067737 Completed in 22ms
700 timing metavuln:cache:put:security-advisory:tar:A8ImuLv3PmHkbpv9X1ifoxqAnyDnPy8K7sEkyfb1iRSOiZ9OFMyNgaF+clYyOCD7Q0QgxfIz2bPDZD6fyLC9kw== Completed in 4ms
701 timing metavuln:calculate:security-advisory:tar:1067767 Completed in 22ms
702 timing metavuln:cache:put:security-advisory:tar:LGNpIzs2mH9XBi2mIftUzBCnZdQGwNe6Yz6M07r8S9KPT8S7NHhp8QgxhRg0PydzD18H6KHGntGF+k9ycD49qQ== Completed in 10ms
703 timing metavuln:calculate:security-advisory:tar:1067731 Completed in 22ms
704 timing metavuln:cache:put:security-advisory:tar:9fCpHzYQDt6/279Ukg2ZXFXMglUrGwxbNicHsd4J1Z/goqUTOwGqLEJtH40hwrcXHzh/ZasDnm+E4OyQiedXcA== Completed in 16ms
705 timing metavuln:calculate:security-advisory:tar:1067734 Completed in 23ms
706 timing metavuln:packument:node-gyp Completed in 0ms
707 timing metavuln:cache:get:security-advisory:node-gyp:1opMWdTWymr8/s3Fi4W4hP4UjSiXB00F5DIHQi/Wb2al2R7g8mzAe+/dQaybc8bLLFG9iqp9BZbk6t68WE9c+A== Completed in 0ms
708 timing metavuln:load:security-advisory:node-gyp:9fCpHzYQDt6/279Ukg2ZXFXMglUrGwxbNicHsd4J1Z/goqUTOwGqLEJtH40hwrcXHzh/ZasDnm+E4OyQiedXcA== Completed in 6ms
709 timing metavuln:cache:put:security-advisory:node-gyp:1opMWdTWymr8/s3Fi4W4hP4UjSiXB00F5DIHQi/Wb2al2R7g8mzAe+/dQaybc8bLLFG9iqp9BZbk6t68WE9c+A== Completed in 3ms
710 timing metavuln:calculate:security-advisory:node-gyp:9fCpHzYQDt6/279Ukg2ZXFXMglUrGwxbNicHsd4J1Z/goqUTOwGqLEJtH40hwrcXHzh/ZasDnm+E4OyQiedXcA== Completed in 9ms
711 timing metavuln:packument:sqlite3 Completed in 0ms
712 timing metavuln:cache:get:security-advisory:sqlite3:vjotBIl09Ff5uJDgzktFRP4/y1hir1n0IYN+/ivTZ37Wu8X8MfqXTx3Xw1qDpu4z1N9vOAVBpI0h6u2wADcDNQ== Completed in 0ms
713 timing metavuln:load:security-advisory:sqlite3:1opMWdTWymr8/s3Fi4W4hP4UjSiXB00F5DIHQi/Wb2al2R7g8mzAe+/dQaybc8bLLFG9iqp9BZbk6t68WE9c+A== Completed in 1ms
714 timing metavuln:cache:put:security-advisory:sqlite3:vjotBIl09Ff5uJDgzktFRP4/y1hir1n0IYN+/ivTZ37Wu8X8MfqXTx3Xw1qDpu4z1N9vOAVBpI0h6u2wADcDNQ== Completed in 2ms
715 timing metavuln:calculate:security-advisory:sqlite3:1opMWdTWymr8/s3Fi4W4hP4UjSiXB00F5DIHQi/Wb2al2R7g8mzAe+/dQaybc8bLLFG9iqp9BZbk6t68WE9c+A== Completed in 3ms
716 timing auditReport:init Completed in 37ms
717 timing reify:audit Completed in 938ms
718 http fetch GET 200 https://registry.npmjs.org/node-addon-api/-/node-addon-api-3.2.1.tgz 1080ms (cache miss)
719 timing reifyNode:node_modules/node-addon-api Completed in 1114ms
720 http fetch GET 200 https://registry.npmjs.org/sqlite3/-/sqlite3-5.0.2.tgz 2034ms (cache miss)
721 timing reifyNode:node_modules/sqlite3 Completed in 2067ms
722 timing reify:unpack Completed in 2072ms
723 timing reify:unretire Completed in 0ms
724 timing build:queue Completed in 4ms
725 timing build:link:node_modules/detect-libc Completed in 3ms
726 timing build:link:node_modules/node-pre-gyp/node_modules/nopt Completed in 2ms
727 timing build:link:node_modules/needle Completed in 3ms
728 timing build:link:node_modules/mkdirp Completed in 3ms
729 timing build:link:node_modules/node-gyp Completed in 2ms
730 timing build:link:node_modules/rc Completed in 2ms
731 timing build:link:node_modules/semver Completed in 2ms
732 timing build:link:node_modules/nopt Completed in 2ms
733 timing build:link:node_modules/rimraf Completed in 2ms
734 timing build:link:node_modules/node-pre-gyp Completed in 2ms
735 timing build:link:node_modules/sshpk Completed in 2ms
736 timing build:link:node_modules/which Completed in 2ms
737 timing build:link:node_modules/uuid Completed in 2ms
738 timing build:link Completed in 3ms
739 info run<EMAIL_ADDRESS>install node_modules/sqlite3 node-pre-gyp install --fallback-to-build
740 info run<EMAIL_ADDRESS>install { code: 1, signal: null }
741 timing reify:rollback:createSparse Completed in 76ms
742 timing reify:rollback:retireShallow Completed in 0ms
743 timing command:install Completed in 25032ms
744 verbose stack Error: command failed
744 verbose stack     at ChildProcess.<anonymous> (/Users/v0/.nvm/versions/node/v16.13.0/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/index.js:64:27)
744 verbose stack     at ChildProcess.emit (node:events:390:28)
744 verbose stack     at maybeClose (node:internal/child_process:1064:16)
744 verbose stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
745 verbose pkgid<EMAIL_ADDRESS>746 verbose cwd /Users/v0/Desktop/demo
747 verbose Darwin 21.4.0
748 verbose argv "/Users/v0/.nvm/versions/node/v16.13.0/bin/node" "/Users/v0/.nvm/versions/node/v16.13.0/bin/npm" "i" "--save-dev" "sqlite3"
749 verbose node v16.13.0
750 verbose npm  v8.1.0
751 error code 1
752 error path /Users/v0/Desktop/demo/node_modules/sqlite3
753 error command failed
754 error command sh -c node-pre-gyp install --fallback-to-build
755 error CC(target) Release/obj.target/nothing/../node-addon-api/nothing.o
755 error   LIBTOOL-STATIC Release/nothing.a
755 error   ACTION deps_sqlite3_gyp_action_before_build_target_unpack_sqlite_dep Release/obj/gen/sqlite-autoconf-3340000/sqlite3.c
755 error Failed to execute '/Users/v0/.nvm/versions/node/v16.13.0/bin/node /Users/v0/.nvm/versions/node/v16.13.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/v0/Desktop/demo/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64/node_sqlite3.node --module_name=node_sqlite3 --module_path=/Users/v0/Desktop/demo/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64 --napi_version=8 --node_abi_napi=napi --napi_build_version=3 --node_napi_label=napi-v3' (1)
756 error node-pre-gyp info it worked if it ends with ok
756 error node-pre-gyp info using<EMAIL_ADDRESS>756 error node-pre-gyp info using<EMAIL_ADDRESS>| darwin | arm64
756 error node-pre-gyp WARN Using request for node-pre-gyp https download
756 error node-pre-gyp info check checked for "/Users/v0/Desktop/demo/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64/node_sqlite3.node" (not found)
756 error node-pre-gyp http GET https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v5.0.2/napi-v3-darwin-arm64.tar.gz
756 error node-pre-gyp http 403 https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v5.0.2/napi-v3-darwin-arm64.tar.gz
756 error node-pre-gyp WARN Tried to download(403): https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v5.0.2/napi-v3-darwin-arm64.tar.gz
756 error node-pre-gyp WARN Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v93 ABI, unknown) (falling back to source compile with node-gyp)
756 error node-pre-gyp http 403 status code downloading tarball https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v5.0.2/napi-v3-darwin-arm64.tar.gz
756 error gyp info it worked if it ends with ok
756 error gyp info using<EMAIL_ADDRESS>756 error gyp info using<EMAIL_ADDRESS>| darwin | arm64
756 error gyp info ok
756 error gyp info it worked if it ends with ok
756 error gyp info using<EMAIL_ADDRESS>756 error gyp info using<EMAIL_ADDRESS>| darwin | arm64
756 error gyp info find Python using Python version 3.8.9 found at "/Applications/Xcode.app/Contents/Developer/usr/bin/python3"
756 error gyp info spawn /Applications/Xcode.app/Contents/Developer/usr/bin/python3
756 error gyp info spawn args [
756 error gyp info spawn args   '/Users/v0/.nvm/versions/node/v16.13.0/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
756 error gyp info spawn args   'binding.gyp',
756 error gyp info spawn args   '-f',
756 error gyp info spawn args   'make',
756 error gyp info spawn args   '-I',
756 error gyp info spawn args   '/Users/v0/Desktop/demo/node_modules/sqlite3/build/config.gypi',
756 error gyp info spawn args   '-I',
756 error gyp info spawn args   '/Users/v0/.nvm/versions/node/v16.13.0/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
756 error gyp info spawn args   '-I',
756 error gyp info spawn args   '/Users/v0/Library/Caches/node-gyp/16.13.0/include/node/common.gypi',
756 error gyp info spawn args   '-Dlibrary=shared_library',
756 error gyp info spawn args   '-Dvisibility=default',
756 error gyp info spawn args   '-Dnode_root_dir=/Users/v0/Library/Caches/node-gyp/16.13.0',
756 error gyp info spawn args   '-Dnode_gyp_dir=/Users/v0/.nvm/versions/node/v16.13.0/lib/node_modules/npm/node_modules/node-gyp',
756 error gyp info spawn args   '-Dnode_lib_file=/Users/v0/Library/Caches/node-gyp/16.13.0/<(target_arch)/node.lib',
756 error gyp info spawn args   '-Dmodule_root_dir=/Users/v0/Desktop/demo/node_modules/sqlite3',
756 error gyp info spawn args   '-Dnode_engine=v8',
756 error gyp info spawn args   '--depth=.',
756 error gyp info spawn args   '--no-parallel',
756 error gyp info spawn args   '--generator-output',
756 error gyp info spawn args   'build',
756 error gyp info spawn args   '-Goutput_dir=.'
756 error gyp info spawn args ]
756 error gyp info ok
756 error gyp info it worked if it ends with ok
756 error gyp info using<EMAIL_ADDRESS>756 error gyp info using<EMAIL_ADDRESS>| darwin | arm64
756 error gyp info spawn make
756 error gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
756 error warning: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: archive library: Release/nothing.a the table of contents is empty (no object file members in the library define global symbols)
756 error /bin/sh: python: command not found
756 error make: *** [Release/obj/gen/sqlite-autoconf-3340000/sqlite3.c] Error 127
756 error gyp ERR! build error
756 error gyp ERR! stack Error: `make` failed with exit code: 2
756 error gyp ERR! stack     at ChildProcess.onExit (/Users/v0/.nvm/versions/node/v16.13.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
756 error gyp ERR! stack     at ChildProcess.emit (node:events:390:28)
756 error gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
756 error gyp ERR! System Darwin 21.4.0
756 error gyp ERR! command "/Users/v0/.nvm/versions/node/v16.13.0/bin/node" "/Users/v0/.nvm/versions/node/v16.13.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/Users/v0/Desktop/demo/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64/node_sqlite3.node" "--module_name=node_sqlite3" "--module_path=/Users/v0/Desktop/demo/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64" "--napi_version=8" "--node_abi_napi=napi" "--napi_build_version=3" "--node_napi_label=napi-v3"
756 error gyp ERR! cwd /Users/v0/Desktop/demo/node_modules/sqlite3
756 error gyp ERR! node -v v16.13.0
756 error gyp ERR! node-gyp -v v8.2.0
756 error gyp ERR! not ok
756 error node-pre-gyp ERR! build error
756 error node-pre-gyp ERR! stack Error: Failed to execute '/Users/v0/.nvm/versions/node/v16.13.0/bin/node /Users/v0/.nvm/versions/node/v16.13.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/v0/Desktop/demo/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64/node_sqlite3.node --module_name=node_sqlite3 --module_path=/Users/v0/Desktop/demo/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64 --napi_version=8 --node_abi_napi=napi --napi_build_version=3 --node_napi_label=napi-v3' (1)
756 error node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/Users/v0/Desktop/demo/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
756 error node-pre-gyp ERR! stack     at ChildProcess.emit (node:events:390:28)
756 error node-pre-gyp ERR! stack     at maybeClose (node:internal/child_process:1064:16)
756 error node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
756 error node-pre-gyp ERR!   Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
642 timing reifyNode:node_modules/uuid Completed in 164ms
643 timing reifyNode:node_modules/har-schema Completed in 165ms
644 timing reifyNode:node_modules/tweetnacl Completed in 165ms
645 timing reifyNode:node_modules/gauge Completed in 163ms
646 timing reifyNode:node_modules/minimist Completed in 164ms
647 timing reifyNode:node_modules/fstream Completed in 165ms
648 warn deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
649 timing reifyNode:node_modules/request Completed in 167ms
650 timing reifyNode:node_modules/qs Completed in 170ms
651 timing reifyNode:node_modules/readable-stream Completed in 168ms
652 timing reifyNode:node_modules/psl Completed in 172ms
653 timing reifyNode:node_modules/node-pre-gyp/node_modules/tar Completed in 169ms
654 timing reifyNode:node_modules/iconv-lite Completed in 171ms
655 warn deprecated<EMAIL_ADDRESS>Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
656 timing reifyNode:node_modules/node-pre-gyp Completed in 170ms
657 timing reifyNode:node_modules/node-addon-api Completed in 170ms
658 timing reifyNode:node_modules/sshpk Completed in 175ms
659 timing reifyNode:node_modules/needle Completed in 175ms
660 timing reifyNode:node_modules/uri-js Completed in 179ms
661 timing reifyNode:node_modules/ajv Completed in 185ms
662 warn deprecated<EMAIL_ADDRESS>This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
663 timing reifyNode:node_modules/tar Completed in 185ms
664 timing reifyNode:node_modules/sqlite3 Completed in 188ms
665 timing reifyNode:node_modules/node-gyp Completed in 189ms
666 timing reify:unpack Completed in 193ms
667 timing reify:unretire Completed in 0ms
668 timing build:queue Completed in 1ms
669 timing build:link:node_modules/detect-libc Completed in 2ms
670 timing build:link:node_modules/node-pre-gyp Completed in 1ms
671 timing build:link:node_modules/nopt Completed in 1ms
672 timing build:link:node_modules/rimraf Completed in 1ms
673 timing build:link:node_modules/rc Completed in 1ms
674 timing build:link:node_modules/node-gyp Completed in 1ms
675 timing build:link:node_modules/needle Completed in 1ms
676 timing build:link:node_modules/uuid Completed in 1ms
677 timing build:link:node_modules/sshpk Completed in 1ms
678 timing build:link:node_modules/semver Completed in 1ms
679 timing build:link:node_modules/mkdirp Completed in 1ms
680 timing build:link:node_modules/node-pre-gyp/node_modules/nopt Completed in 1ms
681 timing build:link:node_modules/which Completed in 1ms
682 timing build:link Completed in 2ms
683 info run<EMAIL_ADDRESS>install node_modules/sqlite3 node-pre-gyp install --fallback-to-build
684 http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/advisories/bulk 313ms
685 timing auditReport:getReport Completed in 315ms
686 silly audit report {
686 silly audit report   tar: [
686 silly audit report     {
686 silly audit report       id: 1067734,
686 silly audit report       url: 'https://github.com/advisories/GHSA-qq89-hq3f-393p',
686 silly audit report       title: 'Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links',
686 silly audit report       severity: 'high',
686 silly audit report       vulnerable_versions: '<4.4.18',
686 silly audit report       cwe: [Array],
686 silly audit report       cvss: [Object]
686 silly audit report     },
686 silly audit report     {
686 silly audit report       id: 1067731,
686 silly audit report       url: 'https://github.com/advisories/GHSA-5955-9wpr-37jh',
686 silly audit report       title: 'Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization',
686 silly audit report       severity: 'high',
686 silly audit report       vulnerable_versions: '<4.4.18',
686 silly audit report       cwe: [Array],
686 silly audit report       cvss: [Object]
686 silly audit report     },
686 silly audit report     {
686 silly audit report       id: 1067737,
686 silly audit report       url: 'https://github.com/advisories/GHSA-9r2w-394v-53qc',
686 silly audit report       title: 'Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links',
686 silly audit report       severity: 'high',
686 silly audit report       vulnerable_versions: '<4.4.16',
686 silly audit report       cwe: [Array],
686 silly audit report       cvss: [Object]
686 silly audit report     },
686 silly audit report     {
686 silly audit report       id: 1067767,
686 silly audit report       url: 'https://github.com/advisories/GHSA-3jfq-g458-7qm9',
686 silly audit report       title: 'Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization',
686 silly audit report       severity: 'high',
686 silly audit report       vulnerable_versions: '<3.2.2',
686 silly audit report       cwe: [Array],
686 silly audit report       cvss: [Object]
686 silly audit report     },
686 silly audit report     {
686 silly audit report       id: 1067771,
686 silly audit report       url: 'https://github.com/advisories/GHSA-r628-mhmh-qjhw',
686 silly audit report       title: 'Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning',
686 silly audit report       severity: 'high',
686 silly audit report       vulnerable_versions: '<3.2.3',
686 silly audit report       cwe: [Array],
686 silly audit report       cvss: [Object]
686 silly audit report     }
686 silly audit report   ]
686 silly audit report }
687 timing metavuln:packument:tar Completed in 0ms
688 timing metavuln:cache:get:security-advisory:tar:fhqFzz90bxoq7DaGDlMK7t7CjkJNFn2vuRIo+17L7EtXkYoVaFkn8vve3AzvhxKJeEreLM52fhjseseedPLuJA== Completed in 4ms
689 timing metavuln:load:security-advisory:tar:1067771 Completed in 1ms
690 timing metavuln:calculate:security-advisory:tar:1067771 Completed in 5ms
691 timing metavuln:cache:get:security-advisory:tar:A8ImuLv3PmHkbpv9X1ifoxqAnyDnPy8K7sEkyfb1iRSOiZ9OFMyNgaF+clYyOCD7Q0QgxfIz2bPDZD6fyLC9kw== Completed in 5ms
692 timing metavuln:load:security-advisory:tar:1067767 Completed in 0ms
693 timing metavuln:calculate:security-advisory:tar:1067767 Completed in 5ms
694 timing metavuln:cache:get:security-advisory:tar:LGNpIzs2mH9XBi2mIftUzBCnZdQGwNe6Yz6M07r8S9KPT8S7NHhp8QgxhRg0PydzD18H6KHGntGF+k9ycD49qQ== Completed in 5ms
695 timing metavuln:load:security-advisory:tar:1067731 Completed in 0ms
696 timing metavuln:calculate:security-advisory:tar:1067731 Completed in 5ms
697 timing metavuln:cache:get:security-advisory:tar:UQnNosBtZfHHkOQcVUKYNPiU0PB/uNif2cbvnrzKbzCEyfB9pW6JZR0xSaGSkCQj2Rvcpx7WgYvcwRe9X8/XSA== Completed in 5ms
698 timing metavuln:load:security-advisory:tar:1067737 Completed in 1ms
699 timing metavuln:calculate:security-advisory:tar:1067737 Completed in 6ms
700 timing metavuln:cache:get:security-advisory:tar:9fCpHzYQDt6/279Ukg2ZXFXMglUrGwxbNicHsd4J1Z/goqUTOwGqLEJtH40hwrcXHzh/ZasDnm+E4OyQiedXcA== Completed in 6ms
701 timing metavuln:load:security-advisory:tar:1067734 Completed in 1ms
702 timing metavuln:calculate:security-advisory:tar:1067734 Completed in 7ms
703 timing metavuln:packument:node-gyp Completed in 1ms
704 timing metavuln:cache:get:security-advisory:node-gyp:1opMWdTWymr8/s3Fi4W4hP4UjSiXB00F5DIHQi/Wb2al2R7g8mzAe+/dQaybc8bLLFG9iqp9BZbk6t68WE9c+A== Completed in 1ms
705 timing metavuln:load:security-advisory:node-gyp:9fCpHzYQDt6/279Ukg2ZXFXMglUrGwxbNicHsd4J1Z/goqUTOwGqLEJtH40hwrcXHzh/ZasDnm+E4OyQiedXcA== Completed in 1ms
706 timing metavuln:calculate:security-advisory:node-gyp:9fCpHzYQDt6/279Ukg2ZXFXMglUrGwxbNicHsd4J1Z/goqUTOwGqLEJtH40hwrcXHzh/ZasDnm+E4OyQiedXcA== Completed in 2ms
707 timing metavuln:packument:sqlite3 Completed in 0ms
708 timing metavuln:cache:get:security-advisory:sqlite3:vjotBIl09Ff5uJDgzktFRP4/y1hir1n0IYN+/ivTZ37Wu8X8MfqXTx3Xw1qDpu4z1N9vOAVBpI0h6u2wADcDNQ== Completed in 1ms
709 timing metavuln:load:security-advisory:sqlite3:1opMWdTWymr8/s3Fi4W4hP4UjSiXB00F5DIHQi/Wb2al2R7g8mzAe+/dQaybc8bLLFG9iqp9BZbk6t68WE9c+A== Completed in 0ms
710 timing metavuln:calculate:security-advisory:sqlite3:1opMWdTWymr8/s3Fi4W4hP4UjSiXB00F5DIHQi/Wb2al2R7g8mzAe+/dQaybc8bLLFG9iqp9BZbk6t68WE9c+A== Completed in 1ms
711 timing auditReport:init Completed in 10ms
712 timing reify:audit Completed in 326ms
713 info run<EMAIL_ADDRESS>install { code: 1, signal: null }
714 timing reify:rollback:createSparse Completed in 74ms
715 timing reify:rollback:retireShallow Completed in 0ms
716 timing command:install Completed in 9518ms
717 verbose stack Error: command failed
717 verbose stack     at ChildProcess.<anonymous> (/Users/v0/.nvm/versions/node/v16.13.0/lib/node_modules/npm/node_modules/@npmcli/run-script/node_modules/@npmcli/promise-spawn/index.js:64:27)
717 verbose stack     at ChildProcess.emit (node:events:390:28)
717 verbose stack     at maybeClose (node:internal/child_process:1064:16)
717 verbose stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
718 verbose pkgid<EMAIL_ADDRESS>719 verbose cwd /Users/v0/Desktop/demo
720 verbose Darwin 21.4.0
721 verbose argv "/Users/v0/.nvm/versions/node/v16.13.0/bin/node" "/Users/v0/.nvm/versions/node/v16.13.0/bin/npm" "i" "--save-dev" "sqlite3"
722 verbose node v16.13.0
723 verbose npm  v8.1.0
724 error code 1
725 error path /Users/v0/Desktop/demo/node_modules/sqlite3
726 error command failed
727 error command sh -c node-pre-gyp install --fallback-to-build
728 error CC(target) Release/obj.target/nothing/../node-addon-api/nothing.o
728 error   LIBTOOL-STATIC Release/nothing.a
728 error   ACTION deps_sqlite3_gyp_action_before_build_target_unpack_sqlite_dep Release/obj/gen/sqlite-autoconf-3340000/sqlite3.c
728 error Failed to execute '/Users/v0/.nvm/versions/node/v16.13.0/bin/node<EMAIL_ADDRESS>build --fallback-to-build --module=/Users/v0/Desktop/demo/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64/node_sqlite3.node --module_name=node_sqlite3 --module_path=/Users/v0/Desktop/demo/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64 --napi_version=8 --node_abi_napi=napi --napi_build_version=3 --node_napi_label=napi-v3' (1)
729 error node-pre-gyp info it worked if it ends with ok
729 error node-pre-gyp info using<EMAIL_ADDRESS>729 error node-pre-gyp info using<EMAIL_ADDRESS>| darwin | arm64
729 error node-pre-gyp WARN Using request for node-pre-gyp https download
729 error node-pre-gyp info check checked for "/Users/v0/Desktop/demo/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64/node_sqlite3.node" (not found)
729 error node-pre-gyp http GET https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v5.0.2/napi-v3-darwin-arm64.tar.gz
729 error node-pre-gyp http 403 https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v5.0.2/napi-v3-darwin-arm64.tar.gz
729 error node-pre-gyp WARN Tried to download(403): https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v5.0.2/napi-v3-darwin-arm64.tar.gz
729 error node-pre-gyp WARN Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v93 ABI, unknown) (falling back to source compile with node-gyp)
729 error node-pre-gyp http 403 status code downloading tarball https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v5.0.2/napi-v3-darwin-arm64.tar.gz
729 error gyp info it worked if it ends with ok
729 error gyp info using<EMAIL_ADDRESS>729 error gyp info using<EMAIL_ADDRESS>| darwin | arm64
729 error gyp info ok
729 error gyp info it worked if it ends with ok
729 error gyp info using<EMAIL_ADDRESS>729 error gyp info using<EMAIL_ADDRESS>| darwin | arm64
729 error gyp info find Python using Python version 3.8.9 found at "/Applications/Xcode.app/Contents/Developer/usr/bin/python3"
729 error gyp info spawn /Applications/Xcode.app/Contents/Developer/usr/bin/python3
729 error gyp info spawn args [
729 error gyp info spawn args<EMAIL_ADDRESS>729 error gyp info spawn args   'binding.gyp',
729 error gyp info spawn args   '-f',
729 error gyp info spawn args   'make',
729 error gyp info spawn args   '-I',
729 error gyp info spawn args   '/Users/v0/Desktop/demo/node_modules/sqlite3/build/config.gypi',
729 error gyp info spawn args   '-I',
729 error gyp info spawn args<EMAIL_ADDRESS>729 error gyp info spawn args   '-I',
729 error gyp info spawn args   '/Users/v0/Library/Caches/node-gyp/16.13.0/include/node/common.gypi',
729 error gyp info spawn args   '-Dlibrary=shared_library',
729 error gyp info spawn args   '-Dvisibility=default',
729 error gyp info spawn args   '-Dnode_root_dir=/Users/v0/Library/Caches/node-gyp/16.13.0',
729 error gyp info spawn args   '-Dnode_gyp_dir=/Users/v0/.nvm/versions/node/v16.13.0/lib/node_modules/npm/node_modules/@npmcli/run-script/node_modules/node-gyp',
729 error gyp info spawn args   '-Dnode_lib_file=/Users/v0/Library/Caches/node-gyp/16.13.0/<(target_arch)/node.lib',
729 error gyp info spawn args   '-Dmodule_root_dir=/Users/v0/Desktop/demo/node_modules/sqlite3',
729 error gyp info spawn args   '-Dnode_engine=v8',
729 error gyp info spawn args   '--depth=.',
729 error gyp info spawn args   '--no-parallel',
729 error gyp info spawn args   '--generator-output',
729 error gyp info spawn args   'build',
729 error gyp info spawn args   '-Goutput_dir=.'
729 error gyp info spawn args ]
729 error gyp info ok
729 error gyp info it worked if it ends with ok
729 error gyp info using<EMAIL_ADDRESS>729 error gyp info using<EMAIL_ADDRESS>| darwin | arm64
729 error gyp info spawn make
729 error gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
729 error warning: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: archive library: Release/nothing.a the table of contents is empty (no object file members in the library define global symbols)
729 error /bin/sh: python: command not found
729 error make: *** [Release/obj/gen/sqlite-autoconf-3340000/sqlite3.c] Error 127
729 error gyp ERR! build error
729 error gyp ERR! stack Error: `make` failed with exit code: 2
729 error gyp ERR! stack     at ChildProcess.onExit (/Users/v0/.nvm/versions/node/v16.13.0/lib/node_modules/npm/node_modules/@npmcli/run-script/node_modules/node-gyp/lib/build.js:194:23)
729 error gyp ERR! stack     at ChildProcess.emit (node:events:390:28)
729 error gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
729 error gyp ERR! System Darwin 21.4.0
729 error gyp ERR! command "/Users/v0/.nvm/versions/node/v16.13.0/bin/node"<EMAIL_ADDRESS>"build" "--fallback-to-build" "--module=/Users/v0/Desktop/demo/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64/node_sqlite3.node" "--module_name=node_sqlite3" "--module_path=/Users/v0/Desktop/demo/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64" "--napi_version=8" "--node_abi_napi=napi" "--napi_build_version=3" "--node_napi_label=napi-v3"
729 error gyp ERR! cwd /Users/v0/Desktop/demo/node_modules/sqlite3
729 error gyp ERR! node -v v16.13.0
729 error gyp ERR! node-gyp -v v9.0.0
729 error gyp ERR! not ok
729 error node-pre-gyp ERR! build error
729 error node-pre-gyp ERR! stack Error: Failed to execute '/Users/v0/.nvm/versions/node/v16.13.0/bin/node<EMAIL_ADDRESS>build --fallback-to-build --module=/Users/v0/Desktop/demo/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64/node_sqlite3.node --module_name=node_sqlite3 --module_path=/Users/v0/Desktop/demo/node_modules/sqlite3/lib/binding/napi-v3-darwin-arm64 --napi_version=8 --node_abi_napi=napi --napi_build_version=3 --node_napi_label=napi-v3' (1)
729 error node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/Users/v0/Desktop/demo/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
729 error node-pre-gyp ERR! stack     at ChildProcess.emit (node:events:390:28)
729 error node-pre-gyp ERR! stack     at maybeClose (node:internal/child_process:1064:16)
729 error node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
729 error node-pre-gyp ERR! System Darwin 21.4.0
729 error node-pre-gyp ERR! command "/Users/v0/.nvm/versions/node/v16.13.0/bin/node" "/Users/v0/Desktop/demo/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
729 error node-pre-gyp ERR! cwd /Users/v0/Desktop/demo/node_modules/sqlite3
729 error node-pre-gyp ERR! node -v v16.13.0
729 error node-pre-gyp ERR! node-pre-gyp -v v0.11.0
729 error node-pre-gyp ERR! not ok
730 verbose exit 1

error node-pre-gyp ERR! node-pre-gyp -v v0.11.0

vs. v1.0.9 https://github.com/mapbox/node-pre-gyp/blob/master/CHANGELOG.md


Create prover skeleton

Create in a subfolder of this repo a project skeleton for the prover. This will be a Haskell project. The skeleton should include a Nix flake, CI with linting and testing stubbed out, and a stubbed out entry point.

With respect to the issue below, what is the relationship to halo2 here for provisioning it in the flake?
Is it Haskell-Rust FFI, CLI, other?

Let's talk about it. I need to understand first how #30 will be implemented. But still, that integration is not in the scope of this ticket.

Ticket created in Orbis-Tertius/prover https://github.com/Orbis-Tertius/prover/issues/3


Analyses colors are not correct

@viddo were you planning to do this?

I figured I'd do it eventually, but first I want to finish the layer creation. If you don't have anything else to work on you could start on it.
But either way I'd most likely need to change some things in my current WIP (the layer-creation-from-node), since some logic related to how the nodes are rendered have changed.


88B planned ?

Great project!
Unfortunately the X-40's are very scarce  now.  I bought the only one I could find on ebay and it just arrived ... with an 88B module.  Any chance you're going to support it someday?  Any suggestions where I might find a X-40 with the right module?
Thanks for the amazing work in any case ... wish I could give you 4 stars!
Skip

I looks like the 88B module already has serial which is what I need.  But I can't find any documentation on the serial protocol, sigh.
Here's some info I mined from https://www.alibaba.com/product-detail/Phase-Shift-M88B-Laser-Distance-Measurement_60696810434.html

Hello.
Unfortunately, support for M88 modules is not planned - I don't have such module.
Newer U85x modules are supported: Link
Notice that firmware for cheap laser tape measure modules is differ from more expensive "UART" versions of that modules - UART is disabled in laser tape measures.
Looks like that this is manual for M88: Link

Thanks for the quick response! I wish shipping from China was as fast!
I'll order some U85x versions and revisit my project in a month or so.


Update README.md

Update code snippet to reflect UseLambdaErrorHandler rename

Thanks for correcting this!

No worries. Thanks for this library, it's awesome! I'm going to do a short talk about it at a meetup =)

Nice, if there will be some recording please share it!


Can i use char as rule id?

for some reason, i need to use char as rule id like:
id : wwwfoobar12345
so i just modify static char *msre_action_id_validate（） in re_actions.c like this:
static char *msre_action_id_validate(msre_engine *engine, apr_pool_t *mp, msre_action *action) {
return NULL;
}
it works well for me but i don't know if it would cause other problems

Well, as far as I know "id" itself is defined as integer in ModSecurity and you might being able to get away with because atoi() is used some times, but I'm not sure as if the string can't be represented after integer conversion it might result in undefined behaviour.
Also, you might have some issues with directives that maybe expects the rule ID on a given format like SecRuleRemoveById as the function might be looking for a range (rule_id_in_range) and I can't say what's the behaviour as I haven't tested :)


"Undefined" is displayed when the kanji form doesn't exist

Hello!
Thanks for the great work on this app. :)
When the word doesn't have a kanji reading the app displays "Undefined"  (for example  こそ https://jisho.org/word/こそ). It's a small issue but it would be nice to display the hiragana form only when it occurs!

Dimitri

It might look like a glitch if the kanji doesn't appear for some words. I don't like the 'undefined' either but it is a placeholder until I can think of something better. Let me know if you have any suggestions!

If there is hiraga, just show the hiragana again. Otherwise just show the katakana again.

If there is hiragana, just show the hiragana again. Otherwise just show the katakana again.

I agree! It would be really nice. :)

Some words aren't any different in kanji than in hiragana. How would this way differentiate those words? I think replacing kanji with hiragana/katakana versions would make it more confusing.
"Not all hiraganas can be replaced with kanjis": https://www.quora.com/When-do-you-know-to-use-Katakana-Hiragana-and-Kanji-when-writing-in-Japanese

Some words aren't any different in kanji than in hiragana. How would this way differentiate those words? I think replacing kanji with hiragana/katakana versions would make it more confusing.
"Not all hiraganas can be replaced with kanjis": https://www.quora.com/When-do-you-know-to-use-Katakana-Hiragana-and-Kanji-when-writing-in-Japanese

I'm not sure I understand what you're saying.
If we look at the screenshot I posted at the beginning, the word  こそ is never written in Kanji and it's only written in Hiragana. (https://jisho.org/word/こそ)
Displaying at the same time both hiragana and katakana for this word is quite confusing.
You should only display the Hiragana (or Katakana if it's relevant) version of the word when there is no related Kanji.

This is fixed on the latest version! Any undefined fields will be replaced by the hiragana.


Migrate prettier/prettier to prettier/pre-commit

Prettier installation is currently broken. See https://github.com/prettier/prettier/issues/9459
Steps to reproduce
Locally
If you have prettier cached, clean with pre-commit uninstall, and run pre-commit again. You will get an error like:
return code: 1
expected return code: 0
stdout: (none)
stderr:
    npm ERR! code ERESOLVE
    npm ERR! ERESOLVE unable to resolve dependency tree
    npm ERR!
    npm ERR! While resolving<EMAIL_ADDRESS>    npm ERR! Found<EMAIL_ADDRESS>    npm ERR! node_modules/@angular/compiler
    npm ERR<EMAIL_ADDRESS>from the root project
    npm ERR!
    npm ERR! Could not resolve dependency:
    npm ERR! peer<EMAIL_ADDRESS>|| ^7.0.0" from<EMAIL_ADDRESS>    npm ERR! node_modules/angular-estree-parser
    npm ERR<EMAIL_ADDRESS>from the root project
    npm ERR!
    npm ERR! Fix the upstream dependency conflict, or retry
    npm ERR! this command with --force, or --legacy-peer-deps
    npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
    npm ERR!

On a CI
If you have a CI system that dynamically pulls and installs prettier in each run, it will happen every time.
Solution
Migrating from https://github.com/prettier/prettier/ to https://github.com/prettier/pre-commit/ (a mirror specifically for pre-commit) solves the problem.
Even if this is a temporary problem, there are plans to fully migrate to prettier/pre-commit in the future (https://github.com/prettier/prettier/pull/8937)
We also need to add extra args and additional_dependencies from upstream prettier in this case (https://github.com/prettier/pre-commit/issues/16#issuecomment-713501862) and add the "v" in the ref because the repo structure is different.
ping @pedrobaeza @sbidoul @Yajo

@sbidoul is there a tool for propagating this change to all repos (13.0 and 14.0)? Is this the problem mentioned in other threads?

is there a tool for propagating this change to all repos

For 14.0 yes, based on copier update. I'll finalize it and push to maintainer-tools it when I push v1.0.3.
For 13.0 it's more difficult.
I see @yajo is involved in the linked prettier issues. Let's wait to see what comes out of it.
@lmignon had a similar issue on one of our private repos this morning and he could resolve it by pinning the node version like we do on the 14.0 branches. That might be enough as a workaround?

Thanks for the response.
Indeed, seems like this issue can be fixed by pinning the npm version: https://github.com/prettier/prettier/issues/9459#issuecomment-714392689 and https://github.com/pre-commit/pre-commit/issues/1655
However, as I mentioned above, there seems to be plans to completely migrate prettier/prettier to prettier/pre-commit. In that case, it would be necessary to make this change anyway.
WDYT @Yajo?

Pinning the npm version means also to change all OCA repos?

I just noticed https://github.com/OCA/oca-addons-repo-template/pull/17
According to https://github.com/pre-commit/pre-commit/issues/1655#issuecomment-714633594, that should fix the issue. I have also tested locally and it seems to work.
As @pedrobaeza was suggesting, how could that be propagated to the repos? Below v13, would that have to be a manual action in each repo?

But if it needs the same propagation, I prefer the definitive patch.

Yes, that would be better, indeed.

Below v13

Below v13 there's no pre-commit, so it doesn't affect. It's just v13.

I just noticed #17

Indeed that's the definitive minimal fix. I just tested locally.

Ok, then what would be the best way to propagate it?

Probably a handcrafted script.

Given what I said above in https://github.com/OCA/oca-addons-repo-template/pull/33#discussion_r510714811 and that #17 was already merged and prevents https://github.com/prettier/prettier/issues/9459 from happening, my vote goes for closing this PR. When we prepare the new templates for v15, we'll see if prettier/pre-commit#18 and prettier/pre-commit#17 are fixed and what to do about it.
Do you agree? Thanks for the patch anyway :blush:

Well, fine by me :smile:
I just wanted a way to fix this... What would be the path to take to that script you mentioned? Would it be something for the OCA Bot?

@sbidoul knows better...

@Yajo what needs to be done exactly? Pin the node version in the 13.0 branches?

That change can be done with https://github.com/OCA/maintainer-tools/pull/442

@Yajo what needs to be done exactly? Pin the node version in the 13.0 branches?

Yes, that's it.

Pin the node version in the 13.0 branches?

This is now applied on all 13.0 branches.

Thank you @sbidoul !


Allow for comments in sematic func docstrings that don't get displayed

Many users expect <!-- some comment --> to hide text from being displayed in Markdown, and Sematic accepts markdown for docstrings. However, comments of that format get displayed. We should suppress them.

In the new version of the Dashboard, the docstring isn't rendered on its own, and the source code renders the entire code + docstring as a conscious choice. Won't do.


No information on the README about the future of this package

This package looks very interesting, and I'd love to make use of it in a real non-testing project.
However, it is quite unclear if after the testing period 1. this will vanish entirely, 2. be available with the same name on pypi, 3. be available with a different name/part of something else on pypi, ...
Can you add some information to the README clarifying where this project is heading, and how much sense it makes to use this for more than just playing around at this stage?

It is on PyPI, and will remain so. It's also used by pip for its PEP 517 implementation, so it's not going away. However, your point about documentation is fair.
The project doesn't really have a full-time maintainer at the moment. @takluyver provided the initial implementation, and I contributed a number of fixes in the process of using it in pip. But neither of us want to take on too much commitment to ongoing management of this project. So one of the key things for sustainability will be to get a good community around the project. That means basically interested people using the code and contributing PRs and enhancements.
To be specific, the code in wrappers.py and the code supporting that is critical to pip, so that will be well-supported (pip will provide plenty of real-world use of that code!). But the other code (in particular envbuild.py) is not yet used in real-world code, and pip's implementation (which was developed independently) has hit a number of corner cases that likely haven't been considered in the code here. So in order for envbuild.py to be production-ready, it will need some work (probably the best approach would be for someone to look at merging this code and pip's implementation of isolated environments, with the intention of pip using the code here, rather than having its own copy. Don't expect me to do that work, though - I doubt I'll have sufficient free time in the near future.
Hopefully, that gives a fair summary of the current state of the project. I don't know how much of that should go in the docs (some of it is too transitory) but I'll see what I can do.

To give a brief update: the wrappers level of functionality is sticking around. The layer above that (envbuild, build, check and meta) is gradually going to be deprecated and eventually removed (#91). The PyPA build project will contain some of this higher-level functionality for setting up an isolated build environment, installing dependencies, and using it to build a package.

I've clarified this in the README.


Helm does not handle resource removal if namespace was changed

I have tiny chart that creates two "services" (can be any other resource). I'm moving one service to other namespace and expect that Helm will delete old one.
Unfortunately, when service moved between namespaces Helm can not handle deletion of old resource, but when i rename resource within same namespaces i see that helm successfully deletes old resource.
Steps to reproduce:

create chart with svc.yaml below
install with helm upgrade --install x-chart x-chart
change namespace of first servcice in svc.yaml from kube-system to default
upgrade chart with helm upgrade --install x-chart x-chart

svc.yaml
kind: Service
apiVersion: v1
metadata:
  name: my-service1
  namespace: default
spec:
  selector:
    app: nginx
  ports:
    - protocol: TCP
      port: 80
      targetPort: 80
---
kind: Service
apiVersion: v1
metadata:
  name: my-service2
  namespace: default
spec:
  selector:
    app: nginx
  ports:
    - protocol: TCP
      port: 80
      targetPort: 80

Actual result:
first service still exists in namespace kube-system
Expected result:
first service deleted from namespace kube-system
Output of helm version:
Client: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.8.1", GitCommit:"6af75a8fd72e2aa18a2b278cfe5c7a1c5feca7f2", GitTreeState:"clean"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.4", GitCommit:"5ca598b4ba5abb89bb773071ce452e33fb66339d", GitTreeState:"clean", BuildDate:"2018-06-06T08:13:03Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.1", GitCommit:"b1b29978270dc22fecc592ac55d903350454310a", GitTreeState:"clean", BuildDate:"2018-07-17T18:43:26Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.): AWS

This is a known limitation of Helm. Helm will not do cross-namespace management, and we do not recommend setting namespace: directly in a template.

Ok, thanks. Do you know the link in the docs, where this mentioned? I did not find it.


Resume/Shuffle Spotify Streams not working

Hello,
I want to use the resume:on option for Spotify Streams. The option can be chosen but if I scan the rfid on the box again the whole systems seems to be not working anymore. Restart is also not working. I have to uncheck the resume option and restart to get the box running again.
Can somebody help me with this issue?
Thanks and best regards
Simon
System: rpi3, USB sound card, gpio buttons, software master branch as of 22.03.2020

I can at least confirm this issue. Noticed it myself while testing other stuff.

Today I had the issue again but not only with resume but also with shuffle mode of a stream.

Its the same for me. Resuming a Spotify-Stream is not possible.
I read on another page that the problem is the float-Number in elapsed time and i modified the script so that there is a convertation from float to integer. But then there are new Problems with stopping the stream.
Is there a solution for this?

@quottax: could you post here what you changed and what errors this has caused?

I added this line in line 93 in resume_play.sh:
ELAPSED=${ELAPSED/\.*}
like this
CURRENTFILENAME=$CURRENTFILENAME
ELAPSED=$ELAPSED
ELAPSED=${ELAPSED/\.*}
PLAYSTATUS="Stopped"
after that it resumes spotify too, but its not stable. So the Stop over RFID doesnt work at any time for example.

@s-martin after installing your suggested script in #700 the resuming/shuffling now is working. So the upgrade to Mopidy 3 will fix this issue in the master branch.

We are upgrading to Mopidy 3 #803, which should fix some issues. PR #804 has been merged. Please try Mopidy 3 by using
cd; rm buster-install-*; wget https://raw.githubusercontent.com/MiczFlor/RPi-Jukebox-RFID/develop/scripts/installscripts/buster-install-mopidy3.sh; chmod +x buster-install-mopidy3.sh; GIT_BRANCH=develop bash ./buster-install-mopidy3.sh

I will close the issue for now.


IPP Everywhere Self-Cert Tool Issue with Roll Media

Canon’s Large Format Printer with Roll-fed media fails with IPP Everywhere Self-Cert Tool 1.1 Update3 (in I-10 Get-Printer-Attributes Operation Test).  Self-Cert Tool expects media-ready="roll_current_609.6x0.0mm“ and our printer is returning "roll_current_609.6x0mm”.
According to PWG 5101.1 in 5.1 Media Size Self-Describing Name Format, a long-dim value of 0 is used for reporting the width of roll-fed media. [long-dim = dim / "0"]  So, "roll_current_609.6x0mm” should be accepted.  Please fix it in IPP Everywhere Self-Cert Tool 1.1.
The Error Message we got from IPP Everywhere Self-Cert Tool 1.1 is:
Error Message:
EXPECTED: media-ready WITH-ALL-VALUES /^(choice(((custom|na|asme|roc|oe|roll)[a-z0-9][-a-z0-9]_([1-9][0-9](.[0-9][1-9])?|0.[0-9][1-9])x([1-9][0-9](.[0-9][1-9])?|0.[0-9][1-9])in|(custom|iso|jis|jpn|prc|om|roll)_[a-z0-9][-a-z0-9]([1-9][0-9](.[0-9][1-9])?|0.[0-9][1-9])x([1-9][0-9](.[0-9][1-9])?|0.[0-9][1-9])mm)){2,}|(custom|na|asme|roc|oe|roll)[a-z0-9][-a-z0-9]_([1-9][0-9](.[0-9][1-9])?|0.[0-9][1-9])x([1-9][0-9](.[0-9][1-9])?|0.[0-9][1-9])in|(custom|iso|jis|jpn|prc|om|roll)_[a-z0-9][-a-z0-9]_([1-9][0-9](.[0-9][1-9])?|0.[0-9][1-9])x([1-9][0-9](.[0-9][1-9])?|0.[0-9][1-9])mm)$/
GOT: media-ready="na_letter_8.5x11in"
GOT: media-ready="roll_current_609.6x0mm"

Dupe of #93.


grpc/ssl handshake fails with a golang server and a c++ client

What version of gRPC and what language are you using?
An golang server and a c++ client
What operating system (Linux, Windows, …) and version?
Ubuntu 14
What runtime / compiler are you using (e.g. python version or version of gcc)
arm linux
What did you do?
If possible, provide a recipe for reproducing the error. Try being specific and include code snippets if helpful.
server.go:
certificate, err := tls.LoadX509KeyPair(${certfile}, ${keyfile})
if err != nil {
    return nil, err
}

// Create a certificate pool from the certificate authority
certPool := x509.NewCertPool()
ca, err := ioutil.ReadFile(${ca_cert})
if err != nil {
    return nil, err
}

// Append the client certificates from the CA
if ok := certPool.AppendCertsFromPEM(ca); !ok {
    return nil, errors.New("failed to append client certs")
}

// Create the TLS credentials
cred := credentials.NewTLS(&tls.Config{
	ClientAuth:   tls.RequireAndVerifyClientCert,
	Certificates: []tls.Certificate{certificate},
	ClientCAs:    certPool,
})

=========================================
C++ client:
 auto contents = [](const std::string& filename) -> std::string {
      std::ifstream fh(filename);
      std::stringstream buffer;
      buffer << fh.rdbuf();
      fh.close();
      return buffer.str();
  };

  auto ssl_options = grpc::SslCredentialsOptions();
  ssl_options.pem_cert_chain = contents(${client-cert});
  ssl_options.pem_private_key = contents(${client-key.pem});
  ssl_options.pem_root_certs = contents(${ca-cert});

  GreeterClient greeter(grpc::CreateChannel(
       "${server_domain_name/common_name}:${port}", grpc::SslCredentials(ssl_options)));
   std::string reply = greeter.SayHello();

What did you expect to see?
client can say hello to server
What did you see instead?
C++ client got: Handshake failed with fatal error SSL_ERROR_SSL: error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
Anything else we should know about your project / environment?
All cert/key file, including CA(self-signed) are generated with openssl tools.
I tested the them with following steps,  which showed that certificates are working good.

openssl verify
openssl s_client -connect xxxx.server.com
go/tls client-server arch.

I digged into the details of grpc, found the error returned from boringssl, which denies the handshake as it verifies the certificates with failure.
However, as I said, I verified certificates with above steps and indicated good on them.
Did I miss some configuration on grpc client or server to get the authentication done?
Thanks

Update trace log:
I0404 20:07:37.299941706    3654 ssl_transport_security.cc:193]                 LOOP - TLS client read_server_certifi  - !!!!!!
I0404 20:07:37.300265372    3654 ssl_transport_security.cc:193]                 LOOP - TLS client read_certificate_st  - !!!!!!
I0404 20:07:37.300314372    3654 ssl_transport_security.cc:193]                 LOOP - TLS client verify_server_certi  - !!!!!!
E0404 20:07:37.301291372    3654 ssl_transport_security.cc:1063] Handshake failed with fatal error SSL_ERROR_SSL: error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED.
D0404 20:07:37.301640372    3654 security_handshaker.cc:129] Security handshake failed: {"created":"@1238875657.301583706","description":"Handshake failed","file":"src/core/lib/security/transport/security_handshaker.cc","file_line":248,"tsi_code":10,"tsi_error":"TSI_PROTOCOL_FAILURE"}
E0404 20:07:37.301964372    3654 lockfree_event.cc:160]      LockfreeEvent::SetShutdown: 0x75a01abc curr=(nil) err={"created":"@1238875657.301583706","description":"Handshake failed","file":"src/core/lib/security/transport/security_handshaker.cc","file_line":248,"tsi_code":10,"tsi_error":"TSI_PROTOCOL_FAILURE"}
E0404 20:07:37.302376039    3654 lockfree_event.cc:160]      LockfreeEvent::SetShutdown: 0x75a01ac0 curr=0x2 err={"created":"@1238875657.301583706","description":"Handshake failed","file":"src/core/lib/security/transport/security_handshaker.cc","file_line":248,"tsi_code":10,"tsi_error":"TSI_PROTOCOL_FAILURE"}
I0404 20:07:37.303013039    3654 combiner.cc:164]            C:0x6baec0 grpc_combiner_execute c=0x6cbb20 last=1
I0404 20:07:37.303394372    3654 handshaker.cc:211]          handshake_manager 0x6bce70: error={"created":"@1238875657.301583706","description":"Handshake failed","file":"src/core/lib/security/transport/security_handshaker.cc","file_line":248,"tsi_code":10,"tsi_error":"TSI_PROTOCOL_FAILURE"} shutdown=0 index=2, args={endpoint=(nil), args=(nil) {size=0: (null)}, read_buffer=(nil) (length=0), exit_early=0}
Thanks

Similar issue with:
https://github.com/grpc/grpc-node/issues/157

Found the reason why ssl verification fails on my arm server, here is the hint if someone sees this kind of issue:
when I use openssl verify to try my arm server from my working PC, I got error like this:
alert bad certificate:s3_pkt.c:1487:SSL alert number 42
Please check the date on both server and client. When generating the certificate, we set a valid period with 3650 or something. Client and server will consider it as a bad certificate if it is expired by checking the clock on host.
Close this issue.
Thanks


App built on Linux does not run on windows

Here is the deal. About a week ago I tried out hover as an alternative build process to the project built in for its advanced packaging support.
The initial test on my app seemed to work well enough, so I started figuring out how to add DLL's and how to handle the plugins I need as app installed on systems with installed VS redist package.
But then I never got to run the result on windows again. I assumed that something is wrong with dependencies until two days ago I decided to step back again and to confirm that tooling works as expected. For the record I am installing app on a virtual machine.
To this end I created a new flutter app using flutter create simple
See the logs below.
Hover doctor
hover: Hover version v0.42.0 running on linux
hover: Sharing flutter version
Flutter 1.21.0-9.1.pre • channel beta • https://github.com/flutter/flutter.git
Framework • revision be9bc8cb39 (3 days ago) • 2020-08-18 09:46:08 -0700
Engine • revision 267070c17a
Tools • Dart 2.10.0 (build 2.10.0-7.2.beta)
hover: Flutter engine commit: https://github.com/flutter/engine/commit/267070c17a6956de1a03dbe09cda56f0c485f41b
hover: Finding out the C compiler version
gcc (GCC) 10.1.0
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

hover: Sharing the content of go.mod
module simple/go

go 1.14

require (
        github.com/go-flutter-desktop/go-flutter v0.41.2
        github.com/pkg/errors v0.9.1
)
hover: Sharing the content of hover.yaml
application-name: ""
executable-name: ""
package-name: ""
license: ""
target: lib/main_desktop.dart
branch: ""
cache-path: ""
opengl: ""
engine-version: ""
hover: Sharing the content of go/cmd
go/cmd/main.go  go/cmd/options.go

Hover output
Using hover build [...] --XXX to build my application, I get the following
output:
➜  simple hover build windows-msi --docker -v
09:46:41 build.go:290: hover: Cleaning the build directory
09:46:42 build.go:335: hover: Building flutter bundle
Font subetting is not supported in debug mode.  Please add it or otherwise you may publish your app with a wrong author. Continuing with `root` as a placeholder author.
docker container: hover: Missing/Empty `license` field in go/hover.yaml. Please add it or otherwise you may publish your app with a wrong license. Continuing with `NOASSERTION` as a placeholder license.
docker container: hover: Packaging msi in /tmp/hover-build-simple-windows-msi221290933
docker container: hover: Generating dynamic build files
docker container: hover: Cleaning the build directory
docker container: Loading simple.wxs...
docker container: Building simple 1.0.0.msi...
docker container: Writing simple 1.0.0.msi...
09:47:11 docker.go:112: hover: Docker run completed

What are the symptoms you are seeing?
The MSI installer works fine. The application gets successfully installed. But it doesn't run. There is no log entry visible through event viewer. There is no console output when running from cmd, I tried added logging into the dart main method but it seems that the executable doesn't get that far either. The linux build works fine.
So I am a bit lost here, because "it doesn't work" is all I can offer.
So as a first step, I would need some guidance to help me gather more information.

@pchampio  @jld3103 @GeertJohan  can somebody please give me some pointers how to collect more information?

Oh I wrote an answer but it somehow disappeard. Sorry for that.
I wrote something like this:

Compile and run the app directly on windows
Cross-compile and the run the app on windows (without packaging)

If something works or not it will be useful to debug it further.

I have been busy elsewhere and I expect to provide required feedback in the next couple of days. I am still very much intereseted and invested in getting hover to work for my use case.

Okay so I took some time to do the testing. Turns out that the build works very well. Even with develop channel.
Turns out the issue was that I was trying to run the app in VM. I expected that it will work since the official embedder does.
Feel free to close this issue.

Duplicate of: https://github.com/go-flutter-desktop/go-flutter/issues/272
You might be able to run it in a vm using: https://github.com/go-flutter-desktop/go-flutter/issues/272#issuecomment-535403717

Hi I built the windows-msi package in UBuntu linux
I ran the installer in another windows machine I have , it got installed but the app didn't run
I got the same issue which @james-lawrence got , not in a vm but a real machine
How do I fix this?

Hi I built the windows-msi package in UBuntu linux
I ran the installer in another windows machine I have , it got installed but the app didn't run
I got the same issue which @james-lawrence got , not in a vm but a real machine
How do I fix this?

Do you have any logs?

Do you have any logs?

This is inside a VM , I ran a build cammand with opengl=none arguement , However it didnt work
$ hover run --opengl=none
hover: Using engine from cache
hover: Cleaning the build directory
hover: ⚠ The go-flutter project tries to stay compatible with the beta channel of Flutter.
hover: ⚠     It's advised to use the beta channel: `flutter channel beta`
hover: Bundling flutter app
Running "flutter pub get" in flutter_app...                      1,307ms

 Building with sound null safety

hover: Checking available release on Github
hover: The core library 'go-flutter' has an update available. (v0.42.0 -> 0.43.0)
hover:               To update 'go-flutter' in this project run: `hover bumpversion`
hover: Checking available release on Github
hover: 'hover' has an update available. (v0.46.1 -> 0.46.2)
hover:               To update 'hover' go to `https://github.com/go-flutter-desktop/hover#install` and follow the install steps
hover: The '--opengl=none' flag makes go-flutter incompatible with texture plugins!
hover: Compiling 'go-flutter' and plugins
hover: Successfully compiled executable binary for windows
hover: Build finished, starting app...
hover: Running flutter_app in debug_unopt mode
creating glfw window: APIUnavailable: WGL: The driver does not appear to support OpenGL
hover: App 'flutter_app' exited with error: exit status 1

This is inside a VM , I ran a build cammand with opengl=none arguement , However it didnt work
$ hover run --opengl=none
hover: Using engine from cache
hover: Cleaning the build directory
hover: ⚠ The go-flutter project tries to stay compatible with the beta channel of Flutter.
hover: ⚠     It's advised to use the beta channel: `flutter channel beta`
hover: Bundling flutter app
Running "flutter pub get" in flutter_app...                      1,307ms

 Building with sound null safety

hover: Checking available release on Github
hover: The core library 'go-flutter' has an update available. (v0.42.0 -> 0.43.0)
hover:               To update 'go-flutter' in this project run: `hover bumpversion`
hover: Checking available release on Github
hover: 'hover' has an update available. (v0.46.1 -> 0.46.2)
hover:               To update 'hover' go to `https://github.com/go-flutter-desktop/hover#install` and follow the install steps
hover: The '--opengl=none' flag makes go-flutter incompatible with texture plugins!
hover: Compiling 'go-flutter' and plugins
hover: Successfully compiled executable binary for windows
hover: Build finished, starting app...
hover: Running flutter_app in debug_unopt mode
creating glfw window: APIUnavailable: WGL: The driver does not appear to support OpenGL
hover: App 'flutter_app' exited with error: exit status 1

Duplicate of: #272
You might be able to run it in a vm using: #272 (comment)

@pchampio already said everything there is about running in a VM

Duplicate of: #272
You might be able to run it in a vm using: #272 (comment)

@pchampio already said everything there is about running in a VM


SideBar background width not respect vs-col

Windows
Node.js 10.14.1
Vuesax 3.8.0
Browser Chrome and Firefox @latest
Which package manager did you use for the install? NPM

The background of SideBar ignores one vs-row -> vs-col vs-w="2" for example and uses 100% of space.

hi @periscuelo, you can send me a image with error?
or implemented code?
thanks

Sure.
https://jsfiddle.net/Ln2vchzq/

how did you remove? I mean what is your full code to remove it?


error patching spotify version <IP_ADDRESS>2.g1924b088-3133

🧐 Have you read the FAQ and viewed similar issues?

[X] I have read the FAQ
[X] I have checked older issues, open and closed
[X] I did a clean install of SpotX as described in the FAQ

Сountry of your account
Philippines
What is your Spotify Plan?
Free
Do you have Spicetify installed?
No
ℹ Computer information
- Spotify: <IP_ADDRESS>2.g1924b088-3133
- Windows: 11 22H2 22621.1702
- PowerShell: 5.1.22621.963

📝 Description

Download and install the latest Spotify version in the excel file (<IP_ADDRESS>2.g1924b088-3133).
Open the Install_Auto.bat file.
An error will show in the Powershell.

📸 Screenshots

Update the bat file


add some retry logic with a delay to check the VM's state

Thanks Frank. Done.
On Sat, Sep 14, 2024 at 2:44 PM liangxiao1 @.***> wrote:

@.**** commented on this pull request.
In os_tests/tests/test_lifecycle.py
https://github.com/virt-s1/os-tests/pull/437#discussion_r1759681706:

@@ -1002,12 +1002,20 @@ def test_reboot_simultaneous(self):

 def _start_vm_and_check(self):
     self.vm.start(wait=True)

   time.sleep(30)

   utils_lib.init_connection(self, timeout=self.ssh_timeout)

   output = utils_lib.run_cmd(self, 'whoami').strip()

   self.assertEqual(self.vm.vm_username,

       output,

       "Start VM error: output of cmd `who` unexpected -> %s" % output)

   time.sleep(60)

   for _ in range(10):

       try:

           utils_lib.init_connection(self, timeout=self.ssh_timeout)

How about increase ssh_timeout to self.ssh_timeout*10 instead of a retry
loop?
Other change looks good to me.
—
Reply to this email directly, view it on GitHub
https://github.com/virt-s1/os-tests/pull/437#pullrequestreview-2304393219,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AY4XWP4PPHFX2IX6VVNO33TZWPLNBAVCNFSM6AAAAABOGSHA32VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDGMBUGM4TGMRRHE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Proposal: I would like to know which plugins I have installed with dtm and their status

Description
As a user, I would like to know which plugins I have installed with dtm and their status by dtm command.
Describe the Proposal
Examples are as follows

dtm list resources gets plugins that I have installed
dtm show states --plugin=argo gets the state of argo plugin
dtm show states --plugin=all  gets the full content of the state file

Has the Feature been Requested Before?
No
Describe the Alternatives You Have Considered
Now all installed plugins and their status are recorded in the state file, which can be read to output the list of installed plugins and their status.
Additional Context
N/A

Great idea!
Status is actually divided into two parts:

The states recorded in the "State Backend"(devstream.state now)
The real status with the resources

So maybe we need a command to get all these two "status".

Command Design:

dtm show status # return all plugins' status
dtm show status --plugin=PLUGIN_NAME # return the status with PLUGIN_NAME

The output message should cover the 2 parts status mentioned above.

If you agree with this implementation idea, I will continue to add the specific design of output information. /cc @devstream-io/devstream

The printing information design
Command: dtm show status --plugin= demo
State (recorded in the state file) == Resource (state got from Read interface)
Name: demo
Plugin: githubactions-golang
Drift: true/false(true if State != Resource)
Options:
     // the options map printed.
Status:
    State: // required
         foo: bar // the state map printed.
    Resource: // only needed when Drift == true
         foo: bar // the resource map printed.

Great. Let's continue with this design.

There are some details that have changed, like --name flag. For more details, please see Test in #410


chore(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/key-protect/ibm (source)
module
patch
v2.3.0 -> v2.3.1

terraform-ibm-modules/resource-group/ibm (source)
module
patch
1.0.5 -> 1.0.6

Release Notes

terraform-ibm-modules/terraform-ibm-key-protect (terraform-ibm-modules/key-protect/ibm)
v2.3.1
Compare Source
Bug Fixes

fixed bug which can cause an error when rotation_enabled is set to false (#425) (41a98fb)

terraform-ibm-modules/terraform-ibm-resource-group (terraform-ibm-modules/resource-group/ibm)
v1.0.6
Compare Source
Bug Fixes

update usage to show hashicorp syntax instead of github (#435) (9469adf)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.13.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


we can use tbb to run multiple static analysis in parallel

actually, we have cpp-takflow integrated.  use that


MessageProducer.InitStatsHandler undefined

When trying to run make build-all from within the k8guard-start-from-here repo, I get the following error coming from the k8guard-discover module:
$ make build-all
cd ../k8guard-discover && make clean
if [ -f k8guard-discover ] ; then rm k8guard-discover ; fi
go clean
cd ../k8guard-discover && make build
CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -ldflags "-X main.Version=`git fetch;git describe --tags > /dev/null 2>&1` -X main.Build=`date +%FT%T%z`" -o k8guard-discover
# github.com/k8guard/k8guard-discover/messaging
messaging/produce.go:43:17: MessageProducer.InitStatsHandler undefined (type types.MessageProducer has no field or method InitStatsHandler)
make[1]: *** [build] Error 2
make: *** [build-discover] Error 2

Kafka_consumer and Kafka_producer changes seem to have been missed from the merge.  Created new PR https://github.com/k8guard/k8guardlibs/pull/20 for k8guard-libs.


Concurrent building of sibling nodes?

I would like to use Broccoli as a build pipeline for a new project, where some tasks are mostly CPU-bound (e.g. processing Docbook-XSL stylesheets with sufficiently large XML inputs).
Given this tree:
I    preprocessing
|\
| A  builder
B |  builder
|/
O    merge results into output

and assuming that both "builder" plugins do return a promise from their build method, will Broccoli build the nodes A and B concurrently?
I'm probably just blind, but I couldn't find any explicit yes or no in the docs... 😅

As @rwjblue mentioned today, the graph of broccoli nodes are topologically sorted and executed serially. The currently recommended approach to achieve CPU parallelism is to do so within each node via a module such as workerpool. (as @rwjblue described above).
The concurrency you describe is a viable option but we have not yet pursued this capability due to pragmatic reasons.
Conceptually the following could be implemented by having a single workerpool which would be provided by broccoli to it's nodes, to ensure node's share available concurrency gracefully. Once this exists, we could either loosen the serial execution constraint across the board or allow plugins to opt into being scheduled concurrently if broccoli deems safe.

I believe concurrent node execution would be a nice feature for another major version of Broccoli, but in the meantime, as it happens, my priorities have shifted so it is no longer a requirement for me personally.
Feel free to close this issue, or keep it around as an informal feature request... 😃


cannot run pyspider!

pyspider version:0.3.10
Operating system:windows10 pro
Start up command: pyspider all

Traceback (most recent call last):
File "C:\Users\dell\AppData\Local\Programs\Python\Python37-32\lib\runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "C:\Users\dell\AppData\Local\Programs\Python\Python37-32\lib\runpy.py", line 85, in run_code
exec(code, run_globals)
File "C:\Users\dell\Documents\bia660\study\venv\Scripts\pyspider.exe_main.py", line 5, in
File "c:\users\dell\documents\bia660\study\venv\lib\site-packages\pyspider\run.py", line 231
async=True, get_object=False, no_input=False):
^
SyntaxError: invalid syntax

does anyone know what happen with the pyspider? when i enter command "pyspider all" to let it run , it shows above error message.

the some issue on macOS Mojave 10.14.6

Same on Ubuntu

update:
i have already addressed this problem by substituting  all the "async" pyspider's scripts for "async_", the reason why i did this is that python3.7 have set "async" to a keyword, so it will occur this syntax problem, so just change "async" to other word, it will help.

@HammerChen, @weet-bred

async is the keyword in python3.7

。。。

Same here.

how to solve it in linux, help

There are several places in code, some change asyn to async_mode, some change async to async_fetch

Same here. Running inside a python 3.7 container:
root@36c71decd081:/# pyspider
Traceback (most recent call last):
File "/usr/local/bin/pyspider", line 5, in
from pyspider.run import main
File "/usr/local/lib/python3.7/site-packages/pyspider/run.py", line 231
async=True, get_object=False, no_input=False):
^
SyntaxError: invalid syntax
root@36c71decd081:/# ls
bin  boot  dev	etc  home  lib	media  mnt  opt  proc  root  run  sbin	srv  sys  tmp  usr  var
root@36c71decd081:/# python
Python 3.7.17 (default, Sep 20 2023, 21:49:50)
[GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.


Potential encoding issue

From Test Flight feedback:

This RSS feed has encoding UTF-8. The description elements embed HTML inside CDATA and NetNewsWire appears to interpret the CDATA blocks as latin1.

Weird; it's showing up correctly for me on desktop build from master.

I can't repro on iPhone either, with build 44. Maybe they fixed their feed?

If we aren't seeing it in build 44, I don't think this is something we need to worry about.


Popover blocking ui when there is a conditional render

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example:
https://codesandbox.io/s/popover-bug-test-1-ymcvrn?file=/demo.tsx
Steps:
Resize from width >500 to <500 and click "open popover on small" - nothing happens (blocked by a popover div MuiModal-root-MuiPopover-root).
Change mui to version 5.10.16 and it works.
First broken in 5.10.17
Tried latest 5.11.11 and it also blocks.
Probably a race condition between how both the 'open' and 'isMd' flag control the Popover.
Current behavior 😯
blocks rest of ui
Expected behavior 🤔
doesn't block
Context 🔦
We have a popover that only shows on mobile. We have a way to fix our use case (see commented out setOpen(false) in code sandbox).
Your environment 🌎
See codesandbox. Tried with Chrome.

Rather than conditionally rendering depending on the value of isMd, I'd suggest you to pass open && isMd to the open prop of your custom Popover component.
Here is a refactored version: https://codesandbox.io/s/popover-bug-test-1-forked-99s41w?file=/demo.tsx