Update dependency node to v20

This PR contains the following updates:

Package
Update
Change

node
major
8.13.0 -> 20.9.0

Release Notes

nodejs/node (node)
v20.9.0: 2023-10-24, Version 20.9.0 'Iron' (LTS), @richardlau
Compare Source
Notable Changes
This release marks the transition of Node.js 20.x into Long Term Support (LTS)
with the codename 'Iron'. The 20.x release line now moves into "Active LTS"
and will remain so until October 2024. After that time, it will move into
"Maintenance" until end of life in April 2026.
Known issue
Collecting code coverage via the NODE_V8_COVERAGE environment variable may
lead to a hang. This is not thought to be a regression in Node.js 20 (some
reports are on Node.js 18). For more information, including some potential
workarounds, see issue #49344.
v20.8.1: 2023-10-13, Version 20.8.1 (Current), @RafaelGSS
Compare Source
This is a security release.
Notable Changes
The following CVEs are fixed in this release:

CVE-2023-44487: nghttp2 Security Release (High)
CVE-2023-45143: undici Security Release (High)
CVE-2023-39332: Path traversal through path stored in Uint8Array (High)
CVE-2023-39331: Permission model improperly protects against path traversal (High)
CVE-2023-38552:  Integrity checks according to policies can be circumvented (Medium)
CVE-2023-39333: Code injection via WebAssembly export names (Low)

More detailed information on each of the vulnerabilities can be found in October 2023 Security Releases blog post.
Commits

[c86883e844] - deps: update nghttp2 to 1.57.0 (James M Snell) #50121
[2860631359] - deps: update undici to v5.26.3 (Matteo Collina) #50153
[cd37838bf8] - lib: let deps require node prefixed modules (Matthew Aitken) #50047
[f5c90b2951] - module: fix code injection through export names (Tobias Nießen) nodejs-private/node-private#461
[fa5dae1944] - permission: fix Uint8Array path traversal (Tobias Nießen) nodejs-private/node-private#456
[cd35275111] - permission: improve path traversal protection (Tobias Nießen) nodejs-private/node-private#456
[a4cb7fc7c0] - policy: use tamper-proof integrity check function (Tobias Nießen) nodejs-private/node-private#462

v20.8.0: 2023-09-28, Version 20.8.0 (Current), @ruyadorno
Compare Source
Notable Changes
Stream performance improvements
Performance improvements to writable and readable streams, improving the creation and destruction by ±15% and reducing the memory overhead each stream takes in Node.js
Contributed by Benjamin Gruenbaum in #49745 and Raz Luvaton in #49834.
Performance improvements for readable webstream, improving readable stream async iterator consumption by ±140% and improving readable stream pipeTo consumption by ±60%
Contributed by Raz Luvaton in #49662 and #49690.
Rework of memory management in vm APIs with the importModuleDynamically option
This rework addressed a series of long-standing memory leaks and use-after-free issues in the following APIs that support importModuleDynamically:

vm.Script
vm.compileFunction
vm.SyntheticModule
vm.SourceTextModule

This should enable affected users (in particular Jest users) to upgrade from older versions of Node.js.
Contributed by Joyee Cheung in #48510.
Other notable changes

[32d4d29d02] - deps: add v8::Object::SetInternalFieldForNodeCore() (Joyee Cheung) #49874
[0e686d096b] - doc: deprecate fs.F_OK, fs.R_OK, fs.W_OK, fs.X_OK (Livia Medeiros) #49683
[a5dd057540] - doc: deprecate util.toUSVString (Yagiz Nizipli) #49725
[7b6a73172f] - doc: deprecate calling promisify on a function that returns a promise (Antoine du Hamel) #49647
[1beefd5f16] - esm: set all hooks as release candidate (Geoffrey Booth) #49597
[b0ce78a75b] - module: fix the leak in SourceTextModule and ContextifySript (Joyee Cheung) #48510
[4e578f8ab1] - module: fix leak of vm.SyntheticModule (Joyee Cheung) #48510
[69e4218772] - module: use symbol in WeakMap to manage host defined options (Joyee Cheung) #48510
[14ece0aa76] - (SEMVER-MINOR) src: allow embedders to override NODE_MODULE_VERSION (Cheng Zhao) #49279
[9fd67fbff0] - stream: use bitmap in writable state (Raz Luvaton) #49834
[0ccd4638ac] - stream: use bitmap in readable state (Benjamin Gruenbaum) #49745
[7c5e322346] - stream: improve webstream readable async iterator performance (Raz Luvaton) #49662
[80b342cc38] - (SEMVER-MINOR) test_runner: accept testOnly in run (Moshe Atlow) #49753
[17a05b141d] - (SEMVER-MINOR) test_runner: add junit reporter (Moshe Atlow) #49614

Commits

