Updated atom to 1.0.10

I think this broke atom, it doesn't start correctly: Uncaught TypeError: Cannot read property 'dispatch' of null

It seems like following module fails to compile: /nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app.asar/node_modules/atom-keymap/node_modules/pathwatcher/lib/main.js

Sorry if I'm doing something wrong at my end, but I can't seem to duplicated the error you are seeing. Atom 1.0.10 has been working fine, on two of my machines. I've attached my build output below. Let me know if I'm missing something.
I'm continuing to investigate, though.....
1] shaun@nixos> nix-env -f . -iA atom
installing ‘atom-1.0.10’
these derivations will be built:
  /nix/store/5qpgv4bh4v368cqh2pd35bqw2h4afmp6-atom-1.0.10.drv
building path(s) ‘/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10’
installing
post-installation fixup
patching ELF executables and libraries in /nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/bin/.atom-wrapped
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/bin/atom
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/bin/apm
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/libchromiumcontent.so
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/libgcrypt.so.11
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app.asar.unpacked/node_modules/symbols-view/vendor/ctags-win32.exe
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app.asar.unpacked/node_modules/symbols-view/vendor/ctags-darwin
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app.asar.unpacked/node_modules/symbols-view/vendor/ctags-linux
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/season/node_modules/cson-parser/node_modules/coffee-script/bin/coffee
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/season/node_modules/cson-parser/node_modules/coffee-script/bin/cake
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/season/node_modules/cson-parser/node_modules/coffee-script/lib/coffee-script/parser.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/season/bin/csonc
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/temp/node_modules/rimraf/bin.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/open/vendor/xdg-open
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/yargs/node_modules/window-size/cli.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/keytar/script/cibuild
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/asar-require/node_modules/asar/node_modules/mkdirp/bin/cmd.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/asar-require/node_modules/asar/node_modules/walkdir/test.sh
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/asar-require/node_modules/asar/bin/asar
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/async/lib/async.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/rimraf/bin.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/opener/opener.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/uid-number/get-uid-gid.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/columnify/node_modules/strip-ansi/cli.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/config-chain/index.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/mkdirp/bin/cmd.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/spdx/node_modules/spdx-license-ids/README.md
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/nopt/bin/nopt.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/node_modules/semver/bin/semver
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/gyptest.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/buildbot/buildbot_run.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/gyp.bat
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/samples/samples
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/gyp
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input_test.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/MSVSSettings_test.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/common_test.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/mac_tool.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/generator/msvs_test.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/win_tool.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/easy_xml_test.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/flock_tool.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/tools/emacs/run-unit-tests.sh
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/tools/pretty_vcproj.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/tools/graphviz.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/tools/pretty_sln.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/tools/pretty_gyp.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/setup.py
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/which/bin/which
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/sntp/LICENSE
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/sntp/Makefile
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/sntp/index.js
missing ELF header
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/sntp/lib/index.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/sntp/README.md
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/cryptiles/LICENSE
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/cryptiles/Makefile
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/cryptiles/index.js
missing ELF header
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/cryptiles/lib/index.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/hoek/LICENSE
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/hoek/Makefile
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/hoek/index.js
missing ELF header
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/hoek/lib/escape.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/hoek/lib/index.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/hoek/README.md
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/hoek/images/hoek.png
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/boom/LICENSE
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/boom/lib/index.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/boom/README.md
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/node_modules/boom/images/boom.png
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/LICENSE
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/lib/browser.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/lib/client.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/lib/index.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/lib/utils.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/lib/crypto.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/lib/server.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/README.md
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/images/hawk.png
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/hawk/images/logo.png
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/form-data/node_modules/async/support/sync-package-managers.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/ctype/tools/jsstyle
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/ctype/tools/jsl.conf
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/node-uuid/bin/uuid
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/node_modules/har-validator/bin/har-validator
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/index.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/release.sh
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/semver/bin/semver
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/bin/node-gyp-bin/node-gyp.cmd
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/bin/node-gyp-bin/node-gyp
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/bin/npm-cli.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/bin/npm
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/bin/read-package-json.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/configure
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/cli.js
missing ELF header
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/lib/utils/completion.sh
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/scripts/doc-build.sh
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/scripts/relocate.sh
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/scripts/update-authors.sh
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/scripts/clean-old.sh
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/scripts/index-build.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/scripts/install.sh
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/mv/node_modules/rimraf/bin.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/mv/node_modules/ncp/bin/ncp
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/ncp/bin/ncp
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/fs-plus/node_modules/rimraf/bin.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/bin/apm
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/bin/node
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/script/download-node.js
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/atom.sh
not an ELF executable
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/libnotify.so.4
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/libffmpegsumo.so
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/atom
gzipping man pages in /nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10
stripping (with flags -S) in /nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/bin
strip:/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/bin/.atom-wrapped: File format not recognized
strip:/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/bin/atom: File format not recognized
strip:/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/bin/apm: File format not recognized
patching script interpreter paths in /nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/bin/.atom-wrapped: interpreter directive changed from "/bin/bash" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/bash  "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/open/vendor/xdg-open: interpreter directive changed from "/bin/sh" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/sh  "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/keytar/script/cibuild: interpreter directive changed from "/bin/bash" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/bash  "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/asar-require/node_modules/asar/node_modules/walkdir/test.sh: interpreter directive changed from "/bin/sh" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/sh  "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/gyp: interpreter directive changed from "/bin/sh" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/sh  "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/gyp/tools/emacs/run-unit-tests.sh: interpreter directive changed from "/bin/sh" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/sh  "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/node_modules/request/release.sh: interpreter directive changed from "/bin/sh" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/sh  "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/bin/node-gyp-bin/node-gyp: interpreter directive changed from "/usr/bin/env sh" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/sh "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/bin/npm: interpreter directive changed from "/bin/sh" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/sh  "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/configure: interpreter directive changed from "/bin/bash" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/bash  "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/lib/utils/completion.sh: interpreter directive changed from "/bin/bash" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/bash  "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/scripts/doc-build.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/bash "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/scripts/relocate.sh: interpreter directive changed from "/bin/bash" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/bash  "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/scripts/update-authors.sh: interpreter directive changed from "/bin/sh" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/sh  "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/scripts/clean-old.sh: interpreter directive changed from "/bin/bash" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/bash  "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/node_modules/npm/scripts/install.sh: interpreter directive changed from "/bin/sh" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/sh  "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/apm/bin/apm: interpreter directive changed from "/bin/bash" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/bash  "
/nix/store/3bia8pf1mjjy0nrj5j9hrcp4908l3hm9-atom-1.0.10/share/atom/resources/app/atom.sh: interpreter directive changed from "/bin/bash" to "/nix/store/548wfw1i43glkx8lkyjmbg59h6127qky-bash-4.3-p39/bin/bash  "
building path(s) ‘/nix/store/01mnp073q8y9yyjvgl0dspisalhjysgr-user-environment’
created 380 symlinks in user environment

Did you try running it?

Yes. No issues. Your 1.0.11 branch works as well.
Nixos version: 16.03.git.b257949 (Emu)

Strange. Can you paste result of nix-store -qR /nix/store/s5xwlnxlzxfb5zllbzmrnybmp72iw1gz-atom-1.0.11/bin/atom: https://gist.github.com/a67e188e55a477c28faf
I'm running 15.09.189.a30ecea (Dingo) and the error is http://imgur.com/2X6Xyof

I run 15.09.189.a30ecea (Dingo) aswell and tested 1.0.10, it works here. I run KDE. @domenkozar maybe atom loads some bad cache, did you try start with a clean home directory? Maybe some cache files are placed under /var or /tmp too.

I tried with a new user and TMP / TMPDIR set to an empty directory.

My nix-store -qR output matches your output: https://gist.github.com/sbruce/a28f3da6355d6900a727
I'll try changing to 15.09.189.a30ecea (Dingo) and see if I can duplicate your errors.

It's trying to compile https://github.com/atom/node-pathwatcher but it fails. But, why does it work for you?

Funny thing is, Atom 1.0.4 still works but 1.0.5 fails to start.

Can you open developers tools and see if you have any errors?

Using ctrl+shift+I

I've updated Atom to 1.0.4, the last working version for me and few folks that also reported problems on #nixos IRC.

Sounds good. I didn't see any startup errors in Atom 1.0.10 on my system: http://imgur.com/dX7zd3m
I tried several different versions of Atom (1.0.4 though 1.0.10) and they all seem to work on my system.

