chore: remove npx's node_modules/.bin after dependencies installation

This is a subtle issue I just discovered. npx is a tool to
automatically run a program inside ./node_modules/.bin. The issue is
that when it runs, it prepends its own local .bin to the PATH, and
if any of npx's dependencies have binaries (which they do), npx will
incorrectly use those instead of the ones we configure in our top level
package.json.
In my particular case, npx's npm was being executed instead of the
system's one. I wonder if this explains the weird shrinkwrap
discrepancies in certain operating systems.
Change-Type: patch
Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

The issue is that when it runs, it prepends its own local .bin to the PATH, and if any of npx's dependencies have binaries (which they do), npx will incorrectly use those

Hmmm, that's kind of a pain :-/  Is this a "by design" feature of npx @jhermsmeier , and/or is there a way to work around this?
CI builds are now failing with e.g.
cd dist/Etcher-cli-1.2.1+c95df54-win32-x64-app && ../.././node_modules/.bin/npx pkg --output ../../dist/Etcher-cli-1.2.1+c95df54-win32-x64/etcher.exe -t node6-win-x64 lib/cli/etcher.js
not found: c:\projects\etcher\node_modules\npx\node_modules\.bin\npm
make: *** [dist/Etcher-cli-1.2.1+c95df54-win32-x64] Error 1

Given that (IIRC) npx is only used in the Makefile, perhaps a better fix for this would be getting rid of npx altogether, and instead doing something like:
--- a/Makefile
+++ b/Makefile
@@ -2,7 +2,7 @@
 # Build configuration
 # ---------------------------------------------------------------------

-NPX = ./node_modules/.bin/npx
+PATH := $(shell pwd)/node_modules/.bin:$(PATH)

 # This directory will be completely deleted by the `clean` rule
 BUILD_DIRECTORY ?= dist