[4879e3fbbe] - benchmark: add a benchmark for read() of ReadableStreams (Debadree Chatterjee) #49622
[78a6c73157] - benchmark: shorten pipe-to by reducing number of chunks (Raz Luvaton) #49577
[4126a6e4c9] - benchmark: fix webstream pipe-to (Raz Luvaton) #49552
[6010a91825] - bootstrap: do not expand argv1 for snapshots (Joyee Cheung) #49506
[8480280c4b] - bootstrap: only use the isolate snapshot when compiling code cache (Joyee Cheung) #49288
[b30754aa87] - build: run embedtest using node executable (Joyee Cheung) #49506
[31db0b8e2b] - build: add --write-snapshot-as-array-literals to configure.py (Joyee Cheung) #49312
[6fcb51d3ba] - debugger: use internal/url.URL instead of url.parse (LiviaMedeiros) #49590
[32d4d29d02] - deps: add v8::Object::SetInternalFieldForNodeCore() (Joyee Cheung) #49874
[ad37cadc3f] - deps: V8: backport de9a5de (Joyee Cheung) #49703
[cdd1c66222] - deps: V8: cherry-pick b33bf2d (Joyee Cheung) #49703
[61d18d6473] - deps: update undici to 5.24.0 (Node.js GitHub Bot) #49559
[b8a4fef393] - deps: remove pthread-fixes.c from uv.gyp (Ben Noordhuis) #49744
[6c86c0683c] - deps: update googletest to d1467f5 (Node.js GitHub Bot) #49676
[1424404742] - deps: update nghttp2 to 1.56.0 (Node.js GitHub Bot) #49582
[15b54ff95d] - deps: update googletest to 8a6feab (Node.js GitHub Bot) #49463
[2ceab877c2] - deps: update corepack to 0.20.0 (Node.js GitHub Bot) #49464
[4814872ddc] - doc: fix DEP0176 number (LiviaMedeiros) #49858
[0e686d096b] - doc: deprecate fs.F_OK, fs.R_OK, fs.W_OK, fs.X_OK (Livia Medeiros) #49683
[5877c403a2] - doc: add mertcanaltin as a triager (mert.altin) #49826
[864fe56432] - doc: add git node backport way to the backporting guide (Raz Luvaton) #49760
[e0f93492d5] - doc: improve documentation about ICU data fallback (Joyee Cheung) #49666
[a5dd057540] - doc: deprecate util.toUSVString (Yagiz Nizipli) #49725
[774c1cfd52] - doc: add missing function call to example for util.promisify (Jungku Lee) #49719
[fe78a34845] - doc: update output of example in mimeParams.set() (Deokjin Kim) #49718
[4175ea33bd] - doc: add missed inspect with numericSeparator to example (Deokjin Kim) #49717
[3a88571972] - doc: fix history comments (Antoine du Hamel) #49701
[db4ab1ccbb] - doc: add missing history info for import.meta.resolve (Antoine du Hamel) #49700
[a304d1ee19] - doc: link maintaining deps to pull-request.md (Marco Ippolito) #49716
[35294486ad] - doc: fix print results in events (Jungku Lee) #49548
[9f0b0e15c9] - doc: alphabetize cli.md sections (Geoffrey Booth) #49668
[7b6a73172f] - doc: deprecate calling promisify on a function that returns a promise (Antoine du Hamel) #49647
[d316b32fff] - doc: update corepack.md to account for 0.20.0 changes (Antoine du Hamel) #49486
[c2eac7dc7c] - doc: remove @anonrig from performance initiative (Yagiz Nizipli) #49641
[3d839fbf87] - doc: mark Node.js 16 as End-of-Life (Richard Lau) #49651
[53fb5aead8] - doc: save user preference for JS flavor (Vidar Eldøy) #49526
[e3594d5658] - doc: update documentation for node:process warning (Shubham Pandey) #49517
[8e033c3963] - doc: rename possibly confusing variable and CSS class (Antoine du Hamel) #49536
[d0e0eb4bb3] - doc: update outdated history info (Antoine du Hamel) #49530
[b4724e2e3a] - doc: close a parenthesis (Sébastien Règne) #49525
[0471c5798e] - doc: cast GetInternalField() return type to v8::Value in addons.md (Joyee Cheung) #49439
[9f8bea3dda] - doc: fix documentation for input option in child_process (Ariel Weiss) #49481
[f3fea92f8a] - doc: fix missing imports in test.run code examples (Oshri Asulin) #49489
[e426b77b67] - doc: fix documentation for fs.createWriteStream highWaterMark option (Mert Can Altın) #49456
[2b119108ff] - doc: updated releasers instructions for node.js website (Claudio W) #49427
[b9d4a80183] - doc: edit import.meta.resolve documentation (Antoine du Hamel) #49247
[f67433f666] - doc,tools: switch to @node-core/utils (Michaël Zasso) #49851
[142e256fc5] - errors: improve classRegExp in errors.js (Uzlopak) #49643
[6377f1bce2] - errors: use determineSpecificType in more error messages (Antoine du Hamel) #49580
[05f0fcb4c4] - esm: identify parent importing a url with invalid host (Jacob Smith) #49736
[8a6f5fb8f3] - esm: fix return type of import.meta.resolve (Antoine du Hamel) #49698
[a6140f1b8c] - esm: update loaders warning (Geoffrey Booth) #49633
[521a9327e0] - esm: fix support for URL instances in register (Antoine du Hamel) #49655
[3a9ea0925a] - esm: clarify ERR_REQUIRE_ESM errors (Daniel Compton) #49521
[1beefd5f16] - esm: set all hooks as release candidate (Geoffrey Booth) #49597
[be48267888] - esm: remove return value for Module.register (Antoine du Hamel) #49529
[e74a075124] - esm: refactor test-esm-loader-resolve-type (Geoffrey Booth) #49493
[17823b3533] - esm: refactor test-esm-named-exports (Geoffrey Booth) #49493
[f34bd15ac1] - esm: refactor mocking test (Geoffrey Booth) #49465
[ec323bbd99] - fs: replace SetMethodNoSideEffect in node_file (CanadaHonk) #49857
[6acf800123] - fs: improve error performance for unlinkSync (CanadaHonk) #49856
[31702c9403] - fs: improve readFileSync with file descriptors (Yagiz Nizipli) #49691
[835f9fe7b9] - fs: fix file descriptor validator (Yagiz Nizipli) #49752
[b618fe262f] - fs: improve error performance of opendirSync (Yagiz Nizipli) #49705
[938471ef55] - fs: improve error performance of sync methods (Yagiz Nizipli) #49593
[db3fc6d087] - fs: fix readdir and opendir recursive with unknown file types (William Marlow) #49603
[0f020ed22d] - gyp: put cctest filenames in variables (Cheng Zhao) #49178
[0ce1e94d12] - lib: update encoding sets in WHATWG API (Jungku Lee) #49610
[efd6815a7a] - lib: fix internalBinding typings (Yagiz Nizipli) #49742
[1287d5b74e] - lib: allow byob reader for 'blob.stream()' (Debadree Chatterjee) #49713
[bbc710522d] - lib: reset the cwd cache before execution (Maël Nison) #49684
[f62d649e4d] - lib: use internal fileURLToPath (Deokjin Kim) #49558
[e515046941] - lib: use internal pathToFileURL (Livia Medeiros) #49553
[00608e8070] - lib: check SharedArrayBuffer availability in freeze_intrinsics.js (Milan Burda) #49482
[8bfbe7079c] - meta: fix linter error (Antoine du Hamel) #49755
[58f7a9e096] - meta: add primordials strategic initiative (Benjamin Gruenbaum) #49706
[5366027756] - meta: bump github/codeql-action from 2.21.2 to 2.21.5 (dependabot[bot]) #49438
[fe26b74082] - meta: bump rtCamp/action-slack-notify from 2.2.0 to 2.2.1 (dependabot[bot]) #49437
[b0ce78a75b] - module: fix the leak in SourceTextModule and ContextifySript (Joyee Cheung) #48510
[4e578f8ab1] - module: fix leak of vm.SyntheticModule (Joyee Cheung) #48510
[69e4218772] - module: use symbol in WeakMap to manage host defined options (Joyee Cheung) #48510
[96874e8fbc] - node-api: enable uncaught exceptions policy by default (Chengzhong Wu) #49313
[b931aeadfd] - perf_hooks: reduce overhead of new performance_entries (Vinicius Lourenço) #49803
[ad043bac31] - process: add custom dir support for heapsnapshot-signal (Jithil P Ponnan) #47854
[8a7c10194c] - repl: don't accumulate excess indentation in .load (Daniel X Moore) #49461
[10a2adeed5] - src: improve error message when ICU data cannot be initialized (Joyee Cheung) #49666
[ce37688bac] - src: remove unnecessary todo (Rafael Gonzaga) #49227
[f611583b71] - src: use SNAPSHOT_SERDES to log snapshot ser/deserialization (Joyee Cheung) #49637
[a597cb8457] - src: port Pipe to uv_pipe_bind2, uv_pipe_connect2 (Geoff Goodman) #49667
[fb21062338] - src: set --rehash-snapshot explicitly (Joyee Cheung) #49556
[14ece0aa76] - (SEMVER-MINOR) src: allow embedders to override NODE_MODULE_VERSION (Cheng Zhao) #49279
[4b5e23c71b] - src: set ModuleWrap internal fields only once (Joyee Cheung) #49391
[2d3f5c7cab] - src: fix fs_type_to_name default value (Mustafa Ateş Uzun) #49239
[cfbcb1059c] - src: fix comment on StreamResource (rogertyang) #49193
[39fb83ad16] - src: do not rely on the internal field being default to undefined (Joyee Cheung) #49413
[9fd67fbff0] - stream: use bitmap in writable state (Raz Luvaton) #49834
[0ccd4638ac] - stream: use bitmap in readable state (Benjamin Gruenbaum) #49745
[b29d927010] - stream: improve readable webstream pipeTo (Raz Luvaton) #49690
[7c5e322346] - stream: improve webstream readable async iterator performance (Raz Luvaton) #49662
[be211ef818] - test: deflake test-vm-contextified-script-leak (Joyee Cheung) #49710
[355f10dab2] - test: use checkIfCollectable in vm leak tests (Joyee Cheung) #49671
[17cfc531aa] - test: add checkIfCollectable to test/common/gc.js (Joyee Cheung) #49671
[e49a573752] - test: add os setPriority, getPriority test coverage (Wael) #38771
[5f02711522] - test: deflake test-runner-output (Moshe Atlow) #49878
[cd9754d6a7] - test: mark test-runner-output as flaky (Joyee Cheung) #49854
[5ad00424dd] - test: use mustSucceed instead of mustCall (SiddharthDevulapalli) #49788
[3db9b40081] - test: refactor test-readline-async-iterators into a benchmark (Shubham Pandey) #49237
[2cc5ad7859] - Revert "test: mark test-http-regr-gh-2928 as flaky" (Luigi Pinca) #49708
[e5185b053c] - test: use fs.constants for fs.access constants (Livia Medeiros) #49685
[b9e5b43462] - test: deflake test-http-regr-gh-2928 (Luigi Pinca) #49574
[1fffda504e] - test: fix argument computation in embedtest (Joyee Cheung) #49506
[6e56f2db52] - test: skip test-child-process-stdio-reuse-readable-stdio on Windows (Joyee Cheung) #49621
[ab3afb330d] - test: mark test-runner-watch-mode as flaky (Joyee Cheung) #49627
[185d9b50db] - test: deflake test-tls-socket-close (Luigi Pinca) #49575
[c70c74a9e6] - test: show more info on failure in test-cli-syntax-require.js (Joyee Cheung) #49561
[ed7c6d1114] - test: mark test-http-regr-gh-2928 as flaky (Joyee Cheung) #49565
[3599eebab9] - test: use spawnSyncAndExitWithoutError in sea tests (Joyee Cheung) #49543
[f79b153e89] - test: use spawnSyncAndExitWithoutError in test/common/sea.js (Joyee Cheung) #49543
[c079c73769] - test: use setImmediate() in test-heapdump-shadowrealm.js (Joyee Cheung) #49573
[667a92493c] - test: skip test-child-process-pipe-dataflow.js on Windows (Joyee Cheung) #49563
[91af0a9a3c] - Revert "test: ignore the copied entry_point.c" (Chengzhong Wu) #49515
[567afc71b8] - test: avoid copying test source files (Chengzhong Wu) #49515
[ced25a976d] - test: increase coverage of Module.register and initialize hook (Antoine du Hamel) #49532
[be02fbdb8a] - test: isolate globalPreload tests (Geoffrey Booth) #49545
[f214428845] - test: split test-crypto-dh to avoid timeout on slow machines in the CI (Joyee Cheung) #49492
[3987094569] - test: make test-dotenv-node-options locale-independent (Livia Medeiros) #49470
[34c1741792] - test: add test for urlstrings usage in node:fs (Livia Medeiros) #49471
[c3c6c4f007] - test: make test-worker-prof more robust (Joyee Cheung) #49274
[843df1a4da] - test,crypto: update WebCryptoAPI WPT (Filip Skokan) #49714
[80b342cc38] - (SEMVER-MINOR) test_runner: accept testOnly in run (Moshe Atlow) #49753
[76865515b9] - test_runner: fix test runner watch mode when no positional arguments (Moshe Atlow) #49578
[17a05b141d] - (SEMVER-MINOR) test_runner: add junit reporter (Moshe Atlow) #49614
[5672e38457] - test_runner: add jsdocs to mock.js (Caio Borghi) #49555
[b4d42a8f2b] - test_runner: fix invalid timer call (Erick Wendel) #49477
[f755e6786b] - test_runner: add jsdocs to MockTimers (Erick Wendel) #49476
[e7285d4bf0] - test_runner: fix typescript coverage (Moshe Atlow) #49406
[07a2e29bf3] - tools: support updating @reporters/github manually (Moshe Atlow) #49871
[5ac6722031] - tools: skip ruff on tools/node_modules (Moshe Atlow) #49838
[462228bd24] - tools: fix uvwasi updater (Michael Dawson) #49682
[ff81bfb958] - tools: update lint-md-dependencies to<EMAIL_ADDRESS>(Node.js GitHub Bot) #49679
[08ffc6344c] - tools: restrict internal code from using public url module (LiviaMedeiros) #49590
[728ebf6c97] - tools: update eslint to 8.49.0 (Node.js GitHub Bot) #49586
[20d038ffb1] - tools: update lint-md-dependencies to<EMAIL_ADDRESS><EMAIL_ADDRESS>(Node.js GitHub Bot) #49584
[210c15bd12] - tools: allow passing absolute path of config.gypi in js2c (Cheng Zhao) #49162
[e341efe173] - tools: configure never-stale label correctly (Michaël Zasso) #49498
[a8a8a498ce] - tools: update doc dependencies (Node.js GitHub Bot) #49467
[ac06607f9e] - typings: fix missing property in ExportedHooks (Antoine du Hamel) #49567
[097b59807a] - url: improve invalid url performance (Yagiz Nizipli) #49692
[7c2060cfac] - util: add getCwdSafe internal util fn (João Lenon) #48434
[c23c60f545] - zlib: disable CRC32 SIMD optimization (Luigi Pinca) #49511

v20.7.0: 2023-09-18, Version 20.7.0 (Current), @UlisesGascon
Compare Source
Notable Changes

[022f1b70c1] - src: support multiple --env-file declarations (Yagiz Nizipli) #49542
[4a1d1cad61] - crypto: update root certificates to NSS 3.93 (Node.js GitHub Bot) #49341
[a1a65f593c] - deps: upgrade npm to 10.1.0 (npm team) #49570
[6c2480cad9] - (SEMVER-MINOR) deps: upgrade npm to 10.0.0 (npm team) #49423
[bef900e56b] - doc: move and rename loaders section (Geoffrey Booth) #49261
[db4ce8a593] - doc: add release key for Ulises Gascon (Ulises Gascón) #49196
[11c85ffa98] - (SEMVER-MINOR) lib: add api to detect whether source-maps are enabled (翠 / green) #46391
[ec51e25ed7] - src,permission: add multiple allow-fs-* flags (Carlos Espa) #49047
[efdc95fbc0] - (SEMVER-MINOR) test_runner: expose location of tests (Colin Ihrig) #48975