Upstream is saying something is wrong with apm rebuild, we have to find how does atom invoke it and why it breaks.

@sbruce can you try running it like nix-shell -p atom --pure --command "atom" -I <path to where nixpkgs folder with atom_1_0_11 is in>

@domenkozar https://github.com/domenkozar Atom starts up without an
error. The console log, in Atom, is also empty.
On Thu, Sep 10, 2015 at 2:03 AM, Domen Kožar<EMAIL_ADDRESS>wrote:

@sbruce https://github.com/sbruce can you try running it like nix-shell
-p atom --pure --command "atom" -I
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/pull/9605#issuecomment-139157350.

I've tried 1.0.19, all the same :/ Tried many different things what could be wrong, can't figure out what's going on. Maybe time to package atom from source?

1.2.0-beta0 works again! as soon as it's released we can bump.

Actually even 1.1.0 works, pushed! Thanks for baring with me.


x/build: frequent connection reset by peer on darwin-arm64 builders since 2022-04-28

@golang/release, I know there has been some recent work to build out and stabilize the darwin/arm64 builders, but it looks like there are some growing pains w.r.t. the network connection in particular in their current configuration.
<EMAIL_ADDRESS>Get<EMAIL_ADDRESS>read tcp [2a00:79e1:abc:1a0d:4d2a:f1b0:e7f9:264d]:56615->[2607:f8b0:4006:809::2011]:443: read: connection reset by peer

greplogs -l -e '(?ms)\Adarwin-arm64-.*connection reset by peer' --since=2022-04-01
2022-05-03T16:36:45-a942556-94274d0/darwin-arm64-11_0-toothrot
2022-05-03T12:34:17-39d4317-a41e37f/darwin-arm64-12_0-toothrot
2022-05-02T17:49:12-39d8c21-d922c0a/darwin-arm64-12_0-toothrot
2022-05-02T17:05:14-477369d-64369c3/darwin-arm64-12_0-toothrot
2022-05-02T04:48:54-39d8c21-7a22c8a/darwin-arm64-12_0-toothrot
2022-04-29T20:16:31-477369d-3ce203d/darwin-arm64-12_0-toothrot
2022-04-28T20:11:37-39d4317-74f0009/darwin-arm64-12_0-toothrot

I've gotten them wired network access as of last Friday; I'll try to get them moved over in the next couple of days and we'll see if that helps.

OK, so, wired network access was not as easy to get as I had hoped. But it is finally done as of today.
I'm going to optimistically close this.


[install_ubuntu_common.sh] Improvement 201708

[ ] $CI_SOURCE_PATH is required. Defining it doesn't make sense and should be only needed on CI.
Workaround was to 1) clone this repo to the specific directory, 2) export the env var:

$ mkdir -p ~/link/github_repos/130s
$ git clone %this repo%
$ export CI_SOURCE_PATH=~/link/github_repos/130s/hut_10sqft
$ curl -s https://raw.githubusercontent.com/130s/hut_10sqft/master/script/install_ubuntu_common.sh | bash -s 130s-p50 false
:

In other words, installation using install_ubuntu_common.sh isn't formalized yet.

[ ] Java8 install fails without apt-get update above this line.

[ ] Java8 install fails without apt-get update above this line.
[ ] Script needs to not duplicate the commands that were already run previously, so that users can run the script multiple times.

[ ] Installing ssh via apt-get wasn't enough for p50. I needed sudo ufw allow 22.


Deprecation warnings logged in console

Describe the bug
Foundry logs about 100 deprecation warnings in a freshly created game world.
commons.js:2004 Error: You are accessing EffectWfrp4e#label which has been migrated to EffectWfrp4e#name
Deprecated since Version 11
Backwards-compatible support will be removed in Version 13
    at logCompatibilityWarning (commons.js:1993:19)
    at EffectWfrp4e._logDataFieldMigration (commons.js:8434:14)
    at EffectWfrp4e.get (commons.js:8906:28)
    at WFRP_Utility.runSingleEffect (wfrp4e.js:7536:59)
    at wfrp4e.js:15913:27
    at Array.forEach (<anonymous>)
    at ActorWfrp4e.runEffects (wfrp4e.js:15905:13)
    at ActorWfrp4e._calculateWounds (wfrp4e.js:14654:10)
    at ActorWfrp4e.checkWounds (wfrp4e.js:14542:25)
    at ActorWfrp4e.prepareNonVehicle (wfrp4e.js:13345:10)

To Reproduce
Create a new game world on v11 and launch it.
Screenshots

Version Numbers
Foundry: v11 304
wfrp4e: 6.5.9
wfrp4e-core: 3.1.4
wfrp4e-starter-set:  3.1.5
wfrp4e-rnhd: 3.0.7
wfrp4e-altdorf: 3.0.0

fixed in v7.0.0


envCache --get stackInfo returns empty on existing environment

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
yarn
If applicable, what version of Node.js are you using?
14.17.0
Amplify CLI Version
5.1.2
What operating system are you using?
Linux
Amplify Categories
Not applicable
Amplify Commands
Not applicable
Describe the bug
My CI fails on a "Preview" build step because the envCache --get stackInfo command returns empty on an existing environment. I can verify the stack exists under CloudFormation -> Stacks. I tried to replace the command with amplify env get --name ${ENV}, but to no avail. I also ran the latter in my local machine and I get the same output as the CI, namely, it won't find the environment. I'm suspecting it's because the environment was created for a "Preview", thus not a user-generated environment. Unfortunately, it renders this feature useless.
Expected behavior
Get the existing environment and use it to continue the build.
Reproduction steps
Run a Preview build.
GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

                                 # Initializing new Amplify environment: prch (amplify init)
2021-07-20T11:40:51.826Z [INFO]: Note: It is recommended to run this command from the root of your app directory
2021-07-20T11:40:58.271Z [WARNING]: - Initializing project in the cloud...
2021-07-20T11:40:58.342Z [INFO]:
                                 An error occurred when creating the CloudFormation stack
2021-07-20T11:40:58.344Z [WARNING]: ✖ Root stack creation failed
2021-07-20T11:40:58.349Z [INFO]: AlreadyExistsException: Stack [amplify-deepdubapp-prch-103126] already exists
                                     at Request.extractError (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/query.js:50:29)
                                     at Request.callListeners (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
                                     at Request.emit (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
                                     at Request.emit (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:688:14)
                                     at Request.transition (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10)
                                     at AcceptorStateMachine.runTo (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12)
                                     at /root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10
                                     at Request.<anonymous> (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9)
                                     at Request.<anonymous> (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:690:12)
                                     at Request.callListeners (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
                                     at Request.emit (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
                                     at Request.emit (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:688:14)
                                     at Request.transition (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10)
                                     at AcceptorStateMachine.runTo (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12)
                                     at /root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10
                                     at Request.<anonymous> (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9)
                                     at Request.<anonymous> (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:690:12)
                                     at Request.callListeners (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
                                     at callNextListener (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:96:12)
                                     at IncomingMessage.onEnd (/root/.nvm/versions/node/v12.21.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/event_listeners.js:336:13)
                                     at IncomingMessage.emit (events.js:326:22)
                                     at IncomingMessage.EventEmitter.emit (domain.js:483:12)
                                     at endReadableNT (_stream_readable.js:1241:12)
                                     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
                                   code: 'AlreadyExistsException',
                                   time: 2021-07-20T11:40:58.341Z,
                                   requestId: '1430a38b-6591-4d65-98bc-5ea580fc3f03',
                                   statusCode: 400,
                                   retryable: false,
                                   retryDelay: 30.883168292505147
                                 }
2021-07-20T11:40:58.365Z [ERROR]: !!! Build failed
2021-07-20T11:40:58.366Z [ERROR]: !!! Non-Zero Exit Code detected

Additional information
No response

This env cache param is related to amplify console. Transferring to their repo for more visibility.


inference time

Hi
Thanks for sharing. How much time does the model inference take?

Hi Zgq91!
Thank you for your interest. For information on the inference time, please refer to our recently updated paper.
Regards,
Kai

i wrote a script to infer a list of 183 images of 480*240. it took 634s.

Hi foxbeing7,
What type of GPU are you currently using?
Regards,
Kai

Hi foxbeing7,
What type of GPU are you currently using?
Regards, Kai

Hi , I'm using tesla V100 with 32G gpu memory.
BTW, is there any advices for speeding up I/O ?
Thanks for your reply.

Hi, in the paper, I used the RTX A5000, which is based on the Ampere architecture with 8,192 CUDA cores and a clock speed of 1695 MHz. The inference speed is 2.1s per image.
The RTX V100 is an older generation (Volta) with 5,120 cores and a 1530 MHz clock speed. The expected inference speed would roughly be 2.1 * (1695/1530) * (8192/5120) = 3.72s per image. I think this aligns with your results.
For speeding up I/O for training, you can consider: 1) loading all data into memory before training; 2) using lmdb for training; 3) using an SSD.
I didn't experience any bottlenecks with I/O during my training.
Regards,
Kai

Hi, in the paper, I used the RTX A5000, which is based on the Ampere architecture with 8,192 CUDA cores and a clock speed of 1695 MHz. The inference speed is 2.1s per image.
The RTX V100 is an older generation (Volta) with 5,120 cores and a 1530 MHz clock speed. The expected inference speed would roughly be 2.1 * (1695/1530) * (8192/5120) = 3.72s per image. I think this aligns with your results.
For speeding up I/O for training, you can consider: 1) loading all data into memory before training; 2) using lmdb for training; 3) using an SSD.
I didn't experience any bottlenecks with I/O during my training.
Regards, Kai