@@ -231,7 +231,7 @@ $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-cli-$(APPLICATION_VERSION)-$(PLATFORM)-$(
        $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-cli-$(APPLICATION_VERSION)-$(PLATFORM)-$(TARGET_ARCH)-app \
        | $(BUILD_DIRECTORY)
        mkdir $@
-       cd $< && ../../$(NPX) pkg --output ../../$@/$(ETCHER_CLI_BINARY) -t node6-$(PLATFORM_PKG)-$(TARGET_ARCH) $(ENTRY_POINT_CLI)
+       cd $< && pkg --output ../../$@/$(ETCHER_CLI_BINARY) -t node6-$(PLATFORM_PKG)-$(TARGET_ARCH) $(ENTRY_POINT_CLI)
        ./scripts/build/dependencies-npm-extract-addons.sh \
                -d $</node_modules \
                -o $@/node_modules
@@ -287,13 +287,13 @@ assets/osx/installer.tiff: assets/osx/installer.png<EMAIL_ADDRESS>
 $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-$(APPLICATION_VERSION).dmg: assets/osx/installer.tiff \
        | $(BUILD_DIRECTORY)
-       TARGET_ARCH=$(TARGET_ARCH) $(NPX) build --mac dmg $(ELECTRON_BUILDER_OPTIONS) \
+       TARGET_ARCH=$(TARGET_ARCH) build --mac dmg $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.version=$(APPLICATION_VERSION) \
                --extraMetadata.packageType=dmg

 $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-$(APPLICATION_VERSION)-mac.zip: assets/osx/installer.tiff \
        | $(BUILD_DIRECTORY)
-       TARGET_ARCH=$(TARGET_ARCH) $(NPX) build --mac zip $(ELECTRON_BUILDER_OPTIONS) \
+       TARGET_ARCH=$(TARGET_ARCH) build --mac zip $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.version=$(APPLICATION_VERSION) \
                --extraMetadata.packageType=zip

@@ -301,7 +301,7 @@ APPLICATION_NAME_ELECTRON = $(APPLICATION_NAME_LOWERCASE)-electron

 $(BUILD_DIRECTORY)/$(APPLICATION_NAME_ELECTRON)-$(APPLICATION_VERSION_REDHAT).$(TARGET_ARCH_REDHAT).rpm: \
        | $(BUILD_DIRECTORY)
-       $(NPX) build --linux rpm $(ELECTRON_BUILDER_OPTIONS) \
+       build --linux rpm $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.name=$(APPLICATION_NAME_ELECTRON) \
                --extraMetadata.version=$(APPLICATION_VERSION_REDHAT) \
                --extraMetadata.packageType=rpm \
@@ -309,7 +309,7 @@ $(BUILD_DIRECTORY)/$(APPLICATION_NAME_ELECTRON)-$(APPLICATION_VERSION_REDHAT).$(

 $(BUILD_DIRECTORY)/$(APPLICATION_NAME_ELECTRON)_$(APPLICATION_VERSION_DEBIAN)_$(TARGET_ARCH_DEBIAN).deb: \
        | $(BUILD_DIRECTORY)
-       $(NPX) build --linux deb $(ELECTRON_BUILDER_OPTIONS) \
+       build --linux deb $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.name=$(APPLICATION_NAME_ELECTRON) \
                --extraMetadata.version=$(APPLICATION_VERSION_DEBIAN) \
                --extraMetadata.packageType=deb \
@@ -322,7 +322,7 @@ ELECTRON_BUILDER_LINUX_UNPACKED_DIRECTORY = linux-$(TARGET_ARCH_ELECTRON_BUILDER
 endif

 $(BUILD_DIRECTORY)/$(ELECTRON_BUILDER_LINUX_UNPACKED_DIRECTORY)/$(APPLICATION_NAME_ELECTRON): | $(BUILD_DIRECTORY)
-       $(NPX) build --dir --linux $(ELECTRON_BUILDER_OPTIONS) \
+       build --dir --linux $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.name=$(APPLICATION_NAME_ELECTRON) \
                --extraMetadata.version=$(APPLICATION_VERSION) \
                --extraMetadata.packageType=AppImage
@@ -356,13 +356,13 @@ $(BUILD_DIRECTORY)/$(APPLICATION_NAME_LOWERCASE)-$(APPLICATION_VERSION)-$(PLATFO

 $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-Portable-$(APPLICATION_VERSION)-$(TARGET_ARCH).exe: \
        | $(BUILD_DIRECTORY)
-       TARGET_ARCH=$(TARGET_ARCH) $(NPX) build --win portable $(ELECTRON_BUILDER_OPTIONS) \
+       TARGET_ARCH=$(TARGET_ARCH) build --win portable $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.version=$(APPLICATION_VERSION) \
                --extraMetadata.packageType=portable

 $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-Setup-$(APPLICATION_VERSION)-$(TARGET_ARCH).exe: \
        | $(BUILD_DIRECTORY)
-       TARGET_ARCH=$(TARGET_ARCH) $(NPX) build --win nsis $(ELECTRON_BUILDER_OPTIONS) \
+       TARGET_ARCH=$(TARGET_ARCH) build --win nsis $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.version=$(APPLICATION_VERSION) \
                --extraMetadata.packageType=nsis

@@ -395,10 +395,10 @@ TARGETS = \
        electron-develop

 changelog:
-       $(NPX) versionist
+       versionist

 package-electron:
-       TARGET_ARCH=$(TARGET_ARCH) $(NPX) build --dir $(ELECTRON_BUILDER_OPTIONS)
+       TARGET_ARCH=$(TARGET_ARCH) build --dir $(ELECTRON_BUILDER_OPTIONS)

 package-cli: $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-cli-$(APPLICATION_VERSION)-$(PLATFORM)-$(TARGET_ARCH)

@@ -524,13 +524,13 @@ electron-develop:
                -s "$(PLATFORM)"

 sass:
-       $(NPX) node-sass lib/gui/scss/main.scss > lib/gui/css/main.css
+       node-sass lib/gui/scss/main.scss > lib/gui/css/main.css

 lint-js:
-       $(NPX) eslint lib tests scripts bin versionist.conf.js
+       eslint lib tests scripts bin versionist.conf.js

 lint-sass:
-       $(NPX) sass-lint lib/gui/scss
+       sass-lint lib/gui/scss

 lint-cpp:
        cpplint --recursive src
@@ -550,15 +550,15 @@ lint: lint-js lint-sass lint-cpp lint-html lint-spell
 MOCHA_OPTIONS=--recursive --reporter spec

 test-spectron:
-       $(NPX) env \
+       env \
                ETCHER_SPECTRON_ENTRYPOINT=$(ETCHER_SPECTRON_ENTRYPOINT) \
                mocha $(MOCHA_OPTIONS) tests/spectron

 test-gui:
-       $(NPX) electron-mocha $(MOCHA_OPTIONS) --renderer tests/gui
+       electron-mocha $(MOCHA_OPTIONS) --renderer tests/gui

 test-sdk:
-       $(NPX) electron-mocha $(MOCHA_OPTIONS) \
+       electron-mocha $(MOCHA_OPTIONS) \
                tests/shared \
                tests/child-writer \
                tests/image-stream

This works fine for me on Linux (both locally and in the Docker containers), but this hasn't been tested on Mac or Windows.
Holy cow, removing npx also gets rid of over 2,500 lines (almost 500 modules) from the npm-shrinkwrap.json file!

Yeah, getting rid of npx might be a good way to go. I'll open a PR with
your patch, so we can have the CI services check if all works fine.
On Fri, Dec 15, 2017 at 05:41:18PM -0800, Andrew Scheller wrote:

The issue is that when it runs, it prepends its own local .bin to the PATH, and if any of npx's dependencies have binaries (which they do), npx will incorrectly use those

Hmmm, that's kind of a pain :-/  Is this a "by design" feature of npx @jhermsmeier , and/or is there a way to work around this?
CI builds are now failing with e.g.
cd dist/Etcher-cli-1.2.1+c95df54-win32-x64-app && ../.././node_modules/.bin/npx pkg --output ../../dist/Etcher-cli-1.2.1+c95df54-win32-x64/etcher.exe -t node6-win-x64 lib/cli/etcher.js
not found: c:\projects\etcher\node_modules\npx\node_modules\.bin\npm
make: *** [dist/Etcher-cli-1.2.1+c95df54-win32-x64] Error 1

Given that (IIRC) npx is only used in the Makefile, perhaps a better fix for this would be getting rid of npx altogether, and instead doing something like:
--- a/Makefile
+++ b/Makefile
@@ -2,7 +2,7 @@
 # Build configuration
 # ---------------------------------------------------------------------

-NPX = ./node_modules/.bin/npx
+PATH := $(shell pwd)/node_modules/.bin:$(PATH)

 # This directory will be completely deleted by the `clean` rule
 BUILD_DIRECTORY ?= dist
@@ -231,7 +231,7 @@ $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-cli-$(APPLICATION_VERSION)-$(PLATFORM)-$(
        $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-cli-$(APPLICATION_VERSION)-$(PLATFORM)-$(TARGET_ARCH)-app \
        | $(BUILD_DIRECTORY)
        mkdir $@
-       cd $< && ../../$(NPX) pkg --output ../../$@/$(ETCHER_CLI_BINARY) -t node6-$(PLATFORM_PKG)-$(TARGET_ARCH) $(ENTRY_POINT_CLI)
+       cd $< && pkg --output ../../$@/$(ETCHER_CLI_BINARY) -t node6-$(PLATFORM_PKG)-$(TARGET_ARCH) $(ENTRY_POINT_CLI)
        ./scripts/build/dependencies-npm-extract-addons.sh \
                -d $</node_modules \
                -o $@/node_modules
@@ -287,13 +287,13 @@ assets/osx/installer.tiff: assets/osx/installer.png<EMAIL_ADDRESS>
 $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-$(APPLICATION_VERSION).dmg: assets/osx/installer.tiff \
        | $(BUILD_DIRECTORY)
-       TARGET_ARCH=$(TARGET_ARCH) $(NPX) build --mac dmg $(ELECTRON_BUILDER_OPTIONS) \
+       TARGET_ARCH=$(TARGET_ARCH) build --mac dmg $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.version=$(APPLICATION_VERSION) \
                --extraMetadata.packageType=dmg

 $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-$(APPLICATION_VERSION)-mac.zip: assets/osx/installer.tiff \
        | $(BUILD_DIRECTORY)
-       TARGET_ARCH=$(TARGET_ARCH) $(NPX) build --mac zip $(ELECTRON_BUILDER_OPTIONS) \
+       TARGET_ARCH=$(TARGET_ARCH) build --mac zip $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.version=$(APPLICATION_VERSION) \
                --extraMetadata.packageType=zip

@@ -301,7 +301,7 @@ APPLICATION_NAME_ELECTRON = $(APPLICATION_NAME_LOWERCASE)-electron

 $(BUILD_DIRECTORY)/$(APPLICATION_NAME_ELECTRON)-$(APPLICATION_VERSION_REDHAT).$(TARGET_ARCH_REDHAT).rpm: \
        | $(BUILD_DIRECTORY)
-       $(NPX) build --linux rpm $(ELECTRON_BUILDER_OPTIONS) \
+       build --linux rpm $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.name=$(APPLICATION_NAME_ELECTRON) \
                --extraMetadata.version=$(APPLICATION_VERSION_REDHAT) \
                --extraMetadata.packageType=rpm \
@@ -309,7 +309,7 @@ $(BUILD_DIRECTORY)/$(APPLICATION_NAME_ELECTRON)-$(APPLICATION_VERSION_REDHAT).$(

 $(BUILD_DIRECTORY)/$(APPLICATION_NAME_ELECTRON)_$(APPLICATION_VERSION_DEBIAN)_$(TARGET_ARCH_DEBIAN).deb: \
        | $(BUILD_DIRECTORY)
-       $(NPX) build --linux deb $(ELECTRON_BUILDER_OPTIONS) \
+       build --linux deb $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.name=$(APPLICATION_NAME_ELECTRON) \
                --extraMetadata.version=$(APPLICATION_VERSION_DEBIAN) \
                --extraMetadata.packageType=deb \
@@ -322,7 +322,7 @@ ELECTRON_BUILDER_LINUX_UNPACKED_DIRECTORY = linux-$(TARGET_ARCH_ELECTRON_BUILDER
 endif

 $(BUILD_DIRECTORY)/$(ELECTRON_BUILDER_LINUX_UNPACKED_DIRECTORY)/$(APPLICATION_NAME_ELECTRON): | $(BUILD_DIRECTORY)
-       $(NPX) build --dir --linux $(ELECTRON_BUILDER_OPTIONS) \
+       build --dir --linux $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.name=$(APPLICATION_NAME_ELECTRON) \
                --extraMetadata.version=$(APPLICATION_VERSION) \
                --extraMetadata.packageType=AppImage
@@ -356,13 +356,13 @@ $(BUILD_DIRECTORY)/$(APPLICATION_NAME_LOWERCASE)-$(APPLICATION_VERSION)-$(PLATFO

 $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-Portable-$(APPLICATION_VERSION)-$(TARGET_ARCH).exe: \
        | $(BUILD_DIRECTORY)
-       TARGET_ARCH=$(TARGET_ARCH) $(NPX) build --win portable $(ELECTRON_BUILDER_OPTIONS) \
+       TARGET_ARCH=$(TARGET_ARCH) build --win portable $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.version=$(APPLICATION_VERSION) \
                --extraMetadata.packageType=portable

 $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-Setup-$(APPLICATION_VERSION)-$(TARGET_ARCH).exe: \
        | $(BUILD_DIRECTORY)
-       TARGET_ARCH=$(TARGET_ARCH) $(NPX) build --win nsis $(ELECTRON_BUILDER_OPTIONS) \
+       TARGET_ARCH=$(TARGET_ARCH) build --win nsis $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.version=$(APPLICATION_VERSION) \
                --extraMetadata.packageType=nsis

@@ -395,10 +395,10 @@ TARGETS = \
        electron-develop

 changelog:
-       $(NPX) versionist
+       versionist

 package-electron:
-       TARGET_ARCH=$(TARGET_ARCH) $(NPX) build --dir $(ELECTRON_BUILDER_OPTIONS)
+       TARGET_ARCH=$(TARGET_ARCH) build --dir $(ELECTRON_BUILDER_OPTIONS)

 package-cli: $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-cli-$(APPLICATION_VERSION)-$(PLATFORM)-$(TARGET_ARCH)

@@ -524,13 +524,13 @@ electron-develop:
                -s "$(PLATFORM)"

 sass:
-       $(NPX) node-sass lib/gui/scss/main.scss > lib/gui/css/main.css
+       node-sass lib/gui/scss/main.scss > lib/gui/css/main.css

 lint-js:
-       $(NPX) eslint lib tests scripts bin versionist.conf.js
+       eslint lib tests scripts bin versionist.conf.js

 lint-sass:
-       $(NPX) sass-lint lib/gui/scss
+       sass-lint lib/gui/scss

 lint-cpp:
        cpplint --recursive src
@@ -550,15 +550,15 @@ lint: lint-js lint-sass lint-cpp lint-html lint-spell
 MOCHA_OPTIONS=--recursive --reporter spec

 test-spectron:
-       $(NPX) env \
+       env \
                ETCHER_SPECTRON_ENTRYPOINT=$(ETCHER_SPECTRON_ENTRYPOINT) \
                mocha $(MOCHA_OPTIONS) tests/spectron

 test-gui:
-       $(NPX) electron-mocha $(MOCHA_OPTIONS) --renderer tests/gui
+       electron-mocha $(MOCHA_OPTIONS) --renderer tests/gui

 test-sdk:
-       $(NPX) electron-mocha $(MOCHA_OPTIONS) \
+       electron-mocha $(MOCHA_OPTIONS) \
                tests/shared \
                tests/child-writer \
                tests/image-stream

This works fine for me on Linux (both locally and in the Docker containers), but this hasn't been tested on Mac or Windows.
Holy cow, removing npx also gets rid of over 2,500 lines (almost 500 modules) from the npm-shrinkwrap.json file!
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/resin-io/etcher/pull/1925#issuecomment-352151228

--
Juan Cruz Viotti
Software Engineer

PR sent: https://github.com/resin-io/etcher/pull/1929. Lets see how it
goes :)
On Fri, Dec 15, 2017 at 05:41:18PM -0800, Andrew Scheller wrote:

The issue is that when it runs, it prepends its own local .bin to the PATH, and if any of npx's dependencies have binaries (which they do), npx will incorrectly use those

Hmmm, that's kind of a pain :-/  Is this a "by design" feature of npx @jhermsmeier , and/or is there a way to work around this?
CI builds are now failing with e.g.
cd dist/Etcher-cli-1.2.1+c95df54-win32-x64-app && ../.././node_modules/.bin/npx pkg --output ../../dist/Etcher-cli-1.2.1+c95df54-win32-x64/etcher.exe -t node6-win-x64 lib/cli/etcher.js
not found: c:\projects\etcher\node_modules\npx\node_modules\.bin\npm
make: *** [dist/Etcher-cli-1.2.1+c95df54-win32-x64] Error 1

Given that (IIRC) npx is only used in the Makefile, perhaps a better fix for this would be getting rid of npx altogether, and instead doing something like:
--- a/Makefile
+++ b/Makefile
@@ -2,7 +2,7 @@
 # Build configuration
 # ---------------------------------------------------------------------

-NPX = ./node_modules/.bin/npx
+PATH := $(shell pwd)/node_modules/.bin:$(PATH)

 # This directory will be completely deleted by the `clean` rule
 BUILD_DIRECTORY ?= dist
@@ -231,7 +231,7 @@ $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-cli-$(APPLICATION_VERSION)-$(PLATFORM)-$(
        $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-cli-$(APPLICATION_VERSION)-$(PLATFORM)-$(TARGET_ARCH)-app \
        | $(BUILD_DIRECTORY)
        mkdir $@
-       cd $< && ../../$(NPX) pkg --output ../../$@/$(ETCHER_CLI_BINARY) -t node6-$(PLATFORM_PKG)-$(TARGET_ARCH) $(ENTRY_POINT_CLI)
+       cd $< && pkg --output ../../$@/$(ETCHER_CLI_BINARY) -t node6-$(PLATFORM_PKG)-$(TARGET_ARCH) $(ENTRY_POINT_CLI)
        ./scripts/build/dependencies-npm-extract-addons.sh \
                -d $</node_modules \
                -o $@/node_modules
@@ -287,13 +287,13 @@ assets/osx/installer.tiff: assets/osx/installer.png<EMAIL_ADDRESS>
 $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-$(APPLICATION_VERSION).dmg: assets/osx/installer.tiff \
        | $(BUILD_DIRECTORY)
-       TARGET_ARCH=$(TARGET_ARCH) $(NPX) build --mac dmg $(ELECTRON_BUILDER_OPTIONS) \
+       TARGET_ARCH=$(TARGET_ARCH) build --mac dmg $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.version=$(APPLICATION_VERSION) \
                --extraMetadata.packageType=dmg

 $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-$(APPLICATION_VERSION)-mac.zip: assets/osx/installer.tiff \
        | $(BUILD_DIRECTORY)
-       TARGET_ARCH=$(TARGET_ARCH) $(NPX) build --mac zip $(ELECTRON_BUILDER_OPTIONS) \
+       TARGET_ARCH=$(TARGET_ARCH) build --mac zip $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.version=$(APPLICATION_VERSION) \
                --extraMetadata.packageType=zip

@@ -301,7 +301,7 @@ APPLICATION_NAME_ELECTRON = $(APPLICATION_NAME_LOWERCASE)-electron

 $(BUILD_DIRECTORY)/$(APPLICATION_NAME_ELECTRON)-$(APPLICATION_VERSION_REDHAT).$(TARGET_ARCH_REDHAT).rpm: \
        | $(BUILD_DIRECTORY)
-       $(NPX) build --linux rpm $(ELECTRON_BUILDER_OPTIONS) \
+       build --linux rpm $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.name=$(APPLICATION_NAME_ELECTRON) \
                --extraMetadata.version=$(APPLICATION_VERSION_REDHAT) \
                --extraMetadata.packageType=rpm \
@@ -309,7 +309,7 @@ $(BUILD_DIRECTORY)/$(APPLICATION_NAME_ELECTRON)-$(APPLICATION_VERSION_REDHAT).$(

 $(BUILD_DIRECTORY)/$(APPLICATION_NAME_ELECTRON)_$(APPLICATION_VERSION_DEBIAN)_$(TARGET_ARCH_DEBIAN).deb: \
        | $(BUILD_DIRECTORY)
-       $(NPX) build --linux deb $(ELECTRON_BUILDER_OPTIONS) \
+       build --linux deb $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.name=$(APPLICATION_NAME_ELECTRON) \
                --extraMetadata.version=$(APPLICATION_VERSION_DEBIAN) \
                --extraMetadata.packageType=deb \
@@ -322,7 +322,7 @@ ELECTRON_BUILDER_LINUX_UNPACKED_DIRECTORY = linux-$(TARGET_ARCH_ELECTRON_BUILDER
 endif

 $(BUILD_DIRECTORY)/$(ELECTRON_BUILDER_LINUX_UNPACKED_DIRECTORY)/$(APPLICATION_NAME_ELECTRON): | $(BUILD_DIRECTORY)
-       $(NPX) build --dir --linux $(ELECTRON_BUILDER_OPTIONS) \
+       build --dir --linux $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.name=$(APPLICATION_NAME_ELECTRON) \
                --extraMetadata.version=$(APPLICATION_VERSION) \
                --extraMetadata.packageType=AppImage
@@ -356,13 +356,13 @@ $(BUILD_DIRECTORY)/$(APPLICATION_NAME_LOWERCASE)-$(APPLICATION_VERSION)-$(PLATFO

 $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-Portable-$(APPLICATION_VERSION)-$(TARGET_ARCH).exe: \
        | $(BUILD_DIRECTORY)
-       TARGET_ARCH=$(TARGET_ARCH) $(NPX) build --win portable $(ELECTRON_BUILDER_OPTIONS) \
+       TARGET_ARCH=$(TARGET_ARCH) build --win portable $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.version=$(APPLICATION_VERSION) \
                --extraMetadata.packageType=portable

 $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-Setup-$(APPLICATION_VERSION)-$(TARGET_ARCH).exe: \
        | $(BUILD_DIRECTORY)
-       TARGET_ARCH=$(TARGET_ARCH) $(NPX) build --win nsis $(ELECTRON_BUILDER_OPTIONS) \
+       TARGET_ARCH=$(TARGET_ARCH) build --win nsis $(ELECTRON_BUILDER_OPTIONS) \
                --extraMetadata.version=$(APPLICATION_VERSION) \
                --extraMetadata.packageType=nsis

@@ -395,10 +395,10 @@ TARGETS = \
        electron-develop

 changelog:
-       $(NPX) versionist
+       versionist

 package-electron:
-       TARGET_ARCH=$(TARGET_ARCH) $(NPX) build --dir $(ELECTRON_BUILDER_OPTIONS)
+       TARGET_ARCH=$(TARGET_ARCH) build --dir $(ELECTRON_BUILDER_OPTIONS)

 package-cli: $(BUILD_DIRECTORY)/$(APPLICATION_NAME)-cli-$(APPLICATION_VERSION)-$(PLATFORM)-$(TARGET_ARCH)

@@ -524,13 +524,13 @@ electron-develop:
                -s "$(PLATFORM)"

 sass:
-       $(NPX) node-sass lib/gui/scss/main.scss > lib/gui/css/main.css
+       node-sass lib/gui/scss/main.scss > lib/gui/css/main.css

 lint-js:
-       $(NPX) eslint lib tests scripts bin versionist.conf.js
+       eslint lib tests scripts bin versionist.conf.js

 lint-sass:
-       $(NPX) sass-lint lib/gui/scss
+       sass-lint lib/gui/scss

 lint-cpp:
        cpplint --recursive src
@@ -550,15 +550,15 @@ lint: lint-js lint-sass lint-cpp lint-html lint-spell
 MOCHA_OPTIONS=--recursive --reporter spec

 test-spectron:
-       $(NPX) env \
+       env \
                ETCHER_SPECTRON_ENTRYPOINT=$(ETCHER_SPECTRON_ENTRYPOINT) \
                mocha $(MOCHA_OPTIONS) tests/spectron

 test-gui:
-       $(NPX) electron-mocha $(MOCHA_OPTIONS) --renderer tests/gui
+       electron-mocha $(MOCHA_OPTIONS) --renderer tests/gui

 test-sdk:
-       $(NPX) electron-mocha $(MOCHA_OPTIONS) \
+       electron-mocha $(MOCHA_OPTIONS) \
                tests/shared \
                tests/child-writer \
                tests/image-stream

This works fine for me on Linux (both locally and in the Docker containers), but this hasn't been tested on Mac or Windows.
Holy cow, removing npx also gets rid of over 2,500 lines (almost 500 modules) from the npm-shrinkwrap.json file!
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/resin-io/etcher/pull/1925#issuecomment-352151228

--
Juan Cruz Viotti
Software Engineer

This has been superseded by https://github.com/resin-io/etcher/pull/1929


Conditional non-weapon gear transmog.

This plugin already allows weapon model swaps based on the item you are wielding, so a lot of the groundwork for conditional gear transmog applying to any slot already exists.
This should support multiple transmogged slots per "trigger item" - e.g. if you want your void setup to swap the chest and legs to bandos despite only changing the head slot.
For shields, this can be done in the same swap as weapon swaps are - this is good for supporting mogging a 2h weapon to a 1h + shield, or hiding the offhand when transmogging from 1h to 2h, or for wielding a 2h weapon with a shield because it looks dumb and is funny. But changing shields should still exist separately. It is also important to remember that shields change the "defend" animation, and whether this should happen should be configurable.

This has been added, minus the "defend" animation.


pulsar-shell persistent modes

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
Using pulsar-shell interactively, it's kind of a pain to prefix everything withadmin. I think it would be nice if the command accepted admin and client on their own as special commands that put the command into that mode with an implicit prefix.
Solution
Allow admin and client, when passed on their own to enter into admin or client mode respectively, with the addition of one more command exitmode to return to the base state. These modes would not persist between sessions.
configname(hostname)> admin
configname(hostname) admin> help
Usage: pulsar-admin [options] [command] [command options]
  Options:
    --admin-url
      Admin Service URL to which to connect.
      Default: https://pulsar.eks.intel.cs.sys:443
<SNIP>
    namespaces      Operations about namespaces
      Usage: namespaces [options]

configname(hostname) admin> exitmode
configname(hostname)>

Alternatives
No response
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Seems like a good first issue that I'm willing to tackle! Could you assign it to me?


Spacing for Return Types

For PHP 7, the format for adding return types appears to be of the format:
function foo( $arg ): array {
This format of characters and whitespace between ) and { can be seen in examples on:

PHP Manual
PHP Return Type RFC
Draft PSR-12
SitePoint example.
This blog post
And this blog post (which has no space after the return type.)

Just for a counter-argument, this post puts a space before the :.
Regardless, the current WPCS flags up ): as Expected one space after closing parenthesis. It doesn't flag up no space between the return type and {.
We, as WPCS, either need to make a decision that ): array { is correct for the WordPress community, or that particular combination of characters / tokens should be excluded from whitespace checks until TPTB have updated the coding standards.

It seems pretty clear-cut to me that there should be a space before the opening bracket. I think it wold be really inconsistent for WP not to adopt that (54 years from now :-).
As far as the space after the closing parenthesis, I think we should just allow it to be configured either way, but not flag it by default.

This error partly comes from an upstream sniff:
 3 | ERROR | [x] Expected 1 space after closing parenthesis; found 0
   |       |     (Generic.Functions.OpeningFunctionBraceKernighanRitchie.SpaceAfterBracket)

So partly this is because PHPCS doesn't fully support PHP 7 yet, I think. Although I also get this from our sniffs:
 3 | ERROR | [x] Space between opening control structure and closing
   |       |     parenthesis is required
   |       |     (WordPress.WhiteSpace.ControlStructureSpacing.NoSpaceAfterCloseParenthesis)

Also, it looks like WordPress.Arrays.ArrayDeclaration isn't compatible with PHP 7:
 1 | ERROR | [x] Expected 1 space after array opener, found 1.
   |       |     (WordPress.Arrays.ArrayDeclaration.SpaceAfterArrayOpener)
 1 | ERROR | [x] Missing space before array closer.
   |       |     (WordPress.Arrays.ArrayDeclaration.NoSpaceAfterOpenParenthesis)
 3 | ERROR | [x] There must be no space between the "array" keyword and
   |       |     the opening parenthesis
   |       |     (WordPress.Arrays.ArrayDeclaration.SpaceAfterKeyword)

Most of the rest of the PHP World uses no space for return types, but the WP historical code style would suggest using a space.

Always put spaces after commas, and on both sides of logical, comparison, string and assignment operators.
-- https://make.wordpress.org/core/handbook/best-practices/coding-standards/php/#space-usage

My preference, is that for something "relatively" new (and not yet found in WP core, or many plugins) that there's a good case for sticking with no-space:

default auto-formatting by IDEs just works - many may not even have an option to include a space there,
examples in WP and PHP tutorials match,
possibly able to inherit a sniff from an existing standard to check this, instead of having to write a current one (which in turn means it could be added to a ruleset far quicker and adopted consistently in the community).

In terms of the space before the : for the return type, the Handbook explicitly says that the case in a switch block must have no space before the colon (and likewise for the CSS standards), so there is prior-art in WP core for having no space before colons (as well as the rest of the PHP community).

Along the same lines and with exactly the same arguments, there is also:
declare(strict_types=1);

declare( strict_types = 1 );

As well as the points I mentioned above for keeping with no-space, the extra argument here is that this isn't going to vary massively - there's only something like three possible values to go inside declare(), so it is very much a boilerplate flag, rather than logic that needs readability.
declare( strict_types = 0 ) would be redundant AFAIK, so the only realistic value is 1. That, therefore, doesn't make it logic in the intent that the existing Handbook sentence was written; the logic is "is there statement there or not", not what the parts of it are.
It's also always going to be at the top of the file, probably with a clear line space before any namespace or use statements, well away from any other blocks of code, so I can't see that readability is an issue.
I agree that exceptions make for a bad approach to writing standards.
But then, the existing Handbook already has inconsistencies. Space usage of ['a'] vs [ $a ], lack of spaces around type-casts like (array), trailing comma usage of single-line vs multi-line arrays etc. All of them are in the middle of business logic. What I'm referring to is a declare statement at the top of a file.

For return types, no space before the colon. When colon is used as a separator between different things (in the ternary operator, for example), there should be spaces. When it's used as a "here is something related to the thing I'm coming after", (case statements and return types), there should be no space before, one space after when they're on the same line.
The other obvious use case of colon is as an alternative to {} on if statements, and loops - I would very much like to deprecate this usage at some point, so I don't think it's necessary to consider.
For declare(), use spaces. While it's usually used at the top of the file, that's not always the case - particularly with the ticks directive, it's not uncommon to see that changed at various points within the code.

My preference, is that for something "relatively" new (and not yet found in WP core, or many plugins) that there's a good case for sticking with no-space:

:+1:  for consistency with prior art here.

For declare(), use spaces.

As - for now - it is rarely used (encoding introduced in PHP 5.3.0, strict_types in PHP 7.0, only ticks available in PHP 5.2), I'd just as easily leave that one alone for now until a time when it becomes more relevant.
Personally I'd prefer no spaces as:

in sync with examples everywhere
distinguishes it from function calls - a declare statement is an execution directive

it is rarely used

ticks and encoding have not been used much, but the availability on strongly-typed behaviour in PHP 7 is only going to increase (strict types, scalar type declarations, return types etc.) as we move forward. Right now, all plugins and client work my team and I do is PHP 7.0+, and all files should be getting strict_types as they are worked on.

particularly with the ticks directive, it's not uncommon to see that changed at various points within the code.

I can't see it in core, and it's not something I've seen much use of at all - do ticks get much use in a WordPress environment? All the reasons for sticking with no-spaces vs the slight chance someone might be doing something with ticks + historical code style of function calls (which are different), seems a simple conclusion.

For return types, no space before the colon.

@pento Yay :-) Can that be added to the Handbook then, please?

I can't see it in core, and it's not something I've seen much use of at all - do ticks get much use in a WordPress environment?

They're used a bit internally on WordPress.com, and always in the context of a ::tick_on(), ::tick_off() helper method, so they can be more readily controlled.

Can that be added to the Handbook then, please?

👍🏻

I just ran into the issue with an expected space before the return type colon, which I don't want to be there.
So, did I understand correctly that this will be fixed sometime soon?
For now, I will just exclude the according message:
<exclude name="WordPress.WhiteSpace.ControlStructureSpacing.NoSpaceAfterCloseParenthesis"/>

Reopening as - while PR #1421 fixes the false positive previously encountered -, there currently isn't any check in place for the desired spacing.

The rule is (currently) inconsistent.
I get:
Space between opening control structure and closing parenthesis is required
(WordPress.WhiteSpace.ControlStructureSpacing.NoSpaceAfterCloseParenthesis)

For:
function test2( array $foo ): \Generator {
    yield 1;
}

But no complaints for the exact same code without a function parameter:
function test1(): \Generator {
    yield 1;
}

I've experienced this as well, though I thought we fixed it.
@connerbw are you on the latest release of WPCS?

Sorry, we're on "wp-coding-standards/wpcs": "^0.14.0",
See: https://github.com/humanmade/coding-standards
I'll open the bug there.


Docs link is broken in the readme

Describe the bug
Unable to visit the link to the docs
Steps to reproduce
Follow the docs link in the readme
Expected behavior
The docs sources or pre-rendered sources are available
Environment

OS: N/A
Browser link from the project github

Additional context
The broken url points to https://github.com/kaazedev/imgui-editor/docs

Fixed, docs will be available soon


libmediaart: remove deprecated recipe

The meta-bistro version of libmediaart recipe is not actively used or
maintained. The upstream version of this recipe exists in
meta-openembedded/meta-multimedia layer.
Singed-off-by: Gordan Markuš<EMAIL_ADDRESS>

@zeenix fixed.


tests/e2e: debugging TestCtlV2Set

Debugging failures in coverage tests.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@72cc355). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #9700   +/-   ##
=========================================
  Coverage          ?   68.55%
=========================================
  Files             ?      373
  Lines             ?    35023
  Branches          ?        0
=========================================
  Hits              ?    24011
  Misses            ?     9287
  Partials          ?     1725

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 72cc355...d8ea9d5. Read the comment docs.

Fixed via https://github.com/coreos/etcd/pull/9702.


Donation options missing

Hi! I was trying to find donation options to encourage further lapce development, but I couldn't find any.
If there would be crypto/SEPA donation options available, that'd be great! Otherwise, potentially mentioning that no donations are needed/beneficial to the project could also work.
Thanks to everyone involved in the project regardless! :green_heart:
Even though I see from many occasions that it's very fresh, I'm already trying to introduce it to certain workflows, and sometimes it works successfully. The start-up times are great and the simplicity is already there!

I second this. I would be very happy to donate.

It was mostly discussed on Lapce Discord server, and for now there are no plans to collect monetary donations.
All other "donations" forms are welcome (code, documentation, issues contributions)

Has anyone here used the GitHub Sponsors service?  Perhaps that could be a way for this project for accepting monetary donations but I'm not familiar with the details and whether or not GitHub takes a cut.

Perhaps that could be a way for this project for accepting monetary donations

The decision is that the project doesn't want to receive money, not that there isn't a way to do so

Okay sorry, it needs to be said - you guys are amazing


docs: revamp the DEVELOPER_GUIDE

Note: used markdown-toc vscode extension to create the toc. It doesn't let
users to --no-firsth1, so I had to promote each heading by one.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #100   +/-   ##
=======================================
  Coverage   47.32%   47.32%
=======================================
  Files          12       12
  Lines         598      598
=======================================
  Hits          283      283
  Misses        268      268
  Partials       47       47

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7225efd...d5fabda. Read the comment docs.


Undefined features in Patric

For some reason there are “undefined” pegs in Patric.  Where do these come from?   Furthermore,  they are listed at the top of Search results after any search  This is probably confusing for a user.
Could you fix these features?   If not, please do not allow these features to appear in  search results at least

when  addressing this, please check all other data types in the global search to make sure this doesn't happen elsewhere.

Instead of getting annotation source and type, I changed to fetch specialty gene property, source and evidence fields, which are more informative for specialty genes.

Fixed and available on alpha.

No, no, it is still not fixed on alpha!   Yes, the word "undefined" disappeared, but if you click on one of these Specialty genes returned - you get an empty page.  This is not good... Sorry to be so difficult

Fixed the "undefined" issue. I'll create a new issue for the link problem.

Got it, thank you!
Shall I create a new issue for the mismatch between gene functions displayed on Search results page versus the actual gene functions displayed on the corresponding gene pages?
What do you think?

Yes, please. Thanks.

confirmed on production.


Fixes materializecss issue 901 Select list dropdown scrollbar closes …

…the dropdown in IE

There is no issue 901, do you mean issue #157?

No, that's a separate issue. This is related to an issue with materializecss.

Ok.
So we are fixing it in angular-materialize, because the folks over at MaterializeCSS isn't going to fix it anytime soon?
In that case, the code should include a comment stating that the code isn't needed when Dogfalo/materialize#901 is fixed.

That's correct. It may be a while (if ever) that this issue is fixed on their end. At the moment they're relying on individual sites/apps to fix it themselves. I'll add the comment.

Ok, I merged it, thinking that it would work, since people said so over at the Materialize issue.
The problem is that it causes an issue with multiple-select, where the select closes when one has selected something (which is not supposed to happen when multiple things can be selected).
So can you answer what the line $('input.select-dropdown').trigger('close'); was doing? Because I cannot see the use for it. (For now i have disabled that part of it when "multiple" is used).


fixed spelling mistake

User pointed out the mis-spelling of received on the label

Grateful to eagle eyed users!


Lock-file update PR's don't trigger PR checks

🐛 Bug Report

The lock-file update GitHub Action uses peter-evans/create-pull-request, which suffers from the known GHA restriction that prevents GHA's generating further GHA's - documented here. This means that the main PR checks do not get run on pull requests proposing dependency updates.
The PR checks are an important benefit of the dependency lock-file PR concept, so we should either:

Explore Peter Evans' various documented solutions.
Seek an alternative GHA for raising PR's that doesn't have this limitation.

This is now resolved by using a GH App generated token.


Add to FlatHub

I'm not sure how I can install a standalone flatpak file - everything points towards the FlatHub repository, where flatpaks may be published.
Could you add the app to their repository? The repository is meant to be used by the developer him- or herself, so I'm not sure if it would be good to add it myself. Thank you!

What kind of issues do you having while installing yakyak using flatpak?

I couldn't find a commend to install it directly (like a deb),  but I may have overlooked something.

What way did you tried to install yakyak flatpak? Using GUI or terminal? I suggest you to use terminal, because when I tried to install yakyak's flatpak it failed me the GUI way, but when I tried install it using terminal command (I think in root) it worked.
So just download the file and open folder that contains the flatpak file in the terminal and use command:
flatpak install filename
Just change the filename to the name of the flatpak's name. If it fails it might be that it needs root privileges.

Oh, that's it, thank you!


How do I convrert bytebuffer image to Image(Tensor) class in JNI?

**Platform: Arm64-v8a
**Operating System: Android
Problem description:
I want to pass my bytebuffer that is filled by RGBA8888 to my jni with neon class.
Here's my code.
Image src;
void *dBuf = env->GetDirectBufferAddress(buf);
src.allocator()->init(TensorInfo(w, h, Format::RGBA8888));
src.allocator()->allocate();
src.allocator()->import_memory(Memory(dBuf));
And I got this error.
error: no matching conversion for functional-style cast from 'void *' to 'arm_compute::Memory'
src.allocator()->import_memory(Memory(dBuf));
I have no idea how to convert my rgb bytebuffer to Image(Tensor) class.
Anyone give me some hint please.

Hello @Kang3498 ,
Have a look here
We will try to simplify the interface to pass just a raw pointer instead of having to implement an interface.


CVQU

Use the preview tab to see the example given below. Edit the relevant information and preview the changes before submitting. You may delete these instructions.

Key
Value

ID
CVQU

Source
Vaaran Bhai Gurdas Ji

Page
28

Line
gur isKI dw rwhu eyhu; gurmuiK cwl clY so dyKY [

Correction
THIS ≠ THAT

PROOF (EDITION)
Image:

Correction:
gur isKI ≠ guris`KI
Proof:
Vaaran Bhai Gurdaas Ji | November 2011 | Shamsher Singh Ashok | SGPC, Sri Amritsar
Image:


[UI] [Bug] Sometimes UI never draws

Occasionally, the window just stays entirely blank.
Interesting that closing the window does NOT close the application in this case.
Logs
2024-07-04 12:59:02.533 -07:00 [INF] ----------------------------------
2024-07-04 12:59:02.860 -07:00 [INF] Starting
2024-07-04 12:59:02.865 -07:00 [DBG] Hosting starting
2024-07-04 12:59:02.881 -07:00 [INF] Application started. Press Ctrl+C to shut down.
2024-07-04 12:59:02.883 -07:00 [INF] Hosting environment: Production
2024-07-04 12:59:02.885 -07:00 [INF] Content root path: ...
2024-07-04 12:59:02.885 -07:00 [DBG] Hosting started
2024-07-04 12:59:03.015 -07:00 [DBG] Main Window: OK
2024-07-04 12:59:03.098 -07:00 [INF] LoadDefinition: OK Sample Slides
2024-07-04 12:59:03.115 -07:00 [DBG] Create Resources: No resource load needed at this time
2024-07-04 12:59:03.145 -07:00 [DBG] Create Resources: Loading...
2024-07-04 12:59:03.198 -07:00 [DBG] LoadDefinitionAsync: Launched
2024-07-04 12:59:03.200 -07:00 [DBG] Main Window: Reload OK

Call stack
Looks like we're in LoadBitmapAsync:
                var result = await CanvasBitmap.LoadAsync(resourceCreator, randomAccessStream);

Happened again.  This time it drew the command bar, and stuck on loading spinner for the canvas.
Logs below. Also, since was in the debugger, a few more interesting bits included here.
[15:55:34 DBG] Main Window: OK
onecoreuap\windows\frameworkudk\warppal.cpp(783)\Microsoft.Internal.FrameworkUdk.dll!00007FF8364A31A8: (caller: 00007FF8364A464D) ReturnHr(1) tid(5ae4) 80004002 No such interface supported
onecoreuap\windows\frameworkudk\warppal.cpp(783)\Microsoft.Internal.FrameworkUdk.dll!00007FF8364A31A8: (caller: 00007FF8364A464D) ReturnHr(2) tid(5ae4) 80004002 No such interface supported
[15:55:34 INF] LoadDefinition: OK Sample Slides
Exception thrown at 0x00007FF859A7BA99 (KernelBase.dll) in LogoSlideMaker.WinUi.exe: 0x40080202: WinRT transform error (parameters: 0x000000008000000B, 0x0000000080070490, 0x0000000000000014, 0x000000DEAE57C6D0).
Exception thrown at 0x00007FF859A7BA99 (KernelBase.dll) in LogoSlideMaker.WinUi.exe: 0x40080202: WinRT transform error (parameters: 0x000000008000000B, 0x0000000080070490, 0x0000000000000014, 0x000000DEAE57C6D0).
[15:55:34 DBG] Create Resources: No resource load needed at this time
onecoreuap\windows\frameworkudk\warppal.cpp(783)\Microsoft.Internal.FrameworkUdk.dll!00007FF8364A31A8: (caller: 00007FF8364A464D) ReturnHr(3) tid(5ae4) 80004002 No such interface supported
[15:55:34 DBG] Create Resources: Loading...
[15:55:35 DBG] LoadDefinitionAsync: Launched
[15:55:35 DBG] Main Window: Reload OK
onecoreuap\windows\frameworkudk\warppal.cpp(783)\Microsoft.Internal.FrameworkUdk.dll!00007FF8364A31A8: (caller: 00007FF8364A464D) ReturnHr(4) tid(44ec) 80004002 No such interface supported
Microsoft.ui.xaml.dll!00007FF81FB4FCC2: CallContext:[\ImageDecodeActivity] 80070057 - E_INVALIDARG
Microsoft.ui.xaml.dll!00007FF81FB4FCC2: CallContext:[\ImageDecodeActivity] 80070057 - E_INVALIDARG
Microsoft.ui.xaml.dll!00007FF81FB4FCC2: CallContext:[\ImageDecodeActivity] 80070057 - E_INVALIDARG
[15:55:36 INF] Create Resources: OK


bugfix: Make ConfigurationManager read and update operate on eva.yml

ConfigurationManager is a singleton that loads the contents of ~/.eva/eva.yml into memory and uses that to read and write configuration values. The issue with that is if the source file changes, the stale values will continue to be used. This causes confusion if the user wants to change configuration values. When EVA becomes distributed, this system breaks down entirely as different processes will operate with different configuration values.
This PR simply reads directly from ~/.eva/eva.yml when a read is needed and writes back to the file when update_value is called.

Can we remove the singleton pattern?


libjsk_recognition_utils.so  to  ‘pcl::search::KdTreepcl::PointNormal::KdTree(bool)’ undefined reference

OS: ubuntu14.04, indigo, autoware-1.9.1, pcl-1.7,  gcc-4.8.5,  g++-4.8.5,  kernel: 4.4.0-146-generic.
Following autoware install wiki, when build with AUTOWARE_COMPILE_WITH_CUDA=1 ./catkin_make_release,  occured this error:
/opt/ros/indigo/lib/libjsk_recognition_utils.so：对‘pcl::search::KdTreepcl::PointNormal::KdTree(bool)’未定义的引用
/opt/ros/indigo/lib/libjsk_recognition_utils.so：对‘pcl::search::KdTreepcl::PointXYZ::KdTree(bool)’未定义的引用
collect2: error: ld returned 1 exit status
make[2]: *** [/home/jxl/third_softwares/autoware/ros/devel/lib/range_vision_fusion/range_vision_fusion] 错误 1
make[1]: *** [computing/perception/detection/fusion_tools/packages/range_vision_fusion/CMakeFiles/range_vision_fusion.dir/all] 错误 2
make[1]: *** 正在等待未完成的任务....
How to fixed this pcl error, any help is appreciated much!

Thanks for using Autoware and for your question. However the issue tracker is for posting confirmed bugs and feature requests.
We ask that you please ask questions at the ROS Answers website following our support guidelines: https://github.com/autowarefoundation/autoware/wiki/Support-guidelines#ros-answers. Please pay particular attention to the information we ask you to provide.


Toggle save configuration error

When the current value of the toggle is true, if it is adjusted to false on the interface, the save configuration will be invalid. On the contrary, when the current value is false, the save configuration can be stored successfully.

How can i define default value for toggle?

When the current value of the toggle is true, if it is adjusted to false on the interface, the save configuration will be invalid. On the contrary, when the current value is false, the save configuration can be stored successfully.

How can i define default value for toggle?


Milestone I Report: Repository Update

We have prepared Milestone Report I.
To Do: Create new wiki pages and add use-case diagram, class diagram, sequence diagram and Milestone I report.
Deadline: 15.04.22 @23.59

Added material to the repository.

Use case diagram
Class diagram
Sequence diagram
Milestone I Report


[stb] Add stb_perlin.h

This PR adds stb_perlin.h, which was originally deleted due to a patent. The patent expired, but it was never added back. Details in the code.

Which triplets are supported/not supported?

Yes

you have to use vcpkg_download_distfile
you cannot use file(DOWNLOAD...)

D'oh! The dist in the name threw me off and I just didn't even look at the function.

@friendlyanon Could you please submit an issue to upstream for adding this file?
I saw upstream mentions in some issues that this file will be restored, but so far there is no action, I am not sure if there is any other impact here, so we need to get upstream approval to add this file.

It looks like upstream has been inactive since September 2021, so I doubt that whether we can get the agrees of upstream.
I saw in this issue that the upstream maintainer indicated that this file would be added back. @BillyONeal Could we merge this PR directly?

Despite upstream being relatively MIA I'm still concerned to be claiming that this header exists in a distribution of upstream when they have not themselves made that claim, no matter what the reasons are that they removed it in the first place. For instance, if there is an exploitable memory corruption bug in this header, they may reasonably complain that vcpkg is 'putting words in their mouth'.
However, the author is on record here that they will put it back soon:
https://github.com/nothings/stb/commit/59e7dec3e8bb0a8d4050d03c2dc32cf71ffa87c6#commitcomment-64296536
I double checked that the file being downloaded here is the exact same file as the one removed in that commit.
Thanks for your submission @friendlyanon


Add https support

Thanks for the contribution @bilal-mk !
I won't disable verification of the hostname, though. If you want you can disabled it with an environment variable, see the documentation, but I will not incorporate an insecure by default setting.
Why do you want to limit the protocols supported? While I don't think that Elasticsearch will ever support e.g. the ftp protocol ; ) I don't really see a point to limit them. What was the thought here?


Additional blink attributes - also correct syntax of /Attribute/Blink

Add:
/Attribute/Blink/Duration {requireChild}  [Duration of blink, usually the half-height blink duration in seconds taken either from base or zero of EEG signal. For eye-trackers, usually denotes interval when pupil covered by eyelid.]
(number sing) {takesValue, isNumeric, unitClass=time, default=s}
Fix:
Numerous syntax errors in adding /Attribute/Blink subtree.  Centiseconds is misspelled. Things are in wrong order. [ ] missing around descriptions.
Also in the units section centiseconds is misspelled.  Also add cs in the units.

The previous comments the number sign on takes value was was misread as markup
/Attribute/BlinkDuration ....
(number sign) {takesValue, isNumeric, unitClass=time, default=s}

Fixed, could you please check?

Checked....looks good.  Thanks
On Tue, Mar 7, 2017 at 3:35 PM, Nima Bigdely-Shamlo <
<EMAIL_ADDRESS>wrote:

Fixed, could you please check?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BigEEGConsortium/HED/issues/11#issuecomment-284866954,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABIkukKlTOh93Hhp-PJv9BHQl2v5YxLsks5rjc23gaJpZM4MURV4
.


Add Processor Options

Enables Passing of Processor Options per DataSourceGroup to ProcessingSources. Closes #176

            freeDataSources,

this.

Refers to: src/Microsoft.Performance.Toolkit.Engine/DataSourceSet.cs:453 in f7e5056. [](commit_id = f7e5056009146dff872fafa7244ccb88b8b49648, deletion_comment = False)


Ps move paired but won't work

Hi
I've paired my PS Move to the PC but it won't work.
It won't even show up in the controller section of the config utility.
It works fine on my macbook with windows 7 but it won't work on my PC.
It pairs fine. The led goes solid an i can see my Move in the bluetooth devices but it  doesn't work.
[2017-09-20 22:47:32.124]: bluetooth_get_host_address - Retrieved radio info
Config file name: "C:\Users\Marcin\AppData\Roaming\PSMoveService\TrackerManagerC
onfig.json"
Config file name: "C:\Users\Marcin\AppData\Roaming\PSMoveService\TrackerManagerC
onfig.json"
Config file name: "C:\Users\Marcin\AppData\Roaming\PSMoveService\HMDManagerConfi
g.json"
Config file name: "C:\Users\Marcin\AppData\Roaming\PSMoveService\HMDManagerConfi
g.json"
libusb: error [init_device] device '\\.\USB#VID_1A2C&PID_2D23&MI_01#6&11FCAEC7&0
&0001' is no longer connected!
libusb: error [windows_get_device_list] program assertion failed - existing devi
ce should share parent
libusb: error [windows_get_device_list] program assertion failed - existing devi
ce should share parent
libusb: error [windows_get_device_list] program assertion failed - existing devi
ce should share parent
libusb: error [windows_get_device_list] program assertion failed - existing devi
ce should share parent
[2017-09-20 22:47:32.147]: PSMoveController::open - Opening PSMoveController(\\?
\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&03d5&col01#8&3551ff
c7&7&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
[2017-09-20 22:47:32.153]: PSMoveController::open -   with serial_number: 0006f5
18d88d
[2017-09-20 22:47:37.149]: PSMoveController::getBTAddress - HID ERROR: Przekrocz
ono limit czasu semafora.
[2017-09-20 22:47:37.160]: PSMoveController::open - Failed to get bluetooth addr
ess of PSMoveController(\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&00020
54c_pid&03d5&col01#8&3551ffc7&7&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
[2017-09-20 22:47:37.180]: DeviceTypeManager::update_connected_devices - Device
device_id 0 (\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&03d
5&col01#8&3551ffc7&7&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}) failed to open
!
[2017-09-20 22:47:37.195]: DeviceTypeManager::update_connected_devices - Closing
 device 0 (PSMove) since it's no longer in the device list.
[2017-09-20 22:47:37.202]: PSMoveController::close - Closing PSMoveController(\\
?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&03d5&col01#8&3551f
fc7&7&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
libusb: error [init_device] device '\\.\USB#VID_1A2C&PID_2D23&MI_01#6&11FCAEC7&0
&0001' is no longer connected!
libusb: error [windows_get_device_list] program assertion failed - existing devi
ce should share parent
libusb: error [windows_get_device_list] program assertion failed - existing devi
ce should share parent
libusb: error [windows_get_device_list] program assertion failed - existing devi
ce should share parent
libusb: error [windows_get_device_list] program assertion failed - existing devi
ce should share parent

Problem resolved by installing Windows 7
No issues since then


Use an explicit entity category of CONTROL instead of None

Having None be the "control" entity category always felt a little strange. This PR makes the mapping explicit in the ZHA lib.
Core diff:
diff --git a/homeassistant/components/zha/entity.py b/homeassistant/components/zha/entity.py
index 3e3d0642ca2..c26f93ecfb6 100644
--- a/homeassistant/components/zha/entity.py
+++ b/homeassistant/components/zha/entity.py
@@ -9,6 +9,7 @@ import logging
 from typing import Any

 from propcache import cached_property
+from zha.application.platforms import EntityCategory as ZhaEntityCategory
 from zha.mixins import LogMixin

 from homeassistant.const import ATTR_MANUFACTURER, ATTR_MODEL, ATTR_NAME, EntityCategory
@@ -45,7 +46,9 @@ class ZHAEntity(LogMixin, RestoreEntity, Entity):
         meta = self.entity_data.entity.info_object
         self._attr_unique_id = meta.unique_id

-        if meta.entity_category is not None:
+        if meta.entity_category is ZhaEntityCategory.CONTROL:
+            self._attr_entity_category = None
+        else:
             self._attr_entity_category = EntityCategory(meta.entity_category)

         self._attr_entity_registry_enabled_default = (

The None default in HA is is a bit weird, yeah..
I guess it's fine to have our EntityCategory deviate from HA's EntityCategory for a good reason, not sure if we need to do it here. Let's assume there would be a "HA entity API" in the future, we'd still need our own EntityCategory and map then if we want to keep CONTROL.
Another thing: e.g. temperature sensors with (primary) sensor entities would also all have the CONTROL category?

Ah, good point, I completely forgot about sensors. Ignore this PR 😄


Add Kubernetes namespace for Arc DNS

Overview/Summary
This PR adds a missing privatelink.kubernetesconfiguration.azure.com namespace to the private DNS zones for Azure Arc.
This PR fixes/adds/changes/removes

Missed in the fix for #482

Breaking Changes
None
Testing Evidence
See unit tests
As part of this Pull Request I have

[x] Checked for duplicate Pull Requests
[x] Associated it with relevant issues, for tracking and closure.
[x] Ensured my code/branch is up-to-date with the latest changes in the main branch
[x] Performed testing and provided evidence.
[x] Updated relevant and associated documentation.
[x] Updated the "RELEASE" page with details needed for when this code change is released.

/azp run update

/azp run update

/azp run unit


Removing a possible race condition between the downloader and installer - To remove the Immediate Zip File error

In the downloader we were piping the response to the output stream with end: false due to which we were not getting the writestream finish event which indicates when the response was completely written to the filestream. This led to the Immediate Zip FIle Error when using the Download and Install Pipeline as we didnt wait for the data to be completely put into the filestream and trying to unzip it created that error.
So in this PR, I have removed {end: false} condition and am resolving the promise of the dowloader when the filestream finish event is seen, so that there is no race condition.
Also instead of using open file descriptors, modified the code to use the file paths so there is no problem, even if the file doesnot have an open fd.

Overall looks ok. I'm not convinced by the fd -> path change. Does this open us up to a bunch of issues?

Perf issues due to multiple OS interactions?
Race conditions? What prevents the file we used to have an fd for from being taken by other processes
Special case of the above: downloaders/installers often fight with AntiVirus tools because the latter grabs locks on recently written files. Are we sure that this change won't open up that set of issues?

Closing this in favor of #2245


Feat: Jump to file with <CR> on the CommitView

At a high level the approach consists on:

Identify if we are over a path on the OverviewFile section by checking for the NeogitFilePath highlight
Recursively check the diffs sections of the layout until with hit leafs with a NeogitDiffHeader sign. If so, store the line number and value of the header on the diff_headers table.
Loop over the diff_headers and jump if we have a hit.

This addresses the feature request on issue #920

Sorry for the delay in reviewing - this looks great. Thanks for the contribution :)


Leave umask unset for redhat

Setting Rsyslog's umask to 0000 causes the /var/lib/rsyslog/imjournal.state file to be created with world writable permissions. This was fixable by setting the umask parameter, however, I don't think the umask should be set by default.

@saz - Wanted to check in on this. Any plans to merge this change in? Or are there particular concerns you have with the change?


FifteenTwenty/FifteenTwentyUltraLight-Oblique.otf - named incorrectly

Name clashes with (Regular) Oblique on OS X El Capitan.

I can't see any obvious way to fix this in Fontforge, so I'm going to close this. Few people will use this variant anway


source_id -- Please modify description of MIROC-ES2H/atmosChem

After modification (#880) it seems that atmosChem of MIROC-ES2H and MIROC-ES2H-NB is different in source_id.html, but these are the same. So please modify description of atomChem as follows:
"description":"CHASER4.0 (T42; 128 x 64 longitude/latitude; 81 levels; top level 0.004 hPa)"

@tinoue70 just so we catch all the outstanding issues, can you please review all the MIROC contributions by browsing CMIP6_source_id.html and using the search entry "MIROC". This way I can minimize my workload but catching any outstanding issues at once

@tinoue70 just checking if the above is the only change required? If yes, I will get this done by the end of the week

@durack1 sorry to be late. I asked our modeling people again, and found nothing else to be changed for now. Please do it.

@tinoue70 thanks for clarifying, the change is now in place. Please review CMIP6_source_id.html and let me know of any further changes


tags href

Hi,
Is it possible to make tags to links?

Looks for this too. No yet find any solution for this. :(

Looking for this too. No yet find any solution for this. :(


Stage 6 RuntimeWarning: invalid value encountered

Instrument
Light curve fitting (Stages 4-6)
What happened?
I am running Eureka from S3, but when I get to Stage 6, I get this error:
2022-08-14 15:54:41,519 - stpipe - WARNING - /mmfs1/home/kcrasmus/src/eureka/src/eureka/S6_planet_spectra/plots_s6.py:96: RuntimeWarning: invalid value encountered in sqrt
return (r/y_scalar)**(1/expFactor)/scaleHeight - H_0
I guess this is implying that y_scalar is zero. I don't have a model yet, which may be the problem? I do not think it is scaleHeight because I have that set to 2.3 in the S5 epf.
Error traceback output
slurm-5868303.txt
S6_TRAPPIST-1c.txt
S5_TRAPPIST-1c.txt
What operating system are you using?
Linux
What version of Python are you running?
3.9
What Python packages do you have installed?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Not having a model to plot at the same time won't be an issue at all as you have correctly set model_spectrum to None for that case. The S5 EPF file is also not relevant for this issue - none of those settings impact Stage 6 directly. I would mention that a mean molecular weight (planet_mu in your S6 ECF) of 2.3 implies an H2 and He dominated atmosphere which is not likely to be the correct value for such a small planet.
The main issue though is likely a bug caused by you setting the planet_Rp manually but not the planet_R0 manually - I know that leaving both set to None works well, but it appears that only setting one of them might cause an issue. I'll look into this more shortly, but as a short-term fix you are likely fine setting planet_Rp to None which should avoid a crash (but do consider using a mean molecular weight more appropriate to the atmosphere you'd expect).
And note that you are able to run just Stage 6 on it's own, so you won't need to re-run everything from scratch or anything.

also, perhaps this is a second issue, but the spectra I'm getting look like
this:
[image: fig6101_transmission.png]
thanks,
kaitlin
On Tue, Aug 16, 2022 at 2:18 PM Kaitlin Rasmussen @.***> wrote:

Hello,
 Which file is planet_Rp in? I see a planet_Rad in S6.ecf but not a

planet_Rp. If I set both planet_Rad and planet_R0 to None, I get the same
error.
Thanks,
Kaitlin
On Tue, Aug 16, 2022 at 2:05 PM Taylor James Bell <
@.***> wrote:

Not having a model to plot at the same time won't be an issue at all as
you have correctly set model_spectrum to None for that case. The S5 EPF
file is also not relevant for this issue - none of those settings impact
Stage 6 directly. I would mention that a mean molecular weight (planet_mu
in your S6 ECF) of 2.3 implies an H2 and He dominated atmosphere which is
not likely to be the correct value for such a small planet.
The main issue though is likely a bug caused by you setting the planet_Rp
manually but not the planet_R0 manually - I know that leaving both set to
None works well, but it appears that only setting one of them might cause
an issue. I'll look into this more shortly, but as a short-term fix you are
likely fine setting planet_Rp to None which should avoid a crash (but do
consider using a mean molecular weight more appropriate to the atmosphere
you'd expect).
And note that you are able to run just Stage 6 on it's own, so you won't
need to re-run everything from scratch or anything.
—
Reply to this email directly, view it on GitHub
https://github.com/kevin218/Eureka/issues/452#issuecomment-1217164574,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2E4CUEHCTG52VV7DHIAV5LVZP7C5ANCNFSM56TGW42Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

I believe you're replying by email rather than on GitHub, and your attached image doesn't seem to be able to make it through that way. Can you send it on GitHub instead of email?

gotcha. here it is:

thanks,
kaitlin

I'll also note that you should look at your outputs from Stage 5 - the lsq fitter failed to converge with the default value for lsq_maxiter. If you set lsq_maxiter to something ~10x the number of evaluations it stopped at (2001 according to the log you sent me, so try 20000) then lsq should converge.
As for the plot, I'm not sure what your concern is. If you want y error bars, you'll need to use one of the methods that gives uncertainties on fitted parameters (emcee of dynesty). If you're concerned by the near-zero transit depth, then you should look at what happened during Stage 5 (see again my comments above for lsq convergence).

This is NIRSpec spectra, so shouldn't there be ~432 data points in the spectrum? Also, the lsq fitter failed to converge even with 30,000 iterations. Not sure what could be causing that.
slurm-5873588.txt
S5_TRAPPIST-1c.ecf.txt
S5_TRAPPIST-1c.epf.txt
S6_TRAPPIST-1c.ecf.txt

In your stage 4 you'll have set the number of spectral bins you want to two. You can set that to None to have unbinned spectra (very time consuming) or whatever coarser wavelength resolution you want. Not sure why lsq isn't converging - you should try troubleshooting that yourself using the plots and logs

ah, gotcha. okay, I'll see if I can figure out the non-convergence problem and report back if I figure it out. Thanks for all your help!

Ohh, I finally understand the issue you encountered with Stage 6 now - it was that you had gotten a point so close to zero that the primary y-axis has values below Rp/R* = 0, and when you then try to take the square-root of that to convert it to a scale height you end up with an imaginary number. I'll have to think a bit on how to handle that properly

Hello,
 Which file is planet_Rp in? I see a planet_Rad in S6.ecf but not a

planet_Rp. If I set both planet_Rad and planet_R0 to None, I get the same
error.
Thanks,
Kaitlin
On Tue, Aug 16, 2022 at 2:05 PM Taylor James Bell @.***>
wrote:

Not having a model to plot at the same time won't be an issue at all as
you have correctly set model_spectrum to None for that case. The S5 EPF
file is also not relevant for this issue - none of those settings impact
Stage 6 directly. I would mention that a mean molecular weight (planet_mu
in your S6 ECF) of 2.3 implies an H2 and He dominated atmosphere which is
not likely to be the correct value for such a small planet.
The main issue though is likely a bug caused by you setting the planet_Rp
manually but not the planet_R0 manually - I know that leaving both set to
None works well, but it appears that only setting one of them might cause
an issue. I'll look into this more shortly, but as a short-term fix you are
likely fine setting planet_Rp to None which should avoid a crash (but do
consider using a mean molecular weight more appropriate to the atmosphere
you'd expect).
And note that you are able to run just Stage 6 on it's own, so you won't
need to re-run everything from scratch or anything.
—
Reply to this email directly, view it on GitHub
https://github.com/kevin218/Eureka/issues/452#issuecomment-1217164574,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2E4CUEHCTG52VV7DHIAV5LVZP7C5ANCNFSM56TGW42Q
.
You are receiving this because you authored the thread.Message ID:
@.***>


chore: replace environment variables with package.json entries

[!Warning]
This is a work in progress. Do not merge.

According to actions/node-setup, it will read manifest.engine values to decide what node version to use.
Second, the lockfile path is only relevant if it is non-default.
Refs: https://github.com/actions/setup-node/blob/main/docs/advanced-usage.md#node-version-file

Todo

investigate why its still on 18: ##[debug]Set output node-version = v18.20.4

Looks like its yet to be fixed: https://github.com/actions/setup-node/issues/912


Gender and Accent Recognition Brainstorm

After a performant forced alignment pipeline is done, my next thought goes to how to add gender and accent recognition.
First of all, I will assume that each segment output by the forced aligner contains the voice of only one speaker. The forced alignment system depends upon voice activity detection to find silent regions of the audio, so this is a decent assumption, except in the case of interjections (where one speaker speaks over another without waiting for the first speaker to stop).
It is straightforward to consider these supervised learning tasks, but I have other ideas.
Librivox and Common Voice both contain gender labels. As I understand it, Common Voice also contains either region or accent metadata for speakers. Finally, it is possible that we could detect, e.g., Spanish-accented English by using Spanish spoken by native Speakers, even if the region or accent metadata is poor. Finally, CommonVoice and Librivox both contain "clean" audio. It is probably worthwhile to use SpecAugment with whatever training process we use in order to help generalization when applied to archive.org data (I've seen data where it is raining, etc.).
We can use locality sensitive hashing on the "ivector" of each training data audio segment (we ignore the text transcript).  It is essentially the mean of a gaussian distribution. We would use locality sensitive hashing to put the gender- and accent-labeled data's ivectors into hash buckets.
You can use Euclidean distance or Mahalanobis distance for the distance metric. It's important that all ivectors (which are the mean of a multivariate Gaussian) have the same covariance for these metrics. I'm not 100% certain, but it seems like you could simply normalize the mean of the spectrogram to 0 and the covariance to the identity matrix to 1 for a particular spectrogram for this. Worth double checking. Otherwise, https://en.wikipedia.org/wiki/Bhattacharyya_distance may work.
For unlabeled data, we would also hash the ivectors into the same hash buckets. We would classify an unlabeled ivector by assigning it to the majority accent or gender in that bucket.
What is distinct about this from a discriminative or supervised method is that it has an "open world" assumption. For example, we could have a large number of buckets. If there are no or few labeled ivectors in a particular bucket, that suggests this may be an unusual accent or way of speaking compared to the rest of the dataset. For example, it could be someone with a speech impediment or children's speech, which are probably worth capturing in their own right.
Finally, if you get ivectors, you could conceivably visualize them using t-SNE or whatever is newer or cooler than it nowadays.

Using this model https://github.com/tensorflow/models/tree/master/research/audioset for inference on our dataset is a good first pass. It has women's speech, men's speech, and children's speech as labels.
No accent detection, but that's not really the focus of the research group behind Audio Set and Youtube-8M.
One of the things I would like to emphasize is that things can quickly become out of hand here. Even "running a pretrained model" can be complicated if we need to port it to an accelerator.

Using this model https://github.com/tensorflow/models/tree/master/research/audioset for inference on our dataset is a good first pass. It has women's speech, men's speech, and children's speech as labels.
No accent detection, but that's not really the focus of the research group behind Audio Set and Youtube-8M.
One of the things I would like to emphasize is that things can quickly become out of hand here. Even "running a pretrained model" can be complicated if we need to port it to an accelerator.


Change Mesh3D_edge_z from latitude to elevation

Fixes Mesh3D_edge_z so that it no longer copies Mesh3D_edge_y.

Thanks! sorry this took so long to merge.


[CDAP-15256] support decimal type in big query connection

Yes, this PR only focuses on bq connection support for numeric types. Dataprep directives should support this type. Also we should add more directives for conversion. Filed: https://issues.cask.co/browse/CDAP-15358


Improve docs

curl http://localhost:8001/posts/resttemplate/1
curl http://localhost:8001/posts/webclient/1
curl http://localhost:8001/katakroker

Added


Make ruby unit tests work on ruby 3

Fixes a style that was broken due to https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/

failures unrelated


API Version 2 Specification

The current API is version 1 and was built mainly to support migration from Scholarsphere 3. Now that it's complete, we need to create a version 2 API to support RMD integration and other features.
WDLL

a specification for our API that will support RMD integration
Swagger docs using OpenAPI

The current v1 of the API supports RMD integration and there are Swagger docs. There needs to be a v2 api, but that's out of scope here.


fix rawbody => rawBody

@mhoeger thanks for fixing this. This bit me today. +1 if you can get it merged and released to npm :)

@altano - the change should be in npm! You may need to delete your package-lock.json and try again. Note that the prerelease version is what was incremented, which may be why you're not seeing it right away!

@mhoeger yeah I'm using the released, stable version not the pre-release. I'll wait for it to make its way to the stable version. Thanks!

Oh, I misunderstood, latest points at 1.0.2-beta2. I updated and now have the fix. Thanks!


String printed in machine-readable format when no references found

What did you expect to happen?
When I call interactively +lookup/references on string "planner" and no results are found, it should print something like:
Couldn’t find references of "planner"
What actually happened?
When the string "planner" in the buffer is propertized, I get:
Couldn’t find references of #("planner" 0 5 (face font-lock-function-name-face fontified t identifier-at-point t) 5 16 (face font-lock-function-name-face fontified t identifier-at-point t))
Describe your attempts to resolve the issue
Changing %S inside +lookup/references error call to "\"%s\"" solved the problem. If there are no caveats with the approach, I can make a PR for this.
Steps to reproduce
I could only reproduce this with lsp-managed-mode by just interactively calling +lookup/references in the buffer
System Information
https://pastebin.com/pz9Xi3XL

This issue should now be resolved. Let me know if that isn't the case and I'll reopen it. Thanks for bringing it to my attention!

Works perfect, thank you


feat/footnotes

@dalanad shall we rename the occurrences of footNotes to footnotes?
Footnote is a single word.


[BUG] Tooltip popover overlay other tooltip, enter and leave delays not working correctly

Detailed description
Tooltip popovers overlays other tooltip popover.
https://github.com/carbon-design-system/carbon-components-angular/assets/2742661/c9329c9e-f6fa-4cdc-834f-7757b1463f16
It's bug related to tooltip component. In React it works as expected.
Expected behaviour:
https://github.com/carbon-design-system/carbon-components-angular/assets/2742661/8c9d4943-f0b2-407f-af26-83924fcc3f18
Will prepare a fix for that.
Steps to reproduce the issue
Add second tooltip in storybook and try to navigate over them. You will see that popover overlays.

Checked React code and problem is the same. If leaveDelayMs is higher than enterDelayMs tooltips will overlap. There is no functionality to hide other tooltips. Is there any reason why enterDelayMs = 100, but leaveDelaysMs = 300 by default? It's quite annoying to override it for example when using many IconButtons.

Not sure, we actually followed the react implementation on this one. I wasn't able to find anything on carbondesignsystem as well, it may be added for accessibility perhaps?

So i found out why they implemented that way: it's because otherwise if you were triggering another tooltip passing with the mouse over the tooltip message you just triggered, it would end up in a display hide loop.
eg:

put your nodes with the tooltip one below the other (you need more than 2)
then configure the tooltip to appear on bottom and give the same enter and leave delay
now trigger the top tooltip with the mouse and move the mouse down till the last tooltip

I think i have a better fix for this. I'll create a PR


Enhancement of the search bar section and adding transitions

Q1: Is your feature request related to a problem? Please describe.

In this current version of the page, the search bar in the light mode looks dull as it is not styled. It also does not resemble the search bar present in dark mode, making it unattractive.
The contents of the search item should be placed just below the search bar. However in this current version the "Git-GITHUB Cheatsheet Topics" section is between the search-bar and search results.
The jump from "Git-GITHUB Cheatsheet Topics" section when clicked on a particular topic is instant.

Q2: Describe the solution you'd like

The search bar in the light mode can be styled accordingly similar to dark mode.
The search bar should be shifted just below the "Git-GITHUB Cheatsheet Topics" section so that search results are loaded just after the topic is searched.
The jump from "Git-GITHUB Cheatsheet Topics" can be made smooth using a pinch of CSS.

Q3: Describe alternatives you've considered
Alternative feature that I would like to work on the typing animation of the heading of the webpage. Though, the current version looks quite fine.
Q4: Additional context

I would like to work on this issue under Hacktoberfest-2022. Would be glad if you assign this to me :) @EshanTrivedi21

Great work noticing, I will assign you this task, you can go on with solving this issue @pooranjoyb

Thanks @EshanTrivedi21 , Getting into it asap :)

resolved!


Typo? 03.05-Hierarchical-Indexing  "Multiply indexed DataFrames"

The markdown  "Multiply indexed DataFrames", should be "Multi-indexed" ?
(Thanks for uploading these notebooks!)

I think it's OK as-is... multi-indexed is short for multiply-indexed. I think the editor removed the hyphens.


Request to be added as a WP MicroProfiler New Contributor

I'd like to blog on the MicroProfile site, so this is my request.
Name: James Falkner
Email<EMAIL_ADDRESS>

Hola @jamesfalkner,
Thankyou for choosing to become a MicroProfiler Content contributor via wordpress. #sharingIScaring!


[CT-1150] Include flat_graph in manifest.deepcopy()

Why isn't flat_graph included in manifest.deepcopy()? Probably not for any reason in particular.
The original implementation of manifest.deepcopy() was the early days of the dbt-RPC server (https://github.com/dbt-labs/dbt-core/commit/1a0df174c9f252d0f93e03dbf4ef5005b2429072), and that's still the only place we really call it. The idea is to support dynamically adding new temporary nodes (arbitrary SQL compilation/execution) that might need to add_refs in the manifest — or rather, a full copy of the manifest.
This does mean, however, that any time you want to deepcopy of a manifest, and you want that copied manifest to support introspection of the graph variable in the Jinja context, you actually need an extra step:
from dbt.contracts.graph.manifest import Manifest

manifest = Manifest(...)

# should just be this, right?
copy_of_manifest = manifest.deepcopy()

# still missing something
copy_of_manifest.build_flat_graph()
# now you're good to go

The fix here might be as simple as taking this:
https://github.com/dbt-labs/dbt-core/blob/b26280d1cf1af1c715753f73eb3b46f6eaa717f5/core/dbt/contracts/graph/manifest.py#L781-L794
And adding in:
import copy
...

    def deepcopy(self):
        return Manifest(
            ...
            flat_graph={k: copy.deepcopy(v) for k, v in self.flat_graph.items()},
            ...
        )

@emmyoop maybe this is something small you could pick up with extra bandwidth


Add debug mode

Resolves #106.

Example of debug output
https://github.com/Brightspace/test-reporting-action/actions/runs/7744223624/job/21117497003?pr=107#step:6:34


Add etcd-tools package

Summary

This PR adds an etcd-tools package, which contains the etcd-dump-* tools from the etcd repository.
Change Log

Add etcd-tools package

Does this affect the toolchain?
No
Test Methodology

Local build

I think I've hit a spec-cleaner bug - it keeps asking me to add a new line above %files.

Thanks for the contribution, LGTM! Don't worry about the spec-linter's endless hunger for newlines.


Add DragFloat to change size of custom rendering.

I've added a drag_float slider to change the size in the "Custom Rendering" window. This fixes a TODO and brings it in line with the official imgui_demo_window. I've copied over the parameters / ranges from there.

Thanks! The change looks good, but it seems your branch is very far (over 100 commits) behind the current master so there's merge conflicts

Ah oops, I'll fix it.
On Fri, Mar 1, 2019, at 23:32, Joonas Javanainen wrote:

Thanks! The change looks good, but it seems your branch is very far
(over 100 commits) behind the current master so there's merge conflicts
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Gekkio/imgui-rs/pull/205#issuecomment-468834446,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAhHbFjHly3OVg3Tdmi1tqX8ppCVMboks5vSapugaJpZM4bYkIe.

Closing this as out of date. if you want to re-open, feel free to comment


Use port 443 for API server

What this PR does / why we need it
loadBalancerIngressAllowCidrBlocks should create rules for port 443
Checklist

[ ] Update changelog in CHANGELOG.md.

Trigger e2e tests

/run cluster-test-suites

/run cluster-test-suites


Save NIST .jars to Azure Artifacts

NIST re-compiled .jars are available in the /lib folder of the structural validator repo

I looked into Azure Artifacts and artifacts require us to integrate with Azure Devops Services which has its own pipelines to integrate with to use.
I'm open to it, but don't have the time currently to look into it.

I'm doing some discovery on this right now.
There is... an internal Nexus somewhere that I'm finding but I'm not sure if it fits our use case.
I looked into Azure Artifact, but I can't tell if Azure Devops requires new billing all together. I need to look into it some more to figure out whether we can actually do this ourselves.

We got access to the internal Nexus - Maven repo; and the developers think this'll work for them.
There's still some work to do to complete this task.

[ ] Ensure that our function app and virtual machine #143 can access it via the network (firewall).
[ ] Create maven type proxy folders for caching Maven Central and other repositories. Need help from @mscaldas2012 for this.
[ ] Create maven repository group - ask @mscaldas2012 how that should look.

I would like Cosmin/Neelima/Marcelo to let me know if this will work for them, while I work out the network details for our machines to pull/push artifacts.

@mscaldas2012 : what should be the close requirement of this?
I'm assuming you'll be the reviewer of this.

Libraries loaded to nexus maven-ede-group :


update gisce/ooui to v2.6.2

Automated changes by create-pull-request GitHub action

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Ignore this

Just to try travis

TravisCI is having some problems internally apparently

Reported the bug to TravisCI support. Hopefully it will get fixed soon


jackett: 0.20.709 -> 0.20.915

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for jackett is: "API Support for your favorite torrent trackers"
meta.homepage for jackett is: "https://github.com/Jackett/Jackett/"
meta.changelog for jackett is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/s6dpvfh3kwvdilrp1k4x0mzvw5cm5638-jackett-0.20.915/bin/Jackett had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/s6dpvfh3kwvdilrp1k4x0mzvw5cm5638-jackett-0.20.915/bin/jackett had a zero exit code or showed the expected version
0 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 0.20.915 with grep in /nix/store/s6dpvfh3kwvdilrp1k4x0mzvw5cm5638-jackett-0.20.915
found 0.20.915 in filename of file in /nix/store/s6dpvfh3kwvdilrp1k4x0mzvw5cm5638-jackett-0.20.915

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
jackett

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/s6dpvfh3kwvdilrp1k4x0mzvw5cm5638-jackett-0.20.915 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A jackett https://github.com/r-ryantm/nixpkgs/archive/251b2195f0e407042146f5100792a7524cbe653e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/s6dpvfh3kwvdilrp1k4x0mzvw5cm5638-jackett-0.20.915
ls -la /nix/store/s6dpvfh3kwvdilrp1k4x0mzvw5cm5638-jackett-0.20.915/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

jackett

Maintainer pings
cc @edwtjo @nyanloutre @purcell for testing.

Why this package dont receive automatic updates anymore? Can I help with this?

I make a PR to unlock this. https://github.com/NixOS/nixpkgs/pull/182847
If it is ok I propose myself as additional maintainer


idp: Add support for certificate bundles

When defining a custom hostname for the identity provider, we need to
support a ca-bundle file to be used when making requests to the server.

https://asciinema.org/a/tSA28OuNKshJz1ihmIKox2MPJ
https://asciinema.org/a/eWfw7AlgV4PwMQP8zKI7eMjfa

/cc @pvasant


Nick: Watch bootstrapstudio.xyz

Nick requests the watch of the watch_keyword bootstrapstudio\.xyz. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

bootstrapstudio\.xyz has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by cocomac in Charcoal HQ


Adding rating feature for the feedback section.

Adding rating feature for the feedback section.

@subhadipbhowmik please assign me this issue


Failure to infer parameter type

TypeScript Version:  3.0.0-dev.20180704

Search Terms: parameter inference
For context, I'm trying to provide accurate typings for a JS library (Material UI). What follows is an extreme simplification of the problem, dealing with functions rather than components:
Code
const foo = <A>(f: (x: A) => void, x: A) => f(x);

foo(
  (x: (n: number) => void) => x(42),
  n => console.log(n)
);

Expected behavior:
Should infer the type of the n parameter of the second argument as number.
Actual behavior:
Infers n: any, which rightly fails when noImplicitAny is enabled. However the compiler clearly knows what the type of the n parameter should be... if it's annotated incorrectly, e.g.
(n: string) => console.log(n)

then we get an error saying
Argument of type '(x: (n: number) => void) => void' is not assignable to parameter of type '(x: (n: string) => void) => void'.
  Types of parameters 'x' and 'x' are incompatible.
    Types of parameters 'n' and 'n' are incompatible.
      Type 'number' is not assignable to type 'string'.

Playground Link

What is happening here is to infere the type of P, the compiler needs to know the type of bar and to know that it needs an inference for P, which at this point is not available.
You can explicitly specify the type argument to the call:
foo<{ bar(x: number): void }>({
    f(p) { },
    bar(x) { },
});

Conditional types do not contribute to inferences.


Grabbing Keys Requires Special privilidges

It is not ideal to require special permissions (and dangerous ones, at that) to be able to snoop keyboard events for a screen reader.
Other, more responsible screen readers, may use the official atspi method of capturing keys. There are a couple problems with this:

Keys will only be forwarded to the screen reader when an application is already accessible.
The long process of being passed from the kernel, to libinput to the window manager/DE, to an application, over DBus, finally to a screen reader is not very efficient.

Keys Only For "Good" Applications
Unless I am completely mistaken, and I very well might be (I encourage criticism): the action of forward keys to the screen reader is required to be implemented by the application or toolkit used for application development. Therefore, if there is some bug in the application which causes key events to not read, or if the application is not accessible at all, the user now has no ability to control their screen reader, resulting in a state where that application must be killed from a console for the user to continue using their computer normally.
I might be wrong, but I think somebody had this problem with Zoom on Linux recently. Maybe it's better now, or that wasn't the problem, but it sounded suspiciously familiar.
Long Process
In addition to essentially being optional for an application to send keys, even in the case that keys are forwarded properly, the latency can be a problem on low-power devices like a Raspberry Pi, or Pinebook Pro; areas which Linux normally excels in, but the accessibility infrastructure isn't suited for. To be clear, this is not any one person or organization's fault, just the way things are at this time.
Solution?
At this time, Odilia is interrupting keys at the kernel level, deciding whether to consume them, or pass them through to the rest of the input stack.
This has some very major disadvantages of its own.

It required access to a privileged interface (evdev, uinput), which causes serious security concerns among the more paranoid (myself included).
It does not respect keymaps, or language settings. When using a European or Russian keyboard, Odilia will still only be bale to bind to the English letter it thinks is represented by the incoming keycode. This is not ideal whatsoever.

At this time, it seems like the only solution, and I would certainly rather a very fast, annoying to configure screen reader than one which is slow/buggy but easy to configure.
Perhaps this bridge can be mended one day, but it would require two things to happen:

Allow a11y programs to capture key input before it is sent to the application (X11). (Side note: how would sudo prompts work? I see why this is complicated.)
Allow a11y programs to capture key input before it is sent to the application (Wayland). Same side not above stands.

Wayland could likely be extended with an a11y protocol extension. I'm not sure what the right idea with X11 may be, or if there is any existing solution to this problem on X.
Put your ideas here. Let's find a way that works best for everyone. A performant, secure screen reader is our goal, and we won't stop until we've got it.

Partially addressed by https://github.com/flatpak/xdg-desktop-portal/pull/711

Going to close this on merge of #99


Object Detection model performance on TensorRT

Hi, what would be the changes to be made in the object detection eval_ssd.py script, https://github.com/dusty-nv/pytorch-ssd/tree/01e0146eb835860cac71763727530d463af67894, for him to evaluate the model optimized by TensorRT. I already did the evaluation of the pytorch model but I would like to make the model that TensorRT optimizes, to compare later. Any help is appreciated.

Hi @Sgomes14843 , to use the TensorRT version, use the detectnet or detectnet.py programs from the jetson-inference repo.

@dusty-nv The detectnet.py script can do the same as this script https://github.com/dusty-nv/pytorch-ssd/blob/01e0146eb835860cac71763727530d463af67894/eval_ssd.py ?? Maybe I explained my question badly. Because what I want is to do what this eval_ssd script does in the pytorch model but in the tensorrt optimized model

You would need to either adapt eval_ssd to use jetson.inference.detectNet object, or integrate the dataset/label loading into detectnet.py.

Thanks I think I'll try the first option, to see if it's possible


FileSystemCache: new parameter size_limit

In environments with limited disk space available for cache and variable element size, it might be too unpredictable to use the existing threshold parameter. I therefore suggest to introduce a size_limit parameter that will be used in the _prune function. Since calculating cache size can be an expensive operation, this should be maintained as a non-decaying cache element, to be updated on cache updates.

@davidism Any input here?

close it via https://github.com/pallets/werkzeug/issues/1249


Timeout waiting for image buffer from camera

Hello,
We're more issues with some of our new cameras. We are consistently failing to get any data out of some of our ifm3d cameras. Not sure what it is or how related to other issues it is. The /tmp/ifm3d.WARNING log repeatedly logs "Timeout waiting for image buffer from camera":
W1208 00:59:17.567520  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:18.068783  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:18.570011  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:19.071226  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:19.572422  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:20.073669  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:20.574818  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:22.267246  8242 camera.cpp:593] Skipping Imager, null value -- should be string!
W1208 00:59:22.340270  8242 camera.cpp:593] Skipping SpatialFilter, null value -- should be string!
W1208 00:59:22.340303  8242 camera.cpp:593] Skipping TemporalFilter, null value -- should be string!
W1208 00:59:23.059981  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:23.561238  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:24.062542  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:24.563859  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:25.065052  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:25.566350  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:26.067569  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:26.568842  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:27.070117  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:27.571358  8242 frame_grabber_impl.hpp:286] Timeout waiting for image buffer from camera
W1208 00:59:29.458178  8242 camera.cpp:593] Skipping Imager, null value -- should be string!

Here's the output of ifm3d dump:
ifm3d_dump.txt
Note, we're able to ping the sensors no problem. This is a major, blocking issue that we need to resolve as quickly as possible.
Thanks,
John

Could you bring up your camera as follows:
$ IFM3D_VLOG=30 roslaunch ifm3d camera.launch

Let it run and timeout a few times as it is doing above. Then kill the process. Send over the output of /tmp/ifm3d.INFO.
NOTE: I won't be near a camera until about 10:30 AM EST tomorrow. Additionally, I am not sure I have access to the firmware version you are running, so, it may be hard (if not impossible) for me to duplicate your issue to take a look. None-the-less, if you can send over the verbose logging output I suggest above, I can do my best to make some inferences on what may be going on.

Also, I just wanted to double check, when the s/w is in this timeout loop, is the illumination unit on the front of the camera face pulsing or is it off?

Here's the ifm3d.INFO log:
ifm3d_info.txt
The camera light is pulsing, although at a significantly slower rate then the working cameras.

hmm, seems the log got overwritten somehow. Here's a better one:
ifm3d_info.txt

One more for good measure:
ifm3d_info.txt
Realized I was running the camera node in a background process, so that was screwing up the logs. It's getting late over here...

So, giving this a quick look, it looks symptomatic of not getting pixel data back from the camera. With the verbosity turned up like you have it, we would see a bunch of chatter coming back from the frame grabber indicating that it is processing pixel data.
As noted in an earlier comment, I do not have recent hardware nor firmware so I cannot really reproduce, but, to me it looks like the camera is thrashing while context switching between "edit mode" and "run mode". One thing you can try is to increase the timeout value. I think you have it set to 500 ms, maybe try 1000 ms -- I'm not optimistic that it will work, but it is a simple thing to try. My thinking is, it could just be the initial context switch from edit mode to run mode that needs a bit longer than .5 secs to bootstrap itself -- it is a shot in the dark. I'd expect subsequent calls to WaitForFrame to not timeout after .5 secs.
You can also try connecting to the camera with Vision Assistant and see if the pixel data are returned. If it works, which I expect it should, it can tell us that the usage paradigm on the camera side has changed since the last revision of ifm3d and ifm3d has to adapt. If VA does not work, then we can focus more on the camera side of the issue.

Due to the fact FW version 1.0.22 is available for download can we close this issue? For more details see Issue #56