Commits

[e84515594e] - benchmark: use tmpdir.resolve() (Livia Medeiros) #49137
[f37444e896] - bootstrap: build code cache from deserialized isolate (Joyee Cheung) #49099
[af6dc1754d] - bootstrap: do not generate code cache in an unfinalized isolate (Joyee Cheung) #49108
[cade5716df] - build: add symlink to compile_commands.json file if needed (Juan José) #49260
[34a2590b05] - build: expand when we run internet tests (Michael Dawson) #49218
[f637fd46ab] - build: fix typo libray -> library (configure.py) (michalbiesek) #49106
[ef3d8dd493] - crypto: remove webcrypto EdDSA key checks and properties (Filip Skokan) #49408
[4a1d1cad61] - crypto: update root certificates to NSS 3.93 (Node.js GitHub Bot) #49341
[7eb10a38ea] - crypto: remove getDefaultEncoding() (Tobias Nießen) #49170
[772496c030] - crypto: remove default encoding from DiffieHellman (Tobias Nießen) #49169
[c795083232] - crypto: remove default encoding from Hash/Hmac (Tobias Nießen) #49167
[08197aa010] - crypto: remove default encoding from sign/verify (Tobias Nießen) #49145
[a1a65f593c] - deps: upgrade npm to 10.1.0 (npm team) #49570
[6c2480cad9] - (SEMVER-MINOR) deps: upgrade npm to 10.0.0 (npm team) #49423
[84195d9584] - deps: add missing thread-common.c in uv.gyp (Santiago Gimeno) #49410
[5b70b68b3d] - deps: V8: cherry-pick eadaef5 (Adam Majer) #49401
[fe34d632e8] - deps: update zlib to <IP_ADDRESS>-motley-f5fd0ad (Node.js GitHub Bot) #49252
[db4ce8a593] - doc: add release key for Ulises Gascon (Ulises Gascón) #49196
[e5f3a694cf] - doc: fix node-api call example (Chengzhong Wu) #49395
[021345a724] - doc: add news issue for Diagnostics WG (Michael Dawson) #49306
[f82347266b] - doc: clarify policy expectations (Rafael Gonzaga) #48947
[73cfd9c895] - doc: add print results for examples in StringDecoder (Jungku Lee) #49326
[63ab591416] - doc: update outdated reference to NIST SP 800-131A (Tobias Nießen) #49316
[935dfe2afd] - doc: use cjs as block code's type in MockTimers (Deokjin Kim) #49309
[7c0cd2fb87] - doc: update options.filter description for fs.cp (Shubham Pandey) #49289
[f72e79ea67] - doc: add riscv64 to list of architectures (Stewart X Addison) #49284
[d19c710064] - doc: avoid "not currently recommended" (Tobias Nießen) #49300
[ae656101c0] - doc: update module hooks docs (Geoffrey Booth) #49265
[fefbdb92f2] - doc: modify param description for end(),write() in StringDecoder (Jungku Lee) #49285
[59e66a1ebe] - doc: use NODE_API_SUPPORTED_VERSION_MAX in release doc (Cheng Zhao) #49268
[ac3b88449b] - doc: fix typo in stream.finished documentation (Antoine du Hamel) #49271
[7428ebf6c3] - doc: update description for percent_encode sets in WHATWG API (Jungku Lee) #49258
[bef900e56b] - doc: move and rename loaders section (Geoffrey Booth) #49261
[a22e0d9696] - doc: clarify use of Uint8Array for n-api (Fedor Indutny) #48742
[1704f24cb9] - doc: add signature for module.register (Geoffrey Booth) #49251
[5a363bb01b] - doc: caveat unavailability of import.meta.resolve in custom loaders (Jacob Smith) #49242
[8101f2b259] - doc: use same name in the doc as in the code (Hyunjin Kim) #49216
[edf278d60d] - doc: add notable-change label mention to PR template (Rafael Gonzaga) #49188
[3df2251a6a] - doc: add h1 summary to security release process (Rafael Gonzaga) #49112
[9fcd99a744] - doc: update to semver-minor releases by default (Rafael Gonzaga) #49175
[777931f499] - doc: fix wording in napi_async_init (Tobias Nießen) #49180
[f45c8e10c0] - doc,test: add known path resolution issue in permission model (Tobias Nießen) #49155
[a6cfea3f74] - esm: align sync and async load implementations (Antoine du Hamel) #49152
[9fac310b33] - fs: add the options param description in openAsBlob() (Yeseul Lee) #49308
[92772a8175] - fs: remove redundant code in readableWebStream() (Deokjin Kim) #49298
[88ba79b083] - fs: make sure to write entire buffer (Robert Nagy) #49211
[11c85ffa98] - (SEMVER-MINOR) lib: add api to detect whether source-maps are enabled (翠 / green) #46391
[c12711ebfe] - lib: implement WeakReference on top of JS WeakRef (Joyee Cheung) #49053
[9a0891f88d] - meta: bump step-security/harden-runner from 2.5.0 to 2.5.1 (dependabot[bot]) #49435
[ae67f41ef1] - meta: bump actions/checkout from 3.5.3 to 3.6.0 (dependabot[bot]) #49436
[71b4411fb2] - meta: bump actions/setup-node from 3.7.0 to 3.8.1 (dependabot[bot]) #49434
[83b7d3a395] - meta: remove modules team from CODEOWNERS (Benjamin Gruenbaum) #49412
[81ff68c45c] - meta: move one or more collaborators to emeritus (Node.js GitHub Bot) #49264
[ab975233cc] - meta: mention nodejs/tsc when changing GH templates (Rafael Gonzaga) #49189
[ceaa5494de] - meta: add test/reporters to codeowners (Chemi Atlow) #49186
[de0a51b7cf] - net: improve performance of isIPv4 and isIPv6 (Uzlopak) #49568
[8d0913bf95] - net: use asserts in JS Socket Stream to catch races in future (Tim Perry) #49400
[2486836a7d] - net: fix crash due to simultaneous close/shutdown on JS Stream Sockets (Tim Perry) #49400
[7a808340cd] - node-api: fix compiler warning in node_api.h (Michael Graeb) #49103
[30f26a99f4] - permission: ensure to resolve path when calling mkdtemp (RafaelGSS) nodejs-private/node-private#440
[5051c75a5b] - policy: fix path to URL conversion (Antoine du Hamel) #49133
[173aed4757] - report: fix recent coverity warning (Michael Dawson) #48954
[d7ff78b442] - sea: generate code cache with deserialized isolate (Joyee Cheung) #49226
[022f1b70c1] - src: support multiple --env-file declarations (Yagiz Nizipli) #49542
[154b1c2115] - src: don't overwrite environment from .env file (Phil Nash) #49424
[dc4de1c69b] - src: modify code for empty string (pluris) #49336
[701c46f967] - src: remove unused PromiseWrap-related code (Joyee Cheung) #49335
[4a094dc7af] - src: rename IsAnyByteSource to IsAnyBufferSource (Tobias Nießen) #49346
[55d6649175] - src: support snapshot deserialization in RAIIIsolate (Joyee Cheung) #49226
[dc092864ef] - src: remove unused function GetName() in node_perf (Jungku Lee) #49244
[f2552a410e] - src: use ARES_SUCCESS instead of 0 (Jungku Lee) #49048
[4a9ae31519] - src: add a condition if the argument of DomainToUnicode is empty (Jungku Lee) #49097
[f460362cdf] - src: remove C++ WeakReference implementation (Joyee Cheung) #49053
[2a35383b3e] - src: use per-realm GetBindingData() wherever applicable (Joyee Cheung) #49007
[184bbddcf5] - src: add per-realm GetBindingData() method (Joyee Cheung) #49007
[e9946885f9] - src: serialize both BaseObject slots (Joyee Cheung) #48996
[ec51e25ed7] - src,permission: add multiple allow-fs-* flags (Carlos Espa) #49047
[8aac95de4b] - stream: improve tee perf by reduce ReflectConstruct usages (Raz Luvaton) #49546
[0eea7fd8fb] - stream: use Buffer.from when constructor is a Buffer (Matthew Aitken) #49250
[b961d9bd52] - stream: add highWaterMark for the map operator (Raz Luvaton) #49249
[ca1384166d] - test: fix warning for comment in embedtest (Jungku Lee) #49416
[2a35782809] - test: simplify test-crypto-dh-group-setters (Tobias Nießen) #49404
[6740f3c209] - test: verify dynamic import call with absolute path strings (Chengzhong Wu) #49275
[6ed47bd8fb] - test: reduce length in crypto keygen tests (Joyee Cheung) #49221
[4faa30c553] - test: split JWK async elliptic curve keygen tests (Joyee Cheung) #49221
[e04a2603d8] - test: split test-crypto-keygen.js (Joyee Cheung) #49221
[0d23c1d4ce] - test: rename test-crypto-modp1-err

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 20.x releases. But if you manually upgrade to 20.x then Renovate will re-enable minor and patch updates automatically.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


Avoids printing missing features for the NER task

Fixes https://github.com/neulab/ExplainaBoard/issues/105 and also does a little bit of code deduplication, refactoring, and typo correction.
I'd like @pfliu-nlp 's review, but also flagging @lyuyangh to quickly make sure this won't break the downstream interface (this means that some features are not output for some datasets).

Thanks! @OscarWang114 might be more familiar with this part. Could you take a look at the code when you get a chance? I think this should work but I'm not 100% sure. I can test these changes with the web app tonight.

Sounds good! I reassigned it to @OscarWang114

@neubig @lyuyangh Thanks! The frontend uses the keys (the strings starting with attr_ in the image) under the results.fine_grained field in the SDK outputted analysis dictionary to determine the number of graphs that should be plotted. So the only requirement is to ensure the un-outputted features are not included in results.finegrained.

I'm not entirely familiar with how the SDK outputs the analysis dictionary and might need some help with this. I can test out the code too, but probably in tomorrow afternoon due to a morning midterm. I hope the information above is clear and sufficient for @pfliu-nlp to review. Let me know if there are other questions!

Yeah, it should be fine then! This PR basically avoids outputting the missing features so the frontend should just not print out the graphs based on this.