I will try it later, thanks for the advice

And what is the inference Speed, when you upscale real-world Content, which is not 240p ?
What if you wan't to upscale 720p content? 720p has 9 times more pixel. Does that mean, inference time is 9 times higher and therefore ~18 secondens for one single frame with an RTX A5000 ? So basically 0.056FPS ?

And what is the inference Speed, when you upscale real-world Content, which is not 240p ?
What if you wan't to upscale 720p content? 720p has 9 times more pixel. Does that mean, inference time is 9 times higher and therefore ~18 secondens for one single frame with an RTX A5000 ? So basically 0.056FPS ?

It will likely cost that much time. Sometimes the bottleneck is at the pipeline, so I guess it will not scale linearly. Nevertheless, I will make a demo code and try it on 720p content shortly.


Minification at dev mode

In older versions dev mode worked with minifaction, but now every fina js is loades on a separated request. Would be nice if this feature work again.
Thank you

We have never had minification in dev, neither bundling. We are still loading third-party dependencies, such as Angular, Rxjs and others, with a single request using their bundle.
Probably in future we'll introduce something like SystemJS HMR or Angular hot loading.

@mgechev Sorry, I was talking about this #400

No problem. This issue should be addressed with final, let me know if you still see all your @angular/* files loaded separately.

Sorry I did not understand.
About final you mean angular 2 final version?
I'm using the last version of angular-seed master branch

Yes, currently we load the Angular bundles so #400 is addressed by the current version of the seed.

We have never loaded the files from src/client/app as a single bundle. Currently the application that I'm working on has a couple of hundreds of files which slows the refresh and I know what you are talking about. At some point we'll think about an optimization which will make the dev process faster.

Hi @mgechev it's exactly what you said, thank you for your support!

Hi @mgechev I just checked, it's only libs from node modules and my own files

It'll be best if we bundle all the app files and produce a single file. It will be loaded together with libraries and everything will be much faster. In the past I've used this. I haven't researched for anything SystemJS-related.


EXSWHTEC-102 - Implement tests for hipMemcpyParam2D APIs

Implement basic behavior checks in all copy directions
Implement synchronization behavior checks for expected behavior based on cuda docs
Implement positive tests for zero sized width and/or height copies, where no copy is expected to happen
Implement negative parameter tests
Implement all of the above for hipMemcpyParam2D and hipMemcpyParam2DAsync.

Depends-on: #3013

PR moved to: https://github.com/ROCm-Developer-Tools/hip-tests/pull/54


Add a property headers to TargetType?

I think it's better adding a headers property to TargetType protocol, it seems like the following:
var headers: [String : String]?

Say that there is an authentication token we need for case isAuthenticationRequired, we have to provide an endpoint when initialize MoyaProvider.
let endpointClosure = { (target: MyTarget) -> Endpoint<MyTarget> in
    let defaultEndpoint = MoyaProvider.defaultEndpointMapping(for: target)

    switch target {
    case .isAuthenticationRequired:
        return defaultEndpoint.adding(newHTTPHeaderFields: ["AUTHENTICATION_TOKEN": GlobalAppStorage.authToken])
    default:
        return defaultEndpoint.adding
    }
}

let provider = MoyaProvider<GitHub>(endpointClosure: endpointClosure)

Having the headers property set, I would't have to write the endpoint, I just need to write the code in MyTarget:
var headers: [String : String]? = {
    switch self {
    case .isAuthenticationRequired:
        return  ["AUTHENTICATION_TOKEN" : GlobalAppStorage.authToken]
    default:
        return nil
    }
}

@EvilNOP Thanks for raising the idea 🙌  I've created #1067 with an initial implementation for headers inside TargetType. Feel free to review it and let us know what you think 😉

Implemented in #1067


Feature Request: Built-in List Drag/Drop Reordering

Feature Request:
Add built-in support for the Material list behavior spec that allows reordering of rows using a drag handle (video example). This may be a good candidate for addition to AnimatedList, since it is likely to be used in combination with animated row addition and removal.
Background:
iOS has had built-in support for drag/drop reordering of its list implementation since it first launched. This is trivial to use for developers: toggle a single boolean and implement 1 callback method to update the list's data model when rows are visually re-ordered.
This is a somewhat-documented part of Material design spec. It's a relatively common UX treatment and there is a Material icon designed specifically for this behavior. In addition, Material Components for iOS has an implementation of this functionality.
A cursory search indicates that early adopters of Flutter have requested this functionality a number of times, so it's clear there's already significant demand for this feature.

This is a feature of Material that hasn't been implemented yet. See https://material.io/guidelines/components/lists.html#lists-behavior

[List] Tiles may be moved between a list and drop target (similar to moving a file into a folder) and picked up and manually reordered within a list.

Updated the issue with the Material spec reference provided by HansMuller

An production-ready implementation using the existing framework will depend on three things:
[ ] support for limiting Draggables to a single axis
[ ] creating a list that wraps its contents with Draggables and DragTargets
[ ] making the list scroll when a drag reaches an edge

You also need to hide the item being dragged (but keep occupying the space) and animate the reorder.

@DaveShuckerow assigning to you since afaik you're already working on this 😄

Bumping this up to bucket 6 since Mulligan needs this for launch.  FYI @Hixie -- this is the bug that spawned the Scrollable.ensureVisible()

This was pretty easy to do by wrapping the list in an Overlay widget.

There are 3 a11y issues that we are working on resolving. ETA: by end of week.

It there an estimated date for this feature release?

Raising this to a blocker for mulligan. We forked the pull request, but we'll likely need the a11y fixes.
@DaveShuckerow mulligan will also need support for a leading widget. I made a comment in the pull request.

@DaveShuckerow, thanks for your work on this. I tried your pull request and have some feedback:

When dragging item down, it needs to be dragged too far for reorder to happen. Right now it seems that when draggin down the top border of dragged item must cross middle of next item for reorder to happen. It should be bottom border of dragged item crossing middle of next item.

There is no animation when dragging is finished - the item just pops in place

Vibration feels very off on iOS. Ideally it should be HapticFeedback.selectionClick(); at the beginning and during every reorder.

Think it should contain a space setting between each tile like "childPadding" or something. Think that could be usable.
I did add these lines to reordable_list.dart at line regio 313.
    List<Widget> _newChildren = [];
    children.forEach((child) {
      _newChildren.add(Container(padding: EdgeInsets.only(bottom: 1), child: child));
    });

Here:
// Wraps children in Row or Column, so that the children flow in
  // the widget's scrollDirection.
  Widget _buildContainerForScrollDirection({List<Widget> children}) {
    List<Widget> _newChildren = [];
    children.forEach((child) {
      _newChildren.add(Container(padding: EdgeInsets.only(bottom: 1), child: child));
    });
    switch (widget.scrollDirection) {
      case Axis.horizontal:
        return Row(children: _newChildren);
      case Axis.vertical:
      default:
        return Column(children: _newChildren);
    }
  }

@martinory this issue is long closed. Don't expect the right people to see it.
If you think this is a feature that should be added it is better to create a new issue.


Remove Find a Campaign button on mobile homepage

It doesn't functionally do anything since we results update as soon as you select them...
cc: @DFurnes

refs #1891

We should probs keep the button if JS fails for whatever reason. Can probably do some logic and remove the button if JS is working fine, otherwise keep it because then form works like a simple dropdown select of choices and then you need to click button to submit. cc: @DFurnes thoughts?

@weerd Unfortunately the query for the campaign finder is built on the client-side so there isn't an easy fallback. I know there were some informal discussions a long time back about making a "search" service that'd act as an intermediary between Solr and the client-side app but I don't think it's been prioritized.

 Okie doke! Been so long since I've touched the campaign finder, haha! Thanks for the reminder @DFurnes 💃


about/ and tags/ look broken

Looking at http://themes.gohugo.io/theme/hugo-theme-cactus-plus/ (and my attempt to use hugo-theme-cactus-plus), neither Tags nor About seem to work.
It's a shame, because I like your theme :)

Probably related to https://github.com/digitalcraftsman/hugo-cactus-theme/issues/20 .

@Yoric Thank you very much! I have merged your pull request 😉


Time Comparison

As suggested by @cncastillo, I'm submitting a pull request reverting the repository to the first commit where the benchmarking CI was running (https://github.com/JuliaHealth/KomaMRI.jl/commit/5b6e9fbbda2311e57f3988185f1d3b13eefe3da1) so we can get an official time comparison by running the benchmarks again. We're curious if the AMD time improvements seen after (https://github.com/JuliaHealth/KomaMRI.jl/commit/1457a4c3ae1e3e7cc40819c534d8c36620bccb75) are actually due to the changes in that commit or an AMD change.

When I merged, it looked like it ignored the git reset and only merged in the one commit that was ahead of the main branch. Just a second ...


fix: do not instantiate logger inside a method

Description:
This PR removes the problematic instantiation of a logger inside a method that is invoked repeatedly.
Related issue(s):
Fixes #2194
Notes for reviewer:

I couldn't run the integration tests as there were no instruction in the README. I saw errors when I ran task test locally: Error: Failed to construct client for IntegrationTestEnv
However, please let me know if anything else I should test/modify.
Checklist

[ ] Documented (Code comments, README, etc.)
[x] Tested (unit, integration, etc.)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 84.26%.  Consider uploading reports for the commit c4a4a4f to get more accurate results

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #2195      +/-   ##
===========================================
- Coverage    84.48%   84.26%   -0.23%
===========================================
  Files          305       53     -252
  Lines        76259    11432   -64827
===========================================
- Hits         64430     9633   -54797
+ Misses       11829     1799   -10030

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Hey leninmehedy,
This logger was only added to track the behavior after the fix we added. We agree to remove it at all. Will add a commit for this.


[Integration] MQTT

Support for custom entities from MQTT broker.
For example: https://www.home-assistant.io/integrations/sensor.mqtt/

tested and added.


Auto shutdown with car

HI Nisarg,
wanted to thank you for this awesome project.
I was able to run it on a combination of Raspberry Pi Zero 2 W and Suzuki XL6 Zeta 6 AT. It pairs almost instantly without any lag and delay.  You can add XL6 ZETA HU to the list of compatible cars .
My Only question is -
A) The moment i switch off the Car ignition, it should switch off the PI as well but i see PI keeps running thus draining the battery. Is this normal behaviour and if this impacts the longevity of device in any way.  is there any way that we can write in code that if there is no inut for 2 min ( example) it should shut it self down.
regards
Sushil

The assumption is that most cars will kill power on USB once ignition is off. But I know this is not true for all.
We can turn off the device when inactive. But if the power is always on, we might not have a nice way to restart the device automatically once the car starts again as it'd need a power cycle to start again. Any ideas on how and when we can restart the device again?

 But I know this is not true for all.
Any ideas on how and when we can restart the device again?

I would expect a code to integrate it with car ignition which i think might not be possible as we have no access to Car ECU .
so way around would be, for it to detect HU power state and proceed accordingly. So If HU is powered on.. it powered itself, If Off it switches itself Off.

so way around would be, for it to detect HU power state and proceed accordingly. So If HU is powered on.. it powered itself, If Off it switches itself Off.

I don't think we generally have an easy way to detect if HU is on/off, if the USB power is always on, especially if we shutdown the dongle in the first place.

My personal experience with Kia Sorento. The USB power shuts off a minute or two after you lock the doors. When you unlock the doors, the USB is powered again.

There's a crude solution to this problem:
Purchase a 12V relay and a cigarette lighter plug.
Disconnect the Pi's VCC 5V and connect it to the relay's control.
When the car starts, the cigarette lighter activates, the relay engages and conducts electricity.
The 5V VCC powers up, and the Pi starts.
This can achieve the functionality you want, but it's a rough solution.
Alternatively, you could purchase an ELM327 OBDII communicator to read the CAN bus signal for startup.
This is much more difficult and would be a different functionality altogether.
The above conversation was translated with the assistance of Claude.ai. I hope I've expressed my meaning clearly.
Thank you.

My experience with Tata Altroz is the car shuts off USB power ~5mins after the doors are locked.
My only concern is that we are not doing shutdown safely as the power is abrubtly switched off after locking the car. This may impact the raspberry pi board or the memory card in the long run.

In case the file system on the SD card is read only, and the full mini Linux environment runs entirely from the Pi's memory, sudden cutting the power is probably not an issue. The Raspberry Pi OS has a read only fs implementation just for this.
Does this project writes to the SD card anything during operation? I can imagine, there's some data related to the initial device pairing. But after that I guess it could run readonly. Maybe an initial setup could write that data to the SD card then switch to fully read only mode.

I think I've found the answer. In the buildroot config the root file system is not configured for read-write remount, and also the copied fstab file also specifies everything as ro. So this whole Linux environment and the proxy runs from memory. I think there should be no problem with cutting the power then.

Could the Pi scan for the cars Bluetooth Mac, and choose to activate or sleep based on that?

HI Nisarg,
wanted to thank you for this awesome project.
I was able to run it on a combination of Raspberry Pi Zero 2 W and Suzuki XL6 Zeta 6 AT. It pairs almost instantly without any lag and delay. You can add XL6 ZETA HU to the list of compatible cars .
My Only question is -
A) The moment i switch off the Car ignition, it should switch off the PI as well but i see PI keeps running thus draining the battery. Is this normal behaviour and if this impacts the longevity of device in any way. is there any way that we can write in code that if there is no inut for 2 min ( example) it should shut it self down.
regards Sushil

Hello @sushilmudgil , Suzuki cars shutoff the poower to the Android Auto in approximately 30 to 60 seconds after the ignition is off and the doors are locked from outside. I have a 2019 Baleno and the Pi BOard shuts off in approximately 30 seconds after doors are locked. Kindly check and it should be the same in XL6 as well.

I've got a Renault Zoe (EV) that's parked on my drive.
the USB ports seem to be either always powered or powered when charging.
this means that my phone connects to it while I'm near the front of my house and even upstairs in the bedroom and I have to either remember to unplug it when I leave the car or turn off WiFi and Bluetooth on my phone.
The super hacky but unfriendly way to the pi that I'm planning on trying Is a usb cable with a switch inline.
I'll still need to remember to switch it to off before leaving the car but this is at least slightly more friendly than unplugging and plugging a usb cable in each time

Could the Pi scan for the cars Bluetooth Mac, and choose to activate or sleep based on that?

This is a great idea as my cars Bluetooth turns of when I open the door and would totally solve me issue!
It could scan for my Renault Bluetooth and if its found can resume normal operation, if it doesn't it goes into standby until it sees Renault again?

@puregreen59 I faced the same problem and solved with this setup.

Hello @sushilmudgil , Suzuki cars shutoff the poower to the Android Auto in approximately 30 to 60 seconds after the ignition is off and the doors are locked from outside. I have a 2019 Baleno and the Pi BOard shuts off in approximately 30 seconds after doors are locked. Kindly check and it should be the same in XL6 as well.

@abhi18588 you are right . I realised later on. Just forget to update here Between i did few really long drives .. 10 hrs at stretch and it did not even crashed or rebooted once with maps & amazon music on all the time.


Support input[type=text]

Seems to work fine with normal text inputs.

Hi @pafcu, thanks for the patch.
Sorry for my late reply. I don't have enough time to check the behavior. Can you show me a screenshot which shows the plugin working with input[type=text]?

I also added support for fixed input elements now. See https://github.com/yuku-t/jquery-textcomplete/issues/151.

LGTM thanks

Thanks for merging! I noticed that the combined JS in dist also needs updating. Should I submit a new pull request for that, or will you do it?

I'll do it. :)


Configure building with VS2022

We're now using vcpkg to manage dependencies (except imgui because that one is silly)!
This should allow us to build with VS2022 and thus make awesome Maya C++ plugin.
TODO:

[ ] Update README to reflect build setup + dependencies
[ ] See if imgui can be done through vcpkg

Built after reinstalling VS and then cleaning and rebuilding to have OpenGL actually show up


Dead 'docs' link

The docs link refers to https://react-basic-starter.github.io

This is currently dead. The docs also say that it's WIP. If there are no docs at all, I'd suggest removing the link for now. If there are docs, I'd add fix the links (even if WIP) instead.

Do we want to drop the second sentence from the paragraph with the dead link for now? Should I provide such a PR?

Same with https://github.com/spicydonuts/purescript-react-basic-hooks

Sorry, I'm not sure when we'll get to this. It's definitely something that needs to be done, but we haven't been able to set aside the time for it yet. In the meantime I've updated the readme to be a little more helpful than a dead link.


security-secretstore-setup: refactor to remove LoggingClient global variable

Fixes: https://github.com/edgexfoundry/edgex-go/issues/2127
Dependency on (includes work from) https://github.com/edgexfoundry/edgex-go/pull/2126. That PR must be reviewed and merged prior to this one.

Codecov Report

Merging #2129 into master will decrease coverage by 0.34%.
The diff coverage is 7.26%.

@@            Coverage Diff             @@
##           master    #2129      +/-   ##
==========================================
- Coverage   41.77%   41.42%   -0.35%
==========================================
  Files         182      183       +1
  Lines       12156    12277     +121
==========================================
+ Hits         5078     5086       +8
- Misses       6781     6894     +113
  Partials      297      297

Impacted Files
Coverage Δ

internal/security/proxy/init.go
0% <ø> (ø)
:arrow_up:

internal/security/secretstore/init.go
0% <0%> (ø)
:arrow_up:

internal/security/secretstore/config.go
0% <0%> (ø)

internal/security/secretstore/certs.go
20.33% <33.33%> (+2.79%)
:arrow_up:

internal/security/secretstore/requester.go
30% <33.33%> (ø)
:arrow_up:

internal/security/secretstore/password.go
29.46% <33.33%> (+2.61%)
:arrow_up:

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 5946931...1ed8cba. Read the comment docs.

Rebased


Promise.promisify fails on fs.createReadStream

Hi,
I just wanted to checkout this library and played a little bit with the pomisify stuff but it does not work for all methods:
var Promise = require('bluebird');
var createReadStream = Promise.promisify(require('fs').createReadStream);

var p1 = createReadStream('app.js').then(console.log);

setTimeout(function() {
    console.log(p1);
}, 1000);

The p1 gets never fulfilled, no error, no success. I did test it for createWriteStream and it did not work, either.

Something to note here is that createReadStream can fail in the future, and even if you created the stream inside a promise chain the error will be reported uncatched (and your application die). This is quite unfortunate, for example in the case of a trying to open a missing file, you get a stream and in the next tick you get an exception.
You need to create a stream like this to avoid problems, although this is far from ideal:
function createReadStream(filename){
  return new Promise(function(resolve, reject){
    function onError(err){
      reject(err);
    }

    function onReadable(){
      cleanup();
      resolve(stream);
    }

    function cleanup(){
      stream.removeListener('readable', onReadable);
      stream.removeListener('error', onError);
    }

    var stream = fs.createReadStream(filename);
    stream.on('error', onError);
    stream.on('readable', function(){
      resolve(stream);
    });
  });
}

@petkaantonov have you give some thought about a proper way to make streams work well together with promises?

Your comment is really useful, thanks @manast !!

Regret digging up an old/closed thread, but I found @manast 's example useful and informative.
Hoping this will help anyone else who stumbles upon it: (tiny correction at the end)
function createReadStream(filename){
  return new Promise(function(resolve, reject){
    function onError(err){
      reject(err);
    }

    function onReadable(){
      cleanup();
      resolve(stream);
    }

    function cleanup(){
      stream.removeListener('error', onError);
      stream.removeListener('readable', onReadable);
    }

    var stream = fs.createReadStream(filename);
    stream.on('error', onError);
    stream.on('readable', onReadable);    // <-- small correction
  });
}

Expanded for the Writable case:
function createWriteStream(filename){
  return new Promise(function(resolve, reject){
    function onError(err){
      reject(err);
    }

    function onOpen(){
      cleanup();
      resolve(stream);
    }

    function cleanup(){
      stream.removeListener('error', onError);
      stream.removeListener('open', onOpen);
    }

    const stream = fs.createWriteStream(filename);
    stream.on('error', onError);
    stream.on('open', onOpen);
  });
}

Why is the cleanup needed here?


support a bit more of the dynamoDB ConditionExpression syntax

Adding support for a few things I needed to test a library I am using with Moto

Support for NOT() in the ConditionExpression
2: Support for #key ExpressionAttributeNames and :value ExpressionAttributeValues  placeholders in the condition expression
Support for #key = :value in the condition expression

Some examples are in the test cases.

Coverage increased (+0.03%) to 92.769% when pulling c1232a7a23b4022c008f273ea71e74b590056773 on gregsterin:better-support-for-ddb-expressions into 1095b7d94bdd46b1bb2dbff0122994baf94f2eeb on spulec:master.


Fix emails not being sent

Since ec36b330c44eecc9b345dccdd6daaf25f0a585bc, we have used I18n to get the
email_from value. Because initializers are loaded before I18n has been
configured with a load path, when the Devise.config.mailer_sender was set, it
received an I18n translation missing message, instead of the email address
string. This was then apparently used by Devise to set the Reply To field and
probably the From field.
When UserMailer and NoisyBatchInvitation mailer call I18n, it has had a load
path set and so override the From field with correct/valid values, but the
Reply To field isn't.
The result was that emails were probably being rejected either by our email
sending service (Amazon SES) or elsewhere, so emails weren't being sent to
users.
Reading the comment for Devise.config.mailer_sender, it isn't neccessary to set
it if you set a custom Devise.config.mailer, so I tried removing this call and
the reply_to was no longer set at all.
@dwhenry you might be affected by this bug.

Tested this on Integration, emails are sent and received as expected :+1:

Well played @jamiecobbett 🌟

Good find!
On Fri, 19 Feb 2016 at 08:32, Ben Lovell<EMAIL_ADDRESS>wrote:

Well played @jamiecobbett https://github.com/jamiecobbett 🌟
—
Reply to this email directly or view it on GitHub
https://github.com/alphagov/signonotron2/pull/476#issuecomment-186116873
.

--
Bradley Wright
Head of Technology, Digital Group
Government Digital Service
@bradwright


Keyword-only argument issues

Some issues I noticed while working on https://github.com/IronLanguages/ironpython3/issues/1015. The following examples need to be run in fresh ipy instances to exhibit the broken behavior.

Bad error message for missing keyword arguments:

def test(*, a): return a

test() # throws TypeError: test() takes no arguments (0 given)

When the call binds to a failure when a value in __kwdefaults__  is missing it still throws even if the value becomes available later on:

def test(*, a=1): return a

test.__kwdefaults__ = None
test() # throws TypeError as expected
test.__kwdefaults__ = {"a": 1}
assert test() == 1 # still throws the same TypeError as above

Not finding a value in __kwdefaults__ should throw a TypeError instead of returning None:

def test(*, a=1): return a

assert test() == 1
test.__kwdefaults__ = None
test() # should throw but returns None instead

PythonFunction.CalculatedCachedCompat takes into account the number of arguments in __kwdefaults__. I don't think this makes sense since __kwdefaults__ can be changed any time and there's no way to know.

More stuff I'm forgetting about...

Related PR: https://github.com/IronLanguages/ironpython3/pull/1018

I think all but the first issue were resolved by https://github.com/IronLanguages/ironpython3/pull/1516.


Add non-root user account to Pulumi image

For the pu/pu image to support non-root execution (a security best practice, and supported by PKOv2), we need to add a local user to the image.
Ideally we wouldn't have separate "nonroot" images (see the "distroless" images).  Otherwise the defaulting logic would be more tricky.
One possibility is to add the local user as shown below but avoid using the USER instruction. I think that's sufficient for purposes of PKOv2, because the pod can apply a security context. The USER instruction seems to set the default, which might be considered a breaking change for existing users of the pu/pu image.
Here's an example of the Dockerfile commands:
ARG BASE_IMAGE=pulumi/pulumi:latest
FROM ${BASE_IMAGE}
ARG UID=1000
ARG GID=1000
RUN addgroup --gid $GID pulumi && \
    adduser --uid $UID --gid $GID --disabled-password --gecos "" pulumi && \
    echo 'pulumi ALL=(ALL) NOPASSWD: ALL' >> /etc/sudoers
USER pulumi:pulumi

And an example of the pod security context:
  securityContext:
    runAsGroup: 1000
    runAsNonRoot: true
    runAsUser: 1000

Added to epic https://github.com/pulumi/pulumi-kubernetes-operator/issues/586

TODO: add securityProfile to stack spec, to allow the workspace's profile to be configured.

A nonroot variant of the kitchen sink image will be available soon:
https://github.com/pulumi/pulumi-docker-containers/pull/277
I believe the remaining work on the PKO side is to use the correct default based on the security profile:

"restricted" - pulumi/pulumi:latest-nonroot
"baseline" - pulumi/pulumi:latest

The latest-nonroot tag is now published https://hub.docker.com/r/pulumi/pulumi/tags

Resolved by #693, #692 and https://github.com/pulumi/pulumi-docker-containers/pull/277.


Update virtual-machines-automation-with-chef.md

Submitted 1 more change

Hi @diegoviso, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;


tachidesk: init at 0.6.3

Description of changes

Tachidesk enables non andoird users to use tachiyomi to read manga.
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

btw thanks, i just wanted to request :)

any progress adding tachiyomi to the main repo? :(


Point cloud view go blank if enable intel graphic multi-sample anti-aliasing

Enabling Intel Graphics multi-sample anti-aliasing (Use Application Settings) will cause VeloView point cloud view become blank. VeloView will only work normal if disable/turn off the multi-sample anti-aliasing. Tested version is 3.5.3-36-g9e4f067. However, official version 3.5.0 work perfectly either enable or disable the anti-aliasing.

Hello,
Thank you very much for this detailed bug report. We recently modified the openGL pipeline to improve the rendering performances, I guess the bug you reported is related. We will investigate.
Thanks again
Regards,
Pierre Guilbert

Great thanks. :)

The bug has been introduced in paraview 5.4 and corrected in paraview 5.5. The next VeloView release will depend on Paraview 5.5 and the problem should be solved
Regards,
Pierre Guilbert


ImportError: No module named rospy

Required Info

Camera Model
T235

Firmware Version
RealSense ROS

Operating System & Version
Ubuntu 18.04 LTS

Kernel Version (Linux Only)
Linux 4.9.140-tegra aarch64

Platform
NVIDIA Jetson

SDK Version
JetPack 3.3.1

I am following the steps from below...
https://www.intelrealsense.com/how-to-multiple-camera-setup-with-ros/
I have both my T265 and D435 camera's running as per step 2:
On Step 3: I get the following error  "ImportError: No module named rospy" ?  Any idea's?  I had to use sudo to run..
Step3.txt

Well, you need to the rospy package
Have you tried sudo apt-get install -y python-rospy?
Not sure if it is available for Jetson, but this would be general ROS question, not directly related to RealSense.

Thank you for your help... I tried and I got a defiant reply...__________________________________lcs@nano:~/catkin_ws$ sudo apt-get install -y python-rospy[sudo] password for lcs: Reading package lists... DoneBuilding dependency tree       Reading state information... DoneSome packages could not be installed. This may mean that you haverequested an impossible situation or if you are using the unstabledistribution that some required packages have not yet been createdor been moved out of Incoming.The following information may help resolve the situation:
The following packages have unmet dependencies: python-rospy : Depends: python-roslib but it is not going to be installedE: Unable to correct problems, you have held broken packages.lcs@nano:~/catkin_ws$

On Tuesday, December 10, 2019, 12:29:58 PM EST, Sergey Dorodnicov<EMAIL_ADDRESS>wrote:

Well, you need to the rospy package
Have you tried sudo apt-get install -y python-rospy?
Not sure if it is available for Jetson, but this would be general ROS question, not directly related to RealSense.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Please close... this is probably an issue but I have gotten around needing it.

Please close... this is probably an issue but I have gotten around needing it.


test: add testcase for timestamp not in primary key

Which issue does this PR close?
Closes #
Rationale for this change
Ensure timestamp is in primary key

What changes are included in this PR?

Bump sqlness to https://github.com/CeresDB/sqlness/releases/tag/v0.3.0
Add tests for missing timestamp in primary key

Are there any user-facing changes?
No

How does this change test
New integration_tests

Codecov Report

Merging #619 (2d2bcce) into main (13c4a0b) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #619   +/-   ##
=======================================
  Coverage   66.01%   66.02%
=======================================
  Files         285      285
  Lines       44358    44358
=======================================
+ Hits        29285    29286    +1
+ Misses      15073    15072    -1

Impacted Files
Coverage Δ

common_types/src/schema.rs
96.34% <100.00%> (ø)

analytic_engine/src/row_iter/merge.rs
88.76% <0.00%> (+0.18%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Unit tests aren't running for several packages, and they are broken

Describe the bug

As part of the github action checks, unit tests are only running for at_lookup package (and only because I just added a job specifically for that)
If I run the unit tests locally for at_contact, at_onboarding_cli and at_server_status, the tests do not all pass cleanly for any of those packages

Steps to reproduce

Create a PR - unit tests will only run for at_lookup
Run the unit tests for at_contact, at_onboarding_cli and at_server_status locally - no package will run green

Expected behavior

All unit test packs should be run
And they should all pass

Screenshots
No response
Smartphones

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Were you using an atApplication when the bug was found?
No response
Additional context
No response

This was fixed a looooong time ago


Design Add Author API Specification

This task is to track the progress of add author API of the library management system.

API specification completed


Fix double flash message on native app.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1084

Relevant Lines:
1084

💛  - Coveralls


sanitize version

sanitizes the version field,
feature/JIRA-123.5 => feature-jira-123-5

Since the GAE ruleset is "lowercase letters, digits, and hyphens" and "must not exceed 63 characters", any thoughts on sanitizing any reasonable string to fit both of those?
Maybe just replace most of the common symbols and punctuation ({}()[]=+&%$*@?,"|) and also trum to 63 chars?

Yea I guess we could trim, and maybe replace a few more special characters but I’m hoping to keep this just a simple  replace. For example, if it ends in a special character, we wouldn’t handle that case

Not sure I follow how ending in a special char would be an issue. I was just suggesting adding those extra characters to the regex. It'd still be a simple find/replace.
As for the length, I figured we'd just check the length after the find/replace and truncate if needed, but we can always add that later.

For example, branch/name. (note the ending .); would result in branch-name- which is an invalid GAE version.
Again, I think it's an edge case and not something we should handle, we can revisit if this actually comes up in practice, but I'd expect mostly reasonable values 🤞 😁

I didnt realize ending with a symbol was also on their bad list. Makes sense.


lifecycle hook to wait until all terraform processes are completed

Lifecycle hooks are supported but it would be nice to add

either a default lifecycle to prevent terraform from being killed in the middle of an apply or plan

otherwise we could have resources created and the information is not saved into the tfstate
otherwise we could have stale dynamodb locks

or document the lifecycle hook to be optionally added

cc: @Balsir since you added the lifecycle feature to this repo, have you figured out a good preStop lifecycle ?
References

https://github.com/runatlantis/helm-charts/pull/220
https://kubernetes.io/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/

Yes, graceful termination should be implemented in the server. I was thinking this lifecycle method could be a nice workaround for now. :smile:

@nitrocode Should we close this issue and create one on the Atlantis repo?

I think we can have both issues. One here for lifecycle method and one for graceful termination in the server.

currently, this helm chart supports pod lifecycle hooks: https://github.com/runatlantis/helm-charts/blob/4afd2a82b1fcc31026c4c392e6984895818b3e62/charts/atlantis/values.yaml#L489-L490

This is what I came up with, let me know if seems okay and I will create a PR.
statefulSet:
  terminationGracePeriodSeconds: 180

lifecycle:
  preStop:
    exec:
      command:
        - /bin/bash
        - -c
        - while [ "$(pgrep -f terraform)" ]; do sleep 1; done


Rename VERSION parameter to prevent conflict with benchmark-operator…

…s VERSION
Signed-off-by: Raul Sevilla<EMAIL_ADDRESS>Description
Benchmark-operator's makefile uses VERSION as parameter, the upgrade workload is breaking CI.
Fixes

/rerun all

Results for e2e-benchmarking CI Tests

Workload
Test
Result
Runtime

router-perf-v2
ingress-performance.sh
PASS
00:04:35

etcd-perf
run_etcd_tests_fromgit.sh
PASS
00:02:45

scale-perf
run_scale_fromgit.sh
PASS
00:17:00

network-perf
smoke_test.sh
PASS
00:06:14

kube-burner
run_clusterdensity_test_fromgit.sh
PASS
00:06:28

kube-burner
run_maxnamespaces_test_fromgit.sh
PASS
00:02:34

kube-burner
run_maxservices_test_fromgit.sh
PASS
00:02:36

kube-burner
run_nodedensity_test_fromgit.sh
PASS
00:03:33

kube-burner
run_nodedensity-heavy_test_fromgit.sh
PASS
00:03:50

storage-perf
run_storage_tests_fromgit.sh
PASS
00:02:37

upgrade-perf
run_upgrade_fromgit.sh
PASS
00:00:56


[DEV-328] Allow additional specified teams to be added to a new repo …

…by default
This pull request adds the configuration option
config.handlers.github.additional_default_teams
which takes an array of slugs to be added by default whenever a new repo
is created.

Seems reasonable :basketball: swish

@theckman How does this look? I replaced the additional_default_teams config option with default_team_slugs. Either default_team_slug or default_team_slugs can be used now, but the former takes precedence over the latter.

What's the benefit of doing it this way, versus consolidating them in to one config option that takes an Array of strings? As someone who builds configs regularly using Chef, a single config option is much more enticing to me.

Just so that people's existing configs wouldn't break, but I guess I could wrap it in an array if it isn't already. I'll make the change then.

This project uses SemVer 2.0, and we're still at the v0 release which indicates things will break. We can cut a 0.2.0 release to try and make it easier on people. But being v0, I'd prefer we make it feel right and break stuff than try to work around it and make it painful later on.

That makes sense. Should I bother wrapping a string value in an array then, or just expect that the user will provide an array?

Actually, I think renaming default_team_slug to default_team_slugs would be logical here, and it follows that an array would be expected. I'll break the current configuration option.

@theckman How's this?

At a quick glance, this also seems reasonable to me.

My only outstanding "issue" is about whether we can make the extrapolate_create_opts method less complex by moving some stuff around.

:+1:


function to generate urls

I have added the ability to use a function in place of the urls option.
This allows the list of urls that are process to be dynamic.

hi @cburgdorf
can you please update this option in docs?
Thanks


SAKIII-5027 Line height in htmlblock widget is too cramped

https://jira.sakaiproject.org/browse/SAKIII-5027

Moved to https://github.com/sakaiproject/3akai-ux/pull/1705


fix: pass --mode argument to child build commands

What is it?

[ ] Feature / enhancement
[X] Bug
[ ] Docs / tests

Description
fixes https://github.com/BuilderIO/qwik/issues/3840
Currently its not possible to switch .env files based on custom vite --mode. This PR passes the mode argument from qwik build to qwik build.client, qwik build.server, qwik build.preview
Use cases and why
Cant currently create and specify custom .env files such as .env.staging
Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

Awesome! gonna merge right away!

Thanks @manucorporat !!


refactor(shadcn): removed empty interface

This change will not change any functionality, but will remove an empty interface increasing readability, and also just so happen to get around the eslint no empty object rule

@jonmejia if it's okay, I'd like to close this in favor of https://github.com/shadcn-ui/ui/pull/5657 which addresses the other instances as well. Feel free to reopen if you have any question.


Structuring name duplicate

I'm not sure of exact name for this syntax,  but [assuming ES6 is detected], should we allow both of these syntaxes:
{ x: x } and { x }?
Or should we force { x } if both the lhs and rhs match?

Right now, we're not actively pushing people toward ES6 features, so I'm -1.
If we end up detecting ES6 (discussion here: https://github.com/feross/standard/issues/159) then we should recommend { x } over { x: x } - agreed.

@dcousens ESLint calls this "object shorthand properties" and "object shorthand methods", and has an object-shorthand rule.


[Draft] HTML artifact

Create a result HTML artifact to let test easier HTML modifications.

Codecov Report

Merging #439 (a94d148) into main (22e5978) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #439   +/-   ##
=======================================
  Coverage   53.36%   53.36%
=======================================
  Files          44       44
  Lines        2732     2732
  Branches      522      522
=======================================
  Hits         1458     1458
  Misses       1163     1163
  Partials      111      111

Looks nice, is there a way to have a link to the artifact in the checks?

Looks nice, is there a way to have a link to the artifact in the checks?

Thanks !
That's what i'm looking for but it seems not possible on github to have a link, so i'm looking for a hack.

@Melvin-klein is there an artifact I can look at?

Exemple of link to the artifact : https://output.circle-artifacts.com/output/job/78494ad6-38ab-4dc5-8ab8-18bbf8006828/artifacts/0/result.html


Run out of free item slots occurred

Version: 1.2.0
Seed: R220-8125-Z1YJGG3
Version: Unknown
Seed: R220-ZAVX-Z9GA15G

Potentially fixed many with 88b0744f94fbf50f5410a1d74cf9602a3b5b0d67


[backport] support multi nics

Proposed changes
This is a backport pr:  https://github.com/rancher/ui/pull/4941
At the same time, for consistency, I cherry-pick the changes related to namesapce and external harvester

Types of changes

Linked Issues

Further comments

Hi, @mantis-toboggan-md   PTAL,  thanks
Note: This pr needs to wait for the backend pr merge before it can be merged .


Enable compression for OpenAPI spec download

Set appropriate headers to allow for gzip compression.
Discovered by Google's PageSpeed Insights: https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Frebilly.github.io%2FReDoc%2F&tab=mobile

The only file which is not compressed according to PageSpeed Insights is http://rebilly.github.io/SwaggerTemplateRepo/swagger.yaml. But this file is served from GitHub pages. I have no control over GitHub pages HTTP headers. GitHub auto gzips most of the files. But it seems that it doesn't gzips yaml files.
Closing this issue.


Token Marker Issues in OSE

Describe the bug
Sometimes the turn marker will appear in multiple positions or not appear at all on actors. Marker will not disappear upon combat completion. *edit: After further testing this issue will cause the actor count in combat to continuously toggle in group initiative when rolled at the top of each round in some instances. This will freeze combat the combat tracker.
To Reproduce
Steps to reproduce the behavior:

Run a world using the Old-School Essentials System
Create multiple actors and initiate combat
Flag combatants
Run through several turns. (It was quite a few before the toggling issue. 32-167 rounds in some instances or the first round in others)
Check console.
End Combat

Expected behavior
The marker should indicate the token corresponding to turn order.
Screenshots

Environment:

OS: MacOS Monterey 12.1
Browser chrome
Foundry Version 9 B242
Module Version 0.1.14
All Modules Disabled: No
Module List if no: libwrapper

Additional context
There is currently a bug being identified in OSE for multiple initiative rolls rather than just the group initiative. This will be evident in mass combat of 14 actors or extremely long combat. This can get intensive on the CPU and is being worked on as a top priority. *** The bug has since been fixed, but the issue still occurs of toggling the combatants continuously when Next Up is enabled.

The initiative issue in OSE has been gone, and I decided to take another stab at this. It seems like the turn marker function is causing an extra reroll and leaving a token marker on the last character in the character initiative list.


Improve performance of array integer indexing

This PR tries to improve performance of array integer indexing as a first step towards addressing #2878.
Since it seems like using jit as suggested in #2891 is difficult I've limited this PR to the case of indexing using a single Python integer outside of jit to keep the diff somewhat manageable. Some of the changes should also benefit other cases.
I split the PR into multiple commits that are best reviewed one by one. Also please let me know if these changes would prevent future planned optimisation that I am not aware of. If so I'm happy to close this, or split out some of the optimisation into separate PR's.
Changes

09134b36bd0a3a6fc10609b8a7a28d93c69b2e93 prevents the conversion of Python integers to DeviceArrays and uses plain Python code in favour of lax operations for index normalisation when possible. This moves the scalar index computations to the CPU instead of running on an accelerator. I currently can't easily measure the performance impact of this but for me this seems to be preferred for statically known indices.
75a092e027b26bcecf832c8cbfe088e98ec8c08d prevents unnecessary calls to lax.expand_dims
b8d70d31a5187c3c4cf72743b3f96a9026627904 removes explicit conversion using asarray
cf8e8ed46062fce095ce76b001626a4d3c248a3f and 19ac51e10339c465f7c40ea3b9acb966320c07a0 remove expensive calls to core.get_aval to speedup checks

Latency impact
I've measured indexing performance using a simple toy example on CPU:
from jax import numpy as jnp

a = jnp.arange(4000)
a[5]
%timeit a[6].block_until_ready()

This PR improves performance by a factor of 4.8x. Jax is still a lot slower than plain numpy but this already seems like a decent improvement.

commit
time
reduction

88ac4edf63625db10f92d5368a598205aac1deb4 (main baseline)
468 µs

09134b36bd0a3a6fc10609b8a7a28d93c69b2e93
225 µs
- 52 %

75a092e027b26bcecf832c8cbfe088e98ec8c08d
168 µs
- 25 %

b8d70d31a5187c3c4cf72743b3f96a9026627904
143 µs
- 15 %

cf8e8ed46062fce095ce76b001626a4d3c248a3f
125 µs
- 13 %

19ac51e10339c465f7c40ea3b9acb966320c07a0
98 µs
- 22 %

Related: #10150

Just curious, does this PR affect performance after JIT?

Related: #10150

@jakevdp Thanks for mentioning that PR. I rebased and added a small test in 8054f426e13346d8c09022704761824651ef983c to ensure that only a gather operation is present when using constant integer indices.

It looks like this breaks some jax2tf tests, namely jax/experimental/jax2tf/tests/shape_poly_test.py:ShapePolyPrimitivesTest.test_prim_getitem_op=poly_idx=slice-poly_noxla_poly_axes=[0] (this test is not run as part of the github CI)

For now I reverted 8e501651d54e765b4b65907e7612015be5e0263e which should fix the broken test.

Thanks for the updates.
So, overall my concern here is that this PR touches a lot of parts of the code, all of which have potential side-effects that are difficult for me to predict. The passing tests are a good sign, but I'm not confident that our test coverage is complete when it comes to things like all the various ways that arrays can be indexed. A PR like this seems ripe for unanticipated and unintended downstream consequences.
Unfortunately, I'm not really sure what to suggest – it's hard to check for unknown issues. I'll pull-in the changes and run a larger suite of internal tests in case that shows us something.

Well, additional testing didn't find any failures. I think we're in good shape

Thanks for the detailed review and the help!
In case any unforeseen problems arise, I'm happy to take another look or extract  10addfd040acbbd1972a6697bf9c8134a1248043 and 38cee9f68644cb27307513ad56f2dad9134b5259 into separate PRs.


Export more internal utils from react package

Is your feature request related to a problem? Please describe.
The composable nature of the hooks system in @floating-ui/react makes it fairly easy to replace a hook with custom implementation, be the reason just for debugging or some functional need. Doing this is a bit complex right now, since most of the hooks use a bunch of internal utility functions and hooks. Copying useListNavigation to my codebase to debug/test some changes, for example, also necessitates copy-pasting 12 utility functions from different files.
Describe the solution you'd like
Make it easier to copy a hook to consumer codebase without all the utility functions (those can be copied and modified separately, if necessary!) by exporting the utilities from the library, as just replacing the imports is much easier than copying all of the source:
import { activeElement, contains, ... } from '@floating-ui/react';

Describe alternatives you've considered
Exporting the internal utilities from the main library entrypoint may not be wanted, since I would say they are in a gray area in terms of semver - as they are mostly for internal use, you likely do not want to do major releases just to overhaul some utility functions.
Alternatives would be:

Add a separate entrypoint for the internal utils, e.g. import { activeElement, contains, ... } from '@floating-ui/react/internal';. This could then be clearly documented that this entrypoint does not necessarily follow semver.
Move the internal utils to a separate package, e.g. import { activeElement, contains, ... } from '@floating-ui/react-internal';. A separate package could stay on 0.x forever, meaning it can always introduce breaking changes.

Additional context
None.

There are a few places where functions in dependencies need to be re-used by the dependants, but can't and need to be copied. I think a 0.0.x versioned @floating-ui/utils package is a good idea.

<EMAIL_ADDRESS>splits most utils into @floating-ui/utils package, non-useful internal ones aren't exported though


Post title

Could you guide me how to change blog post url that is postX.html to custom name. thank you :+1:  :smiley:
Nice theme

It took some time to find the trick to do it :+1:  Newbie so i guess that is why.
Solved it by changing the the post file title appropriately.
THANKS AGAIN :+1:


Prevent loading resource in template

When I have a template in my html like this:

There is always a request going to something like /PhotoPath/%7B%7B:%20Name%7D%7D
Is there something I can do to prevent this from happening?

That should not happen. It works for me. If you can't figure it out, create a jsfiddle showing the issue.

Sorry, you're right. I'm using another component which depends on jsrender so I should check better where the issue originates.
My test case for the interested: https://codepen.io/jogai/pen/NJYrZB


POSIX compliant shell

Is it possible to make this shell-independent?
/wait-for-it.sh: line 70: syntax error: unexpected "(" (expecting ";;")

This would be particularly useful to run it with alpine, which uses busybox.

@iturgeon have you looked into this too?

Strange, I don't think my alpine 3.3 container complained about this line.

Yes, I've added this too as a workaround.

To add to @iturgeon's comment,
I also fixed this issue by replacing sh /code/wait-for-it.sh .... with bash /code/wait-for-it.sh ...

Since this issue is open for while. Let me share a tool I have written in Go with cross platform support and which has the same purpose of this project (even the name is the same) https://github.com/maxcnunes/waitforit.

What's great in shell script is that you just add one file to your directory and if you have bash that's it. Since your script is written in go, and go is a part of docker, it can be executed without a shell, right?

For UNIX systems the approach of this project is really straight forward. But it may start to be a bit complicated to maintain this approach once:

need to add support for different OS and platforms
need to add new features such as supporting http code checking (may would depend on third party tools such as curl)
An approach in Go solve those problems because it generates a binary. So to add support for a new OS/platform would only be required to build a binary for that target. And adding new features is simple because in most cases would require using a Go built in package or maybe another external package. But that would not be a problem for different OS/platform because of the binary.
PS: The built binary does not need Go installed in the machine to be able to run. Is a totally self contained executable.

I meant you can build it using a Dockerfile, without the need to download, right?

It would be great if it was shipped with alpine.

OS support is irrelevant, since bash would be supported in windows and Docker doesn't currently support any other platform except linux (windows 2016 is still not released).

I don't think so you have access to Go from the Dockerfile. Because the Docker running the build on the Dockerfile is already a built binary. Does not have all the Golang support to build a new binary.
OS support is relevante if you think it depend on third party tools. For instance bash itself is not available in all images by default. You would still need to install that at least. And as I said before, if it start to include new features such as the http status checking, it may start to depend on other tools as well. Which means, you have to include in your image more things than a single binary.
But if the these points I am bringing up does not concern you and the solution of this project works for you. Please than just use this one. It is a small and straight forward solution. 😄

I'm open to new solution. It's just that while it solves one problem (not having to have bash) it adds another (having to build or download a binary)

@Vanuan Just a reminder. If you don't want to your Dockefile be responsible to download the binary. You could also use COPY do add the binary from your file system.
Actually even with this tool you would end up with the same "problem": download or copy the script from the file system.

 I'm just sharing my thoughts

I'm not 😄  Just sharing some thoughts as well.

You guys are hijacking this thread, please stop.

Has anyone found a workaround for this? I just hit it in a python:3.7.2-alpine3.9 image.

im also getting this with a openjdk:8-jre manifold image

This doesn't work with classical shell (sh).
Docker image: php:fpm-alpine
Shell version BusyBox v1.31.1 () multi-call binary.
line 75: syntax error: unexpected "(" (expecting ";;")
WAITFORIT_hostport=(${1//:/ })
line 121: syntax error: unexpected "(" (expecting ";;")
WAITFORIT_CLI=("$@")
line 133: syntax error: bad substitution
    esac
done
//line 133
if [[ "$WAITFORIT_HOST" == "" || "$WAITFORIT_PORT" == "" ]]; then
    echoerr "Error: you need to provide a host and port to test."
    usage
fi


Use older variable names from<EMAIL_ADDRESS>

Fixes https://github.com/iTwin/itwinjs-backlog/issues/406

Run extract-api, lint, and rush change.