I tested this PR with the web app and it works for conll2003. But I don't think SDK should throw an error whenever it cannot find pre-computed features for a given dataset. The web app has no knowledge of whether the SDK has special features for a certain dataset so it sends the dataset name to SDK as long as the user chooses one. I think the SDK or DataLab SDK can maybe keep a list of dataset names that should have a pre-computed feature file. And it only throws an error if it cannot find the file for a dataset that's in the list? What do you think?

"But I don't think SDK should throw an error whenever it cannot find pre-computed features for a given dataset."

Yeah, I kinda agree.

"I think the SDK or DataLab SDK can maybe keep a list of dataset names that we support training set dependent features. And it only throws an error if it cannot find the file for a dataset that's in the list? What do you think?"

Good suggestion.  I think we probably can:

try .. except the error from sdk side
keep a list of datasets that support training set dependent features from sdk side
what frontend needs to care about is to prompt users whether the dataset they used could be supported by training set dependent features

merged this branch and added try except for FileNotFoundError.


Fix navigation to mw provider from topology

@miq-bot add_label bug, topology, providers/hawkular
this PR is dependent on #8877 and should be merged after it.

@miq-bot add_label wip

@Jiri-Kremser @ammendonca fyi

@miq-bot add_label test
@miq-bot rm_label wip

@miq-bot rm_label bug


chore(litmus-portal): Adding Dockerfile for subscriber client and adding dockerops to Makfile

Signed-off-by: Raj Das<EMAIL_ADDRESS>
What this PR does / why we need it:
Adding Dockerfile for subscriber client and adding dockerops to Makfile
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Checklist

[ ] Does this PR have a corresponding GitHub issue?
[ ] Have you included relevant README for the chaoslib/experiment with details?
[ ] Have you added debug messages where necessary?
[ ] Have you added task comments where necessary?
[ ] Have you tested the changes for possible failure conditions?
[ ] Have you provided the positive & negative test logs for the litmusbook execution?
[ ] Does the litmusbook ensure idempotency of cluster state?, i.e., is cluster restored to original state?
[ ] Have you used non-shell/command modules for Kubernetes tasks?
[ ] Have you (jinja) templatized custom scripts that is run by the litmusbook, if any?
[ ] Have you (jinja) templatized Kubernetes deployment manifests used by the litmusbook, if any?
[ ] Have you reused/created util functions instead of repeating tasks in the litmusbook?
[ ] Do the artifacts follow the appropriate directory structure?
[ ] Have you isolated storage (eg: OpenEBS) specific implementations, checks?
[ ] Have you isolated platform (eg: baremetal kubeadm/openshift/aws/gcloud) specific implementations, checks?
[ ] Are the ansible facts well defined? Is the scope explicitly set for playbook & included utils?
[ ] Have you ensured minimum/careful usage of shell utilities (awk, grep, sed, cut, xargs etc.,)?
[ ] Can the limtusbook be executed both from within & outside a container (configurable paths, no hardcode)?
[ ] Can you suggest the minimal resource requirements for the litmusbook execution?
[ ] Does the litmusbook job artifact carry comments/default options/range for the ENV tunables?
[ ] Has the litmusbooks been linted?

Special notes for your reviewer:

LGTM


[Codegen] Add canonicalization pattern for reshape into interface stores

This pattern is similar to the existing one for loads except for stores. This is needed for implicit gemm where a reshape ends up at the bottom of the kernel.

@MaheshRavishankar I am not able to land this by the way if that's what you were expecting (no rush to land).

@MaheshRavishankar This PR is ready to land from my perspective (commenting as suggested in #12494). If squash/rebase is needed I can do that first.


ISSUE-4: updated readme to reflect issues with finding the right libgdal

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Adrian Partl seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Move public test helper classes to test package and generate a test-jar.

Makes a bit more sense. Might loosen restrictions on the test classes checkstyle-wise.
@Rule
public Timeout timeout = new Timeout(5, TimeUnit.SECONDS);

requires more work as the service projects depends on these classes. The checkstyle should be adjusted instead.


Better error message when connecting to DB with special characters in the password

Hi all - I'm really enjoying this project so far, just wanted to bring a small bug to your attention!
Bug description
Seeing an issue when trying to connect to a PSQL db when using a password that has certain special characters.
Example:
datasource db {
  provider = "postgresql"
  url      = "postgres://postgres:%Q&UaU5e89vK^drgppl#q@some.url:5432/some_db"
}

doesn't work but:
datasource db {
  provider = "postgresql"
  url      = "postgres://postgres:password@some.url:5432/some_db"
}

does.
Note: I can connect with pgAdmin with the first.

How to reproduce

Create a db with this password: %Q&UaU5e89vK^drgppl#q
Run npx prisma migrate up --experimental
You'll receive this error:

Error: Can't parse migration engine response:
undefined

Expected behavior
Can pass any valid password for a PSQL db as a schema db url.

Prisma information

See above
Environment & setup

OS: Mac OS
Database: PostgreSQL
Prisma version: 2.0.0-beta.2
Node.js version: v13.3.0

Thanks for reporting this! I read up on this and tested the current implementation. Currently the database URL needs to be a spec-compliant URL, meaning the password should be percent-encoded. This is consistent with libpq. This should be at least documented better though, I opened an issue for this: https://github.com/prisma/specs/issues/464
If you replace the password with the url-encoded version (%25Q%26UaU5e89vK%5Edrgppl%23q in your example) it should work.

At this time I think this should be considered a product issue (do we want to diverge from other libraries and have our own definition of an URL string? If yes, what should it be?). See the specs issue linked in the previous comment for details.

Specs issue was resolved with a decision to stay standards compliant. But we want to find a way to surface this to users that might not know and give them a helpful error message that leads them to success (by url-encoding their credentials for example).

migrate up is not a thing any more, but we should test this with all commands and potentially add tests for the (now hopefully useful) error message.

prisma db pull throws this because I had a # in the URL. An error message for percentage encoding will really be helpful. I tried \ escaping, using different variable to quote, etc.
✖ Introspecting based on datasource defined in prisma/schema.prisma

Error: Error parsing connection string: invalid port number in database URL


Added checking conn state before sending resp.

This change is small, but it is very useful when you want to send_resp in before_send hook.
About my situation.
I want to check authorization just before resolve function, because my app uses users permissions to allow/deny access to fields. So I use
    Absinthe.Plug.put_options(conn, context: %{ current_user: resource })

in plug before Absinthe.Plug and then (in before_send) I want to check that authorization is checked (I can forget to add auth checker middleware before resolve func) and passed (is user authorized and have required permissions) and send 401 response with message if authorization failed. But if I try to do it, I get Plug.Conn.AlreadySentError in (absinthe_plug) lib/absinthe/plug.ex:471: Absinthe.Plug.encode/4 because absinthe_plug tries to send_resp second time.
Also I think that it can be useful in other situations.
Thanks

Hey, thanks for the PR!
Unfortunately I'm not entirely sure that I'm on board with the use case. If you're running the GraphQL document, you should return a GraphQL response which would be whatever Absinthe.Plug wants to return. If you aren't running the document you can just halt from an earlier plug.
From a technical perspective, this PR could definitely use a test case to illustrate the desired flow. I'm actually a bit skeptical that this PR fixes the issue that you think it does. before_send callbacks are gonna be run exactly when  Absinthe.Plug calls send_resp. This is to say, the conn.state passed into the Absinthe.Plug will always be unset because none of the before_send callbacks have run yet.

when you want to send_resp in before_send hook

I'm also skeptical that this is a good idea. When before_send callbacks run it's because some other plug has already called send_resp, and now the callback is trying to hijack that.

Thank you for your response.
I agree with you that returning graphql response is better idea, for example for situations when user have access to one fields and haven't to others, and he can get data for that one fields and errors with path for another. And successfully processed graphql request should return 200 even if it contains errors. This is more correct in terms of graphql but more difficult to implement both on backend and on frontend.
May be I really should find another solution. I played some with absinthe middleware callbacks, but couldn't get wanted behavior.
So I'll will try to implement it in more suitable way and reply to this PR if find another advantages of proposed solution.
About control flow: I found that before_send callbacks runs before send_resp.
Call stack looks like call/2 –> execute/1 –> run_request/4 –> run_query/4 –> apply_before_send/3 –> apply/3. And send_resp is called in call/2 method after calling execute so that also after before_send callback.

Ah, you're using the before_send option of Absinthe.Plug, not the Plug.Conn.register_before_send. Yes the flow is correct then. Nonetheless, I don't think it's a right use of that feature to try to override the response that Absinthe is going to send.


addr and resolve apis should wait until Addrs are non-pending

Problem
If address resolution takes some time, the addr and resolve endpoints will return an address in the pending state.
Solution
Wait until the address is non-pending before returning.
Reported by @Ashald

lgtm, but a question:
What if the name doesn't become pending for a very long time?  Does it make sense to accept a wait=N query param that specifies how long to wait for a pending message?  if it times out, we just return the pending response.  This allows the consumer to specify their tolerance explicitly.  I get that this can be implemented in timeouts, but doesn't seem onerous to be a part of the API, either.
TIOLI.

Checked - works like a charm!


Cant Build after a reboot of my computer

Hello Dude, First thank you for Javatar, I´m having a little bit of troubles trying to build, everything was working flawless but after a reboot of my computer javatar cant build, I think it can build but is not making an out for the bin folder.
I already check and yes it it building because I inject a compile error and actually javatar found it, well came up the error. So I believe what is happening is that is not making the file in the bin folder.

Javatar Report
System Informations

Javatar Version: 1.0.2
Sublime Version: 3083
Package Path: /Users/eduardosanzb/Library/Application Support/Sublime Text 3/Packages
Javatar Channel: stable
Sublime Channel: stable
Is Debug Mode: False
Platform: osx
As Packages: True
Package Control: True
Architecture: x64
Javatar's Parent Folder: Javatar
Is Project: True
Is File: True
Is Java: True

Action List

Startup
Reset all settings
Reset all snippets
Reset all default packages
Read settings
Load snippets
Check news
Ready
Javatar snippet Class.javatar loaded
Analyse snippet [file=Packages/Javatar/snippets/Class.javatar]
Javatar snippet Enumerator.javatar loaded
Analyse snippet [file=Packages/Javatar/snippets/Enumerator.javatar]
Javatar snippet Interface.javatar loaded
Analyse snippet [file=Packages/Javatar/snippets/Interface.javatar]
Load Java default packages
Javatar default package Proto.javatar-packages loaded
Analyse package [file=Packages/Javatar/Developers/Proto.javatar-packages]
Javatar default package JavaSE8.javatar-packages loaded
Analyse package [file=Packages/User/JavaSE8.javatar-packages]
Check packages update
Select item ['Builds...', 'Build system'] [from_sublime=True]
Select item ['Current Class', 'Build current class'] [from_sublime=False]
Build [build_type=class]
Build file
Building Finished with Warning [0.03s]
Select item ['Builds...', 'Build system'] [from_sublime=False]
Select item ['Run Main Class', 'Run class contains main method'] [from_sublime=False]
Select item ['Builds...', 'Build system'] [from_sublime=False]
Select item ['Project', 'Build all classes in project'] [from_sublime=False]
Build [build_type=project]
Build all
Building Finished with Warning [0.15s]
Select item ['Javatar Settings...', 'Adjust Javatar settings'] [from_sublime=False]
Select item ['Dependencies...', 'Manage default dependencies'] [from_sublime=False]
Select item ['Back', 'Back to previous menu'] [from_sublime=False]
Select item ['Set Default JDK', 'Set default JDK for builds and runs'] [from_sublime=False]
Project Settings [type=set_jdk]
Select item ['Javatar Settings...', 'Adjust Javatar settings'] [from_sublime=False]
Select item ['Set Default JDK', 'Set default JDK for builds and runs'] [from_sublime=False]
Project Settings [type=set_jdk]
Select item ['Packages Manager...', 'Javatar packages manager'] [from_sublime=False]
Select item ['Reload and Update packages', 'Reload all packages and update packages list'] [from_sublime=False]
Reload Packages
Reset all default packages
Load Java default packages
Javatar default package Proto.javatar-packages loaded
Analyse package [file=Packages/Javatar/Developers/Proto.javatar-packages]
Javatar default package JavaSE8.javatar-packages loaded
Analyse package [file=Packages/User/JavaSE8.javatar-packages]
Check packages update
Select item ['Operations...', 'Do a Java operation'] [from_sublime=False]
Select item ['Back', 'Back to previous menu'] [from_sublime=False]
Select item ['Builds...', 'Build system'] [from_sublime=False]
Select item ['Current Class', 'Build current class'] [from_sublime=False]
Build [build_type=class]
Build file
Building Finished [0.00s]
Exit menu [from_sublime=False]
Select item ['Builds...', 'Build system'] [from_sublime=True]
Select item ['Current Class', 'Build current class'] [from_sublime=False]
Build [build_type=class]
Build file
Building Finished [0.00s]
Select item ['Builds...', 'Build system'] [from_sublime=False]
Select item ['Run Main Class', 'Run class contains main method'] [from_sublime=False]
Create package [package=]
Create package [package=j]
Create package [package=ja]
Create package [package=jav]
Create package [package=java]
Create package [package=javat]
Create package [package=javata]
Create package [package=javatar]
Create package [package=javata]
Create package [package=javat]
Create package [package=java]
Create package [package=jav]
Create package [package=ja]
Create package [package=j]
Create package [package=]
Create package [package=]
Create package [package=]
Create package [package=]
Create package [package=]
Create package [package=]
Create package [package=]
Create package [package=]
Create package [package=]
Create package [package=]
Create package [package=]
Create package [package=]
Create package [package=]
Select item ['Builds...', 'Build system'] [from_sublime=False]
Select item ['Project', 'Build all classes in project'] [from_sublime=False]
Build [build_type=project]
Build all
Building Finished with Warning [0.11s]
Select item ['Builds...', 'Build system'] [from_sublime=False]
Select item ['Project', 'Build all classes in project'] [from_sublime=False]
Build [build_type=project]
Build all
Building Finished with Warning [0.12s]
Select item ['Packages Manager...', 'Javatar packages manager'] [from_sublime=False]
Select item ['Package Tools...', 'Tools for package creator'] [from_sublime=False]
Select item ['Back', 'Back to previous menu'] [from_sublime=False]
Select item ['Back', 'Back to previous menu'] [from_sublime=False]
Select item ['Javatar Settings...', 'Adjust Javatar settings'] [from_sublime=False]
Select item ['Set Default JDK', 'Set default JDK for builds and runs'] [from_sublime=False]
Project Settings [type=set_jdk]
Select item ['Builds...', 'Build system'] [from_sublime=False]
Select item ['Project', 'Build all classes in project'] [from_sublime=False]
Build [build_type=project]
Build all
Building Finished with Warning [0.12s]
Select item ['Help and Support...', 'Utilities for Help and Support on Javatar'] [from_sublime=False]
Select item ['Actions History', 'Generate a report on Javatar actions history'] [from_sublime=False]

P.D.
Also I believe is not reading the bin folder files.

Thanks to your screenshot. The problem is you did not set your source folder (you can see that the Package:  show the prefix src. which means your src folder is being use as default package).
What you have to do is set the source folder to your src folder again, this should solve the problem. This can be happen if you have configured the Javatar and did not save as a project since the settings will be lost after restart Sublime Text.
The problem can be permanently solved by saving your project as .sublime-project by using the Sublime Texts's menu under Project. This will store all the project-related settings to your project file and hence the settings will not be lost again.
Let me know if it's work :)

Thank you so much. U rock!


Improve handling the Best Segments comparison

The Best Segments comparison is often not suitable for deriving information as due to the shortest path calculation that we use for it, the difference between two segments may actually be meaningless. Instead we calculate information based on the stored best segment times for each individual segment and possibly add them up.

Superseded by #160


chimeric_sam.awk not work

Hello, I am using Juicer to analyze a HiC data without information on restriction enzyme. The mapping goes successfully. However, the chimeric_sam.awk does not work. Here's the error information.
(-:  Align of /home/jib79/hic/2019-NG/juicer/splits/SRR9822212.fastq.sam done successfully
awk: /home/jib79/hic/2019-NG/juicer/scripts/scripts/common/chimeric_sam.awk: line 50: illegal reference to local variable array
awk: /home/jib79/hic/2019-NG/juicer/scripts/scripts/common/chimeric_sam.awk: line 51: illegal reference to local variable array
awk: /home/jib79/hic/2019-NG/juicer/scripts/scripts/common/chimeric_sam.awk: line 164: syntax error at or near [
samtools: /home/jib79/miniconda2/envs/Hicpro/bin/../lib/libtinfow.so.6: no version information available (required by samtools)
samtools: /home/jib79/miniconda2/envs/Hicpro/bin/../lib/libncursesw.so.6: no version information available (required by samtools)
samtools: /home/jib79/miniconda2/envs/Hicpro/bin/../lib/libncursesw.so.6: no version information available (required by samtools)
samtools sort: failed to read header from "-"
***! Failure during chimera handling of /home/jib79/hic/2019-NG/juicer/splits/SRR9822212.fastq

apt install gawk


Delete events from meta

This should only be merged in once https://github.com/hackclub/events/pull/2 is merged.

Currently blocking on #617

*meant this is blocking on https://github.com/hackclub/events/pull/2

@MaxWofford no longer blocking, can you merge in?


Problema con la instalacion de RunTimeCompilation version 5.0.9 en Windows 10

Problem encountered on https://dotnet.microsoft.com/learn/aspnet/hello-world-tutorial/install
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

Can you provide more information about this issue? Any screenshots or error messages?


Get-Childitem misspelling

When performing:
Get-Help Get-Childitem -Full
The following result is returned for the -LiteralPath parameter in the help (using PS 5.1.18362.145)
"    -LiteralPath <String[]>
Specifies, as a string arrya, a path to one or more locations. Unlike the Path.......
"
Notice the word 'arrya' should be array.
Thank you.

Hello, @GitHubBJW
The online article for Get-Childitem is located in PowerShell-Docs repository.
The mentioned typo seems to be not present in the article. Please ensure that your documentation cache is up to date and consider providing a feedback to the relevant repository if the problem persists.
Thank you for providing feedback.


Add Awesome Ecommerce

Awesome Ecommerce
Ecommerce centric tools and software with a focus on options that are developer-friendly and API-First.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
(DONE) You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
(DONE) You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ add Swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The title of your entry should be title-cased and the URL to your list should end in #readme.

Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.

The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.
Must not feature Contributing or Footnotes sections.

Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.
It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
The section should not appear in the Table of Contents.

All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't use hard-wrapping.
Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

Unicorn

Walking through each point again, you can ignore this part:

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.

Sounds Good.

You have to review at least 2 other open pull requests.

#2397 & #2410
This pull request has a title in the format Add Name of List.
    ✅ Add Awesome Ecommerce

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.
    ✅ - All things ecommerce

Your entry should be added at the bottom of the appropriate category.

Added to bottom of business section
The title of your entry should be title-cased and the URL to your list should end in #readme.
    Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.
   [Ecommerce](https://github.com/jluterek/awesome-ecommerce#readme) - All things e-commerce.

The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list
Has been around for at least 30 days. *YES*
That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use https://github.com/sindresorhus/awesome/issues/2242 for incubation visibility. *Added during incubation, past 30 days*
Run [awesome-lint](https://github.com/sindresorhus/awesome-lint) on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please [report it](https://github.com/sindresorhus/awesome-lint/issues/new).

The default branch should be named [main, not master](https://www.zdnet.com/article/github-to-replace-master-with-alternative-term-to-avoid-slavery-references/).

Includes a succinct description of the project/theme at the top of the readme. [(Example)](https://github.com/willempienaar/awesome-quantified-self)
    ✅ Mobile operating system for Apple phones and tablets.
    ✅ Prototyping interactive UI designs.
    ❌ Resources and tools for iOS development.
    ❌ Awesome Framer packages and tools.
    *Updated to try and be more succinct*

It's the result of hard work and the best I could possibly produce. *30+ commits and counting*
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list. *awesome-ecommerce*
    ✅ awesome-swift
    ✅ awesome-web-typography
    ❌ awesome-Swift
    ❌ AwesomeWebTypography
The heading title of your list should be in [title case](https://capitalizemytitle.com/) format: # Awesome Name of List.

    ✅ # Awesome Swift
    ✅ # Awesome Web Typography
    ❌ # awesome-swift
    ❌ # AwesomeSwift
Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as [GitHub topics](https://help.github.com/articles/about-topics). I encourage you to add more relevant topics.

Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything. *This is subjective, I believe all items are awesome*
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible. *Ecommerce does not have a standard logo*
    Either centered, fullwidth, or placed at the top-right of the readme. [(Example)](https://github.com/sindresorhus/awesome-electron)
    The image should link to the project website or any relevant website.
    The image should be high-DPI. Set it to maximum half the width of the original image.
Entries have a description, unless the title is descriptive enough by itself. It rarely is though. *Yes*
Includes the [Awesome badge](https://github.com/sindresorhus/awesome/blob/main/awesome.md#awesome-badge).
    Should be placed on the right side of the readme heading.
        Can be placed centered if the list has a centered graphics header.
    Should link back to this list.

Has a Table of Contents section.
    Should be named Contents, not Table of Contents.
    Should be the first section in the list.
    Should only have one level of [nested lists](https://commonmark.org/help/tutorial/10-nestedLists.html), preferably none.
    Must not feature Contributing or Footnotes sections.

Has an appropriate license.
    We strongly recommend the [CC0 license](https://creativecommons.org/publicdomain/zero/1.0/), but any [Creative Commons license](https://creativecommons.org/choose/) will work.
        Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).
    A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and [Unlicense](https://unlicense.org/).
    Place a file named license or LICENSE in the repo root with the license text.
    Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
    To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/main/awesome.md#include-contribution-guidelines).
    The file should be named contributing.md. Casing is up to you.
    It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
    The section should not appear in the Table of Contents.

All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
Has consistent formatting and proper spelling/grammar.
    The link and description are separated by a dash.
    Example: - [AVA](…) - JavaScript test runner.
    The description starts with an uppercase character and ends with a period.
    Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
Doesn't use [hard-wrapping](https://stackoverflow.com/questions/319925/difference-between-hard-wrap-and-soft-wrap).
Doesn't include a Travis badge.
You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Hi @jluterek,
Your list has an MIT license which is not recommended. Is it possible for you to use another license, e.g. CC0-1.0?

Hi @jluterek, Your list has an MIT license which is not recommended. Is it possible for you to use another license, e.g. CC0-1.0?

Sure, updated with CCO-1.0

am have a problem developing my app in admod, so tell me what should I do
On Tue, Oct 25, 2022, 13:15 James Luterek @.***> wrote:

Hi @jluterek https://github.com/jluterek, Your list has an MIT license
which is not recommended. Is it possible for you to use another license,
e.g. CC0-1.0?
Sure, updated with CCO-1.0
—
Reply to this email directly, view it on GitHub
https://github.com/sindresorhus/awesome/pull/2417#issuecomment-1290442498,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A24UGW7EYCYSE325X6CLZOTWE7FMNANCNFSM6AAAAAARNBY5P4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

am have a problem developing my app in admod, so tell me what should I do
…
On Tue, Oct 25, 2022, 13:15 James Luterek @.> wrote: Hi @jluterek https://github.com/jluterek, Your list has an MIT license which is not recommended. Is it possible for you to use another license, e.g. CC0-1.0? Sure, updated with CCO-1.0 — Reply to this email directly, view it on GitHub <#2417 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A24UGW7EYCYSE325X6CLZOTWE7FMNANCNFSM6AAAAAARNBY5P4 .  This is a pull request for adding awesome ecommerce to the awesome lists.

unicorn

Can I get a second review please?

This pull request has a title in the format Add Name of List.


Sign up for CodePagesEncodingProvider

No data is available for encoding 850
Sign up for CodePagesEncodingProvider

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you @luo007 for your input. Bear in mind that at the beginning .NET Framework supported large number of encodings. Then the .NET evolved and the number of encodings included by default in .NET was limited. There is a reason that .NET Team decided not to include all possible encodings in default code base. I prefer to follow this approach. If an exotic encoding is needed then the developer should include it in their project, as described in the documentation.


Browserlist: caniuse-lite is outdated. Installation instructions are not clear.

While setting up PAWLS according to the instuctions in READMEthere are multiple errors and the documentation is not clear how to proceed with this software.
In the end when using docker-compose up the software builds but fails to start.
When attempting to visit the localhost:8080 the following error is shown:
pawls-ui-1      | Browserslist: caniuse-lite is outdated. Please run:
pawls-ui-1      | npx browserslist@latest --update-db
pawls-ui-1      |
pawls-ui-1      | Why you should do it regularly:
pawls-ui-1      | https://github.com/browserslist/browserslist#browsers-data-updating
pawls-api-1     | INFO:     <IP_ADDRESS>:44274 - "GET / HTTP/1.1" 204 No Content
pawls-ui-1      | Failed to compile.
pawls-ui-1      |
pawls-ui-1      | src/App.tsx
pawls-ui-1      |   Line 1:4:    Delete `␍`  prettier/prettier
pawls-ui-1      |   Line 2:69:   Delete `␍`  prettier/prettier
pawls-ui-1      |   Line 3:3:    Delete `␍`  prettier/prettier
pawls-ui-1      |   Line 4:82:   Delete `␍`  prettier/prettier
pawls-ui-1      |   Line 5:78:   Delete `␍`  prettier/prettier

The browserlist error is a warning. I don't think it's what's actually causing a problem.
The other errors shown there are emitted by prettier, a tool we use for formatting.  Based on the message, I think you might be trying to run things on windows.
You could try porting over this change, or removing the volumes stanzas from the docker-compose.yaml file:
-         volumes:
-             - ./ui/src:/usr/local/src/skiff/app/ui/src
-             - ./ui/public:/usr/local/src/skiff/app/ui/public
-             - ./ui/package.json:/usr/local/src/skiff/app/ui/package.json
-             - ./ui/tsconfig.json:/usr/local/src/skiff/app/ui/tsconfig.json
-             - ./ui/yarn.lock:/usr/local/src/skiff/app/ui/yarn.lock

I'd do that for both the api and ui services to see if it resolves the issue. My guess is there's something weird going on when mounting files from a Windows host into a Linux container. But I could be wrong.
Sorry for the trouble! Let me know if either of these things help!

Thank you for the response, I will try to apply the suggestions and verify if the software runs.


Building Myers Briggs Personality Test App with Python

Introduction
This article focuses on how to implement python data structure with a substantial flow with python functions that enable  I/O operations in a python data structure such as list and format specifiers which display a string of characters in a table.
According to  Isabel Briggs Myers, there are sixteen types of personalities identities and there are four key elements of categorizing people into the various sixteen personalities identities. The four key elements are:

Introversion (I) vs. Extraversion (E)
Sensing (S) vs. Intuition (N)
Thinking (T) vs. Feeling (F)
Judging (J) vs. Perceiving (P)
More information on personality typing is here (https://www.truity.com/page/16-personality-types-myers-briggs)
The test contains the four stages above and provides the personalities of the user base on the most common options in the user's test answers. In order words, the questions are structured to determine if the user is an introvert or extravert, sensing or intuition, thinking or feeling, judging or perceiving. In this test app,  we prompt users for questions related to each of the four stages above and categorizes people into the below personality types: INFP, INTJ, INFJ, INTP, ENFP, ENTJ, ENTP, ENFJ, ISFJ, ISFP, ISTJ, ISTP, ESFJ, ESFP, ESTJ, ESTP. For more information about personality identities kindly follow the link below: https://www.truity.com/page/16-personality-types-myers-briggs

The goals of this tutorial are to:

Makes convincing concepts clearer and understanding enough for beginners.
Shows the implementation of python list in a way that enables the reader how list can be used in I/O applications such as quiz app.
Makes a clean implementation of formatting strings in python in relation to data representation in a table.
Shows how to write python functions for the list, string, and floating-point manipulations.

Reference
-[Myers Briggs Personality Interpretation] (https://www.truity.com/page/16-personality-types-myers-briggs)
-[introduction to computer and python] (https://deitel.com/wp-content/uploads/2019/11/intro-to-python-for-computer-science-and-data-science-table-of-contents.pdf)

Good afternoon and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.


Publish to ghcr.io/cloudfoundry-incubator

Publish images to ghcr instead of dockerhub.
Consume ghcr secrets already on concourse.

Flown.

Triggered package-base, then all jobs to rebuild images and publish to ghcr.io.


🐛 (video): Shift of assets displayed and color changed

Can be detected by reading SDRAM or directly the screen and check that corresponding RGB is correct or not. Can be done at startup and sometimes at random time.


Issue with solution on bigger flow

Hi @ramonck , do you have any special character anywhere in the Flow (action names, variable names, ....) or as part of the filename?


ripgrep: install man-page

Modify the ripgrep package to install the tool's manual page.
I have tested this commit per nixpkgs manual section 11.1 ("Making
patches").
cc @tailhook

lgtm


Allow loading from model with empty weights.

For example, when the model graph contains only NDArray operators.
Description
(Brief description on what this PR is about)
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@JiadingGai for past release branches, we usually prefer cherry-picking a merged commit from master over directly making PRs so that all changes can be linked to a single PR which needs just one review and approval. Would you mind working towards merging #16061 and then request cherry-picking them on dev@?

Thanks @szha and @ChaiBapchya for pointing out the policy. Closing this request out and look forward to getting the master one pushed.


[Task]: Deprecate ActionBase.getUsedDatabaseConnections method

What needs to happen?
org.apache.hop.workflow.action.ActionBase.getUsedDatabaseConnections
Issue Priority
Priority: 3
Issue Component
Component: Actions

Another method to be deprecated  in 3.0
List org.apache.hop.base.AbstractMeta.getDatabases()


update the weexpack-create

I changed two questions altogether
The first is to cover the browser's default style on body.
The second is the addition of compilerModules to webpack.config.js
Thank you!

Issue on https://github.com/alibaba/weex-ui/issues/55


Feature: HTML Content Viewer Tab for Response Pane

Feature: HTML Content Viewer Tab for Response Pane
Description
Currently, the response pane does not support viewing HTML content in a formatted way. A dedicated tab for rendering and previewing HTML responses would improve the user experience, especially when handling API responses that return HTML or sometimes error statuscodes with descriptions.
Why It's Needed

Improved Usability: For API responses containing HTML, it can be difficult to read the raw response. A formatted HTML viewer helps users understand and debug HTML content more effectively.
Consistent Experience: Users who expect to view structured content (like JSON or headers) should have the same level of readability for HTML.

Solution Implemented

Added an HTML Preview Tab to the response pane, allowing users to view HTML responses in a formatted, rendered manner.
Utilized the flutter_html package to render HTML content in a new tab.
Added the tab next to "Response Body" and "Headers" for seamless navigation.

Screenshots
Below are screenshots showing the new HTML Preview tab:

Would love to hear any suggestions for improving this feature! Could I work on this issue if it aligns with the project’s direction?

Duplicate of #155
Please discuss on that thread.


Cannot resolve module 'invariant'

Cloning the repo, running npm i and npm start gives me the following error when I load the page.
I am running on a mac.
I have tried removing the node_modules folder and installing again, but it didn't help. Any clues?
ERROR in ./~/google-maps-react/dist/index.js
Module not found: Error: Cannot resolve module 'invariant' in /Users/sorenbs/Code/react-yelp-clone/node_modules/google-maps-react/dist
 @ ./~/google-maps-react/dist/index.js 3:4-184

ERROR in ./~/google-maps-react/dist/lib/GoogleApi.js
Module not found: Error: Cannot resolve module 'invariant' in /Users/sorenbs/Code/react-yelp-clone/node_modules/google-maps-react/dist/lib
 @ ./~/google-maps-react/dist/lib/GoogleApi.js 3:8-49

This is caused by fullstackreact/google-maps-react#3

In the mean time, install invariant from npm as a dependency and you should be good to go.

+1 to fix this

Fixed in google-maps-react#3.
Thanks for reporting!


Add webpack-dev-server troubleshooting tip

I suspect that this should probably go into its own section, but I'm not too sure, especially since the content is so thin.
I realize that this may seem like an unnecessary tip to experts, but I found it helpful - in my case, I had put a screwy output.filename in a quick project which had messed it up, so the logged output of webpack output is served from / wasn't quite right. Discovered this trick at http://stackoverflow.com/a/42592398/4200039
Hopefully a troubleshooting section can be expanded which in the long run will reduce the load of new issues opened.

Thanks for the tips. Updated.


SizeSSZ panic when struct has nil pointer

Cannot Marshal / SizeSSZ when a struct has a nil pointer.
For example, if BeaconBlock.Body is nil, this will panic.
// SizeSSZ returns the ssz encoded size in bytes for the BeaconBlock object
func (b *BeaconBlock) SizeSSZ() (size int) {
        size = 76

        // Field (3) 'Body'
        size += b.Body.SizeSSZ()

        return
}

Using commit f7a73f06375eb09bbd87a7266b567514b086963c

Branch safe-check-nil-structs has a fix for this.


Cannot read property 'entries' of undefined

Cannot read property 'entries' of undefined
at postmanToOpenApi (/node_modules/postman-to-openapi/lib/index.js:26:34)
Used the below collection
https://github.com/api-evangelist/swagger/blob/master/swagger-petstore-v2-postman-collection.json
I'm getting this error in some of the files I tested.  Thanks for making this tool.  :)
Hope this helps.

HI @d3ep4k,
This collection is in format "Collection v1" that is deprecated by postman and not supported by postman-to-openapi. You can import the collection into postman and save as a v2 or v2.1 (recommended) to make it works.
Best Regards,


docs: add EnableDefaultDeny documentation

This adds more complication to the logic for determining an endpoint's default policy mode, so pull that in to its own section. Then, add the docs for EnableDefaultDeny.
While we're at it, clean up obsolete configuration references; we don't support configuration by environment variable anymore.

/test


Add Igensia file

@Fyleek The first verification stage is complete: the official domain for  Campus Igensia Toulouse - Ecole en Informatique IPI is www.ipi-ecoles.com, to the best of my knowledge. This is just an informational note. The pull request is still under review. The review may take some more time. I greatly appreciate your patience. Here is the proof of domain ownership: https://www.ipi-ecoles.com/espace-entreprises/recruter-a-lipi/

The group to which the school belongs change their name from IGS to IGENSIA
In fact its more about the global domain for all the campus with multiple school (like IPI which is in IT)

I just asked the school, there is a sub before igensia.com. According to the documentation the igensia.txt file is therefore in the correct format

@Fyleek  Thank you for the clarifications. Pull request merged. Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Fix build error for ignored qualifiers warning/error on GCC8

Building rviz using GCC8 results in few errors, including std::filesystem-related one discussed in https://github.com/ros/pluginlib/pull/116.
This PR fixes another one - new GCC detects additional ignored qualifiers (const in this case) and -Werror makes it fail on them.

Thanks!


Mobile reading: header and side margin takes up too much space

From discord:

I currently have a few annoyances with the mobile website.  This wastes a lot of vertical real estate that I need while searching dictionaries. And the 2nd biggest annoyance is there is wide borders on the left and right sides which in turn waste a lot of horizontal real estate

makes a lot of sense, should have a more mobile-friendly option.

Here's an example screenshot

Launched in 3.3.0.


1.13 Marathon bump 1.8.222

High-level description
Bump Marathon to 1.8.222
This is mostly to include the change for MARATHON-8681
What features does this change enable? What bugs does this change fix?
Corresponding DC/OS tickets (required)

DCOS_OSS-5460 Bump Marathon to 1.8.222 on 1.13
MARATHON-7977: Clarify support for ranges and sets with constraint operators
DCOS-51846: Add seccomp integration tests
MARATHON-8627: Revive and suppress offers based on instance state
MARATHON-8685: Exit with 111 if Marathon could not bind to address
MARATHON-8660: Added maintenance mode to info endpoint
MARATHON-8681: Remove strict validation of external volume name

Related tickets (optional)
Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): compare on github
[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[x] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot Label Ready for Review

@mesosphere-mergebot sync


Clicking on TAB and SHIFT+TAB should also fire a blur event

When firing a keyboard TAB event (eg. press TAB button). Browsers behavior is, to throw a keyboard event and also, blur the current document.activeElement.
Currently, we are not doing that in ember-native-dom-helpers. It caused a bit of confusion to understand what's going on, so I think it might be worth to add it as a default behavior.
Thoughts?

This is tricky actually. If we want to replicate the browsers behaviour when using TAB, we should do it properly, which is not simple. I don't oppose tho, I just want to highlight what it would be required.
We'd need to have a special case for tab (and SHIFT + TAB) that gets the first focusable item after what what it's currently focused, or the first one if nothing is focused. This by itself has some tricky rules: all inputs, elements with contenteditable, buttons and links unless they have a negative tabindex. Also, if something has a positive tabindex, we need to obey it. Disabled inputs and elements don't count.
Also, this requires the concept of "what it's currently focused", so I think this feature would require the browser window to be focused for real.
I'm ok with the idea, but it is a hard one.

@cibernox yes, this was the thing that I was concerned about... making it right, is actually mimicking the whole browser tabbing behavior, which is definitely complex. If I am not mistaken, is we will use normal Event instead of KeyboardEvent, things should work. So the question is, maybe we can fake it until we make it somehow? :)

we will use normal Event instead of KeyboardEvent

Can you explain this? I think that a KeyboardEvent is closer to "reality"

@cibernox yes it does. I tried to say that - looks like, using just a simple Event solves the issues, and tabbing works, while using keyboard event it doesn't. So maybe there is a way, how we can have a 'fallback' to the simple Event. But I am not exactly sure how we can implement it, without breaking stuff a lot :)

Wait, you mean if that if you fire a generic Event instead of a KeyboardEvent the browser blurs the active element? Really? That makes no sense to me.

@cibernox before I'll say that, I'll verify it again :) I might've mistaken this behaviour yesterday with something else :)


make error message more specific when failing to create build system with LLBuild

motivation: clearer error message to help diagnose when LLBuild fails
changes: instead of throwing a generic error, throw a more detailed one

@swift-ci please smoke test


[Research] -- Find a way to deploy our backend, database and frontend

On the frontend we are using the Netlify application, but I am not very sure if it works ok. I am also not sure if we can use netlify for the backend, but if we can't we have to search where to host our backend and database.
@xTavi @AniketS312 @Explosion-Scratch @Chris-Mugumwa we should look into this in the future

Backend places:

Heroku: free node.js backends
Repl.it: Also free but pretty slow

Note: We'll need to use uptimerobot.com to ping the server every 5 minutes to keep heroku or repl from making it fall asleep

Good 👍🏻
Also I can create an Health Check API endpoint which will be used by the bot. I have never deployed a NestJs app to heroku, but I think it won't be so hard since it's Node at its core


Adjust 2D viewer Timer

What problem is this solving
When looking at the 2D viewer it would be nice if the timer could represend the real time of the game.
For now it is really complicated to calculate at what timestamp in the Round player reaches a certain point.
Example Basic Infos:
Competitive RoundTime: 1:55min
Round time in total: 2:20min Incl warmup
Warumup 15sec
Event 1 Round start after warmup:

Round start: Timer shows 2:05
Round Processbar shows 0:15
Real elapsed Round Time: 0:00
Real Round Timer ingame: 1:55

Event 2 Player X reaches certain interesting point:

Round start: Timer shows 1:32
Round Processbar shows 0:47
Real elapsed Round Time: 0:33
Real Round Timer ingame: 1:22

Event 3 Bombplant:

Round start: Timer shows 0:47
Round Processbar shows 1:32
Real elapsed Round Time: 1:18
Real Round Timer ingame: 0:37

We see here, that calculating the time which is interesting on a review (Real elapsed Round Time/Real Round Timer ingame) often can be confusing to determine.
To be able to get this info faster and more comfortable I would suggest adding another timer on top of the 2D viewer next to the existing timer.
Proposed solution
As the GameMode (Comp, Causal etc) is known, I would suggest, that an additional timer is added to the UI next to the existing Timer.
Im not sure if the data of a demo can provide the roundtime (For competitive eg 1:55), but if so, this timer as an additonal Timer in the UI could help teams to improve their strats against other teams when reviewing Demos.
In case the Bomb gets planted, I would suggest to do it like ingame. Either set the new added timer to "0:00"/"-:--" or hide it completly
Imho: Adding the Real Round Timer (counting down from 1:55 in competitive) would be the prefered solution.
Describe alternatives you've considered
If the data of a demo does not provide the roundTimer, I would suggest, at the "Generate Positions"-UI, add an additional, optional (default 1:55 for competitive) Field to add the time of a round to the DB entry of the demo

I don't think there is an accurate way to detect mp_roundtime, the new version also shows the elapsed time since the end of the freezetime.


2.35.2 with Raspberry PI 4 4GB is not working at boot

librealsense
2.35.2 RELEASE

OS
Linux

Please provide a description of the problem

Dear support, librealsense 2.35.2 with Raspberry PI 4 4GB is not working at boot:
28/06 10:14:22,108 WARNING [3069497360] (messenger-libusb.cpp:66) bulk_transfer returned error, endpoint: 0x1, error: No data available, err. num: 61
28/06 10:14:22,108 ERROR [3069497360] (tm-boot.h:39) Error booting T265
If I unplug and replug USB works but only for a couple of minutes.
Cuou you help us?

I use 32-bit raspbern system,the same thing happened to me：WARNING [3069497360] (messenger-libusb.cpp:66) bulk_transfer returned error, endpoint: 0x1, error: No data available, err. num: 61.When I switch 64-bit system, the problem is solved.You can try

@DreamLFairy
Can you specify the 64-bit system, you have used to get the problem is solved?
I am willing to believe it work but I have to prove it myself ;-)

@DreamLFairy @patrickpoirier51 and @robertocalvi
I am having similar issues, have you gained any further experience with 64bit raspian system and the camera, is it working stable now?


Build failed with ensurepip

I got error when build
aries-vcr-issuer-controller/docker$ ./manage build

=> CACHED [myorg-pipeline 11/15] WORKDIR /data-pipeline                                                                                0.0s
=> ERROR [myorg-pipeline 12/15] RUN make install-packages                                                                                0.8s

[myorg-pipeline 12/15] RUN make install-packages:
0.812 The virtual environment was not created successfully because ensurepip is not
0.812 available.  On Debian/Ubuntu systems, you need to install the python3-venv
0.812 package using the following command.
0.812
0.812     apt-get install python3-venv
0.812
0.812 You may need to use sudo with that command.  After installing the python3-venv
0.812 package, recreate your virtual environment.
0.812
0.812 Failing command: ['/data-pipeline/.venv/bin/python3.8', '-Im', 'ensurepip', '--upgrade', '--default-pip']
0.812
0.816 make[1]: *** [.venv/bin/python] Error 1
0.816 .scripts/mara-app/install.mk:35: recipe for target '.venv/bin/python' failed
0.816 .scripts/mara-app/install.mk:15: recipe for target 'install-packages' failed
0.816 make: *** [install-packages] Error 2

failed to solve: process "/bin/sh -c make install-packages" did not complete successfully: exit code: 2

i am having the same issue


HHVM Event

Add @rosmanov's HHVM Event extension to Travis HHVM tests.

I still think that this feature makes perfect sense :+1: However, there are currently no immediate plans to build this from our end (no demand at the moment and more important outstanding issues currently), but I suppose we would be really happy to accept PRs :+1:
I'm closing this for now as it hasn't received any input in a while and we have no plans to change this ourselves anytime soon. Please come back if you feel this is still an issue and we can reopen this :+1:


Allow typing text into a cell

Right now I can't write words into a cell.

Closing as duplicate of #12

I seemed to misunderstand; #12 means texts in formulas, but this seems to mean plain texts in a cell


Flag bool in less/greater than comparison as error

Fixes #15506.
This PR flags boolean operands in comparisons with <, >, <= and >= as errors, for example:
var a = true;
var b = 123;
var c = a > b;
        ~~~~~
> error TS2365: Operator '<' cannot be applied to types 'bool' and 'number'.

Some baselines have changed that I didn't expect to, but mhegazy confirmed that they're due to graceful parsing (see issue).
Hope I didn't miss too much. Feedback is very welcome 😃

@FabianLauer,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

I think the expected behaviour is to allow only number, string and any to be compared as per https://github.com/Microsoft/TypeScript/issues/15506#issuecomment-299946258.

As gcnew noted, number, string, and any should be allowed.

Closing for now. please reopen with the suggested changes.


avoid depreciation issues in php8.1

Description:
wrapped $this->timeToNext() with intval() to avoid implicit conversion from float to int since this is depricated in php8.1.

Thanks for the PR, but this is incorrect for two reasons:

The timeToNext already is guaranteed to return an int.
intval should not be used. It's the same as an int cast, but much slower.

Thanks for the PR, but this is incorrect for two reasons:

The timeToNext already is guaranteed to return an int.
intval should not be used. It's the same as an int cast, but much slower.

@GrahamCampbell thanks for the performance hint - until now i didn't know that there's such a big performance difference ... but it is! 👍

Then why don't we prevent installing Guzzle 6 from php 8.1?
We should put a php 8.1 limitation in composer.json file.

Because it's too late. If we do that, composer just installs the version of Guzzle that did not have that upper-bound. We'd have to have added it back in 2015, before I was a maintainer.

My position is somewhere in the middle (the other school of thought is always bound to major.minor, so not even allow PHP 8.2 on guzzle 7 yet, since php does not follow semver), and as such Guzzle 7 has upper bounds on the PHP major version, but not minor version.


Provide better error message when assigning to tuple element

Description
This change addresses the second part of #1560 by adding an explicit error message when assigning to a tuple element:
./src/bpftrace -e 'i:s:1 { $x = (1, 2); $x.1 = 1; }'
stdin:1:22-30: ERROR: Tuples are immutable. Consider creating a new tuple and assigning it instead.
i:s:1 { $x = (1, 2); $x.1 = 1; }
                     ~~~~~~~~

I went with the approach of making this a parse-time error for simplicity. I ran all the unit tests and verified that the number of shift-reduce conflicts haven't changed after implementing this.
An alternative approach is to allow tuple assignment to parse successfully, and then make tuple assignment error later during semantic analysis. This would be a little more complex, but would also provide a better error message (since it can disambiguate between assigning to tuples vs. assigning to maps). Let me know if this approach is preferable.
Checklist

[x] Language changes are updated in docs/reference_guide.md
[x] User-visible and non-trivial changes updated in CHANGELOG.md
[x] The new behaviour is covered by tests

Oh, also update the changelog, please.

@danobi Thank you for reviewing this...I added a few more tests and updated the changelog.

Thanks for the PR!


SQS ReceiveMessageAsync() hangs in .Net Core when the provided identity doesn't have access

Expected Behavior
An exception should be thrown.
Current Behavior
In a Worker Service (using HostBuilder), executing await _sqs.ReceiveMessageAsync(...) using credentials that does not have access to the given queue will cause the operation to hang.  It seems indefinite, as it will keep going for several minutes without nothing happening.
Screenshot
Same results in .Net Core 3.1 and 3.0.
In a Console Application, however, an error message is thrown as expected. This is also true for .Net Framework 4.7. Exception screenshot.
Possible Solution
Unknown.
Steps to Reproduce (for bugs)
Repro at https://github.com/hognevevle/SqsWorkerServicePlayground . Make sure you change to a valid Queue URL in Worker.cs, and if needed, change to a different region in Program.cs.
Your Environment

AWSSDK.Core version used: <IP_ADDRESS>
Service assembly and version used: Not sure what Service assembly means
Operating System and version: Windows 10 Pro
Visual Studio version:  2019 (16.4.0)
Targeted .NET platform: .Net Core

.NET Core Info

.NET Core version used for development: 3.1
.NET Core version installed in the environment where application runs:  3.1
Output of dotnet --info:

.NET Core SDK (reflecting any global.json):
 Version:   3.1.100
 Commit:    cd82f021f4

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.18362
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.1.100\

Host (useful for support):
  Version: 3.1.0
  Commit:  65f04fb6db

.NET Core SDKs installed:
  3.0.101 [C:\Program Files\dotnet\sdk]
  3.1.100 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.14 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.14 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.14 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download```

* Contents of project.json/project.csproj: See github repo above

Hi @hognevevle, I think this is due to an unhandled exception.  When I reproduced the issue, it hung for me too unless I surrounded the call in a try catch and handled the exception.  Please try doing that.  You should still be getting the access denied exception.

Thanks @klaytaybai - indeed, a try/catch does the trick. Regardless, I do find this behaviour rather strange, but it seems to be an issue in the .Net Core Generic Host, rather than the AWS SDK.
I've opened an issue there. https://github.com/aspnet/Extensions/issues/2758


Parse tree forwarding input

Hello,
I have been using the parse tree code, and I was wondering if its parse function[1,2] should be using a forwarding reference for the Input parameter, as does the general PEGTL parse function[3]. It looks like the Input&& in forwarding reference in parse gets sent to various Rule's match functions, which appear to all take non-const lvalue references Input& in, so I suppose after that point there need not be any more forwarding. Is this correct?
Thanks,
Matthew
[1] https://github.com/taocpp/PEGTL/blob/7e39261e46408a32b2eb8aed260ba67ce2b07494/include/tao/pegtl/contrib/parse_tree.hpp#L297
[2] https://github.com/taocpp/PEGTL/blob/7e39261e46408a32b2eb8aed260ba67ce2b07494/include/tao/pegtl/contrib/parse_tree.hpp#L308
[3] https://github.com/taocpp/PEGTL/blob/7e39261e46408a32b2eb8aed260ba67ce2b07494/include/tao/pegtl/parse.hpp#L25

Good catch. The reason for having Input&& in is that the function should accept temporaries, if you replace it with Input& in in the normal parse functions you'll see several examples of how it fails. It was an oversight that the parse-tree parse function does not take the parameter as Input&&, I'll fix it in a minute...


Added lazyness to contrib.gis imports

Seems like a nice tidy!

I've worked almost all day on it! Pushed in master.


RuntimeError: cuDNN error: CUDNN_STATUS_MAPPING_ERROR

Anyone has this error?

i find the reason. i use RTX3090, must run in env >CUDA11. How can I use pytorch1.9?

you can use pytirch1.9 by changing dvn2 to torch type DEFORMCONV2D

Have the same error when running test.sh.
I installed cuda 10.0.130 in Ubuntu 16.04 with pytorch 1.2.


[CA-964][DO NOT MERGE] Update billing validation to include uppercase letters and underscores

Tested by submitting the string dm-AbcD4_- which passes our validation and is URL safe, but does not pass googles. This should be considered part of our feature branch for the work to separate out google-project from billing-project and not merge until that code goes to production

This matches the regex here: https://github.com/broadinstitute/rawls/blob/develop/model/src/main/scala/org/broadinstitute/dsde/rawls/StringValidationUtils.scala#L10

Can we close this?

Can we close this?

@zarsky-broad We will still need this once our (very long lived) Rawls feature branch for one Google project per workspace merges

@zarsky-broad is this set on your end? Do you want to give it another review?

I'm good.