chore(deps): :arrow_up: update nx monorepo

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

@angular-devkit/build-angular
17.0.1 -> 17.0.3

@angular-devkit/core
17.0.1 -> 17.0.3

@angular-devkit/schematics
17.0.1 -> 17.0.3

@angular/cli
17.0.1 -> 17.0.3

@angular/core
^17.0.3 -> ^17.0.4

@angular/core
17.0.3 -> 17.0.4

@nx/angular (source)
17.1.2 -> 17.1.3

@nx/cypress (source)
17.1.2 -> 17.1.3

@nx/eslint (source)
17.1.2 -> 17.1.3

@nx/eslint-plugin (source)
17.1.2 -> 17.1.3

@nx/jest (source)
17.1.2 -> 17.1.3

@nx/js (source)
17.1.2 -> 17.1.3

@nx/storybook (source)
17.1.2 -> 17.1.3

@nx/web (source)
17.1.2 -> 17.1.3

@nx/webpack (source)
17.1.2 -> 17.1.3

@nx/workspace (source)
17.1.2 -> 17.1.3

@schematics/angular
17.0.1 -> 17.0.3

ng-packagr
17.0.1 -> 17.0.2

nx (source)
17.1.2 -> 17.1.3

Release Notes

angular/angular-cli (@angular-devkit/build-angular)
v17.0.3
Compare Source
@angular-devkit/build-angular

Commit
Type
Description

450dd29a1
fix
default to watching project root on Windows with application builder

8072b8574
fix
ensure service worker hashes index HTML file for application builder

d99870740
perf
only create one instance of postcss when needed

v17.0.2
Compare Source
@angular-devkit/build-angular

Commit
Type
Description

023645185
fix
always normalize AOT file reference tracker paths

3b99980bd
fix
emit root files when localize is enabled when using the esbuild based builders

ef3e3abb8
fix
ensure watch file paths from TypeScript are normalized

d11b36fe2
fix
normalize paths in ssr sourcemaps to posix when using vite

62d51383a
fix
only include vendor sourcemaps when using the dev-server when the option is enabled

d28ba8a73
fix
remove browser-esbuild usage warning

angular/angular (@angular/core)
v17.0.4
Compare Source
common

Commit
Type
Description

7f1c55755d
fix
remove load on image once it fails to load (#52990)

fafcb0d23f
fix
scan images once page is loaded (#52991)

compiler

Commit
Type
Description

98376f2c09
fix
changed after checked error in for loops (#52935)

291deac663
fix
generate i18n instructions for blocks (#52958)

49dca36880
fix
nested for loops incorrectly calculating computed variables (#52931)

f01b7183d2
fix
produce placeholder for blocks in i18n bundles (#52958)

compiler-cli

Commit
Type
Description

f671f86ac2
fix
add diagnostic for control flow that prevents content projection (#52726)

core

Commit
Type
Description

db1a8ebdb4
fix
cleanup loading promise when no dependencies are defined (#53031)

31a1575334
fix
handle local refs when getDeferBlocks is invoked in tests (#52973)

migrations

Commit
Type
Description

ac9cd6108f
fix
control flow migration fails for async pipe with unboxing of observable (#52756) (#52972)

13bf5b7007
fix
Fixes control flow migration if then else case (#53006)

492ad4698a
fix
fixes migrations of nested switches in control flow (#53010)

0fad36eff2
fix
tweaks to formatting in control flow migration (#53058)

nrwl/nx (@nx/angular)
v17.1.3
Compare Source
17.1.3
🚀 Features

angular: update component generator to use a single string styles or styleUrl property (#20146)

🩹 Fixes

angular: update jest-preset-angular fixing an issue with component single string styles and styleUrl props (#20205)
angular: fix misc issues with migration replacing the nguniversal usages (#20209)
angular: set the correct target version for package update (#20219)
angular: improve express server setup for static files in mf remote apps (#20218)
angular: use esm2022 for secondary entrypoints in ng-packagr-lite executor (#20130)
angular: display template error when cache is disabled in ng-packagr executors (#20277)
angular: generate component with as-provided format when generating a library (#20306)
angular: fix builder/executor resolution in ngcli-adapter (#20307)
core: pass workingDirectory to executed schematic, if found in schema (#19371)
js: filtering of local dependencies when running nx release version (#19995)
misc: fix project-name-and-root-utils type imports in schemas (#20305)
misc: @nx/web:file-server should not error on destructuring null (#20318)
module-federation: add tsconfig file for linting with TS webpack #20150 (#20210, #20150)
nextjs: read nextConfig path correctly when provided as an option. (#20241)
react: types should be in compilerOptions of tsconfig.spec.json (#20290)
testing: target defaults migration should not throw if workspace contains inferred projects (#20189)
vite: vitest versions alignment (#20215)

❤  Thank You

Colum Ferry @Coly010
Craigory Coppola @AgentEnder
Denis Frenademetz @skrtheboss
Katerina Skroumpelou @mandarini
Kræn Hansen @kraenhansen
Leosvel Pérez Espinosa @leosvelperez
Nicholas Cunningham @ndcunningham
Philipp Kirchniawy @pkirchniawy

ng-packagr/ng-packagr (ng-packagr)
v17.0.2
Compare Source

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2023-11-23T13_22_45_944Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2023-11-23T13_22_45_944Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_22_46_698Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @angular/cli --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_47_731Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_22_48_280Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_49_432Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_22_50_137Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @angular/core --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_51_008Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_22_51_558Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_53_145Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_22_53_836Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @angular/core --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_54_683Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_22_55_248Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_56_358Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_22_57_024Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/angular --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_57_859Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_22_58_377Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_58_885Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx run-many --target=lint --all --parallel --fix --skip-nx-cache
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_59_491Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_00_185Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/cypress --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_01_041Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_01_578Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_02_685Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_03_368Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/eslint --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_04_231Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_04_752Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_05_845Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_06_516Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/eslint-plugin --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_07_354Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_07_883Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_08_986Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_09_661Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/jest --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_10_494Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_11_021Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_11_525Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx run-many --target=lint --all --parallel --fix --skip-nx-cache
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_12_121Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_12_799Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/js --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_13_641Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_14_162Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_15_269Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_15_948Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/storybook --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_16_800Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_17_319Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_19_125Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/web --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_19_978Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_20_502Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_21_608Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_22_284Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/webpack --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_23_118Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_23_654Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_25_447Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/workspace --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_26_826Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_28_085Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-11-23T13_23_28_776Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate nx<EMAIL_ADDRESS><EMAIL_ADDRESS>npm WARN cli npm v10.2.4 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR!   @ang


[release/1.7] Prepare release notes for v1.7.21

Generated notes

Welcome to the v1.7.21 release of containerd!
The twenty-first patch release for containerd 1.7 contains various fixes
and updates.
Highlights

Regenerate introspection UUID if state is empty (#10510)
Set stderr to empty string when using terminal on Windows. (#10499)

Build and Release Toolchain

Move builds to Go 1.22 and add support for testing with 1.23 (#10596)

Container Runtime Interface (CRI)

Borrow latest wsstream from k8s v1.31.x to 1.7 (#10575)
Make StopPodSandbox idempotent (#10527)

Runtime

Fix packaged runc reporting incorrect version (#10559)
Ensure /run/containerd gets created with correct perms (#10534)

Deprecations

pkg/userns: deprecate and migrate to github.com/moby/sys/userns (#10564)
Update warnings for deprecated CRI config fields (#10512)

Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
Contributors

Davanum Srinivas
Samuel Karp
Sebastiaan van Stijn
Phil Estes
Maksym Pavlenko
Akhil Mohan
Chris Henzie
Kazuyoshi Kato
Sascha Grunert
Akihiro Suda
Derek McGowan
Erikson Tung
Iceber Gu
Mauri de Souza Meneguzzo
Mike Brown
Shengjing Zhu
TinaMor
rongfu.leng

Changes
44 commits

975f279ee Prepare release notes for v1.7.21
go.mod: keep minimum go version at go1.21 (#10633)

d63bd8464 go.mod: keep minimum go version at go1.21

Move builds to Go 1.22 and add support for testing with 1.23 (#10596)

c76028088 update golangci-lint to 1.60.1
3b263d082 add go1.23.0, drop go1.21.x

Fix TestNewBinaryIOCleanup on Go 1.23 and Linux 5.4 (#10590)

09ca004de Fix TestNewBinaryIOCleanup on Go 1.23 and Linux 5.4

Borrow latest wsstream from k8s v1.31.x to 1.7 (#10575)

9269d97b1 hide wsstream under internal/ to prevent external use
59815fa44 golangci-lint should only look for problems in new code
1c431dc6f Run go mod tidy
226f93d92 Add copyright headers
6f3252733 switch over references to the new package
0a85d476a Fix up some constant references
82bfa44d0 Copy over wsstream from k8s v1.31.0-rc.1 release

Ensure the CRIAPIV1Alpha2 warning's lastOccurrence is accurate (#10571)

52b79f337 Update CRIAPIV1Alpha2 warning lastOccurrence every call

pkg/userns: deprecate and migrate to github.com/moby/sys/userns (#10564)

dce0b5a6d migrate to github.com/moby/sys/userns
65f7d0740 pkg/userns: deprecate and migrate to github.com/moby/sys/user/userns
f21675c27 vendor: github.com/moby/sys/user v0.2.0

update to go1.21.13 / go1.22.6 (#10570)

228914a5e update to go1.21.13 / go1.22.6

Fix TestNewBinaryIOCleanup failing with gotip (#10554)

3ff82ba0f Fix TestNewBinaryIOCleanup failing with gotip

Fix packaged runc reporting incorrect version (#10559)

d51143f6f script/setup/install-runc: fix runc using incorrect version

update auths code comment (#10536)

7bb1455d8 update auths code comment

Ensure /run/containerd gets created with correct perms (#10534)

16c5fc768 Ensure /run/containerd is created with correct perms

Make StopContainer RPC idempotent (#10528)

6da4e40b2 Make StopContainer RPC idempotent

Make StopPodSandbox idempotent (#10527)

b3b6f1507 Make StopPodSandbox RPC idempotent

client: fix tasks with PID 0 cannot be forced to delete (#10523)

0db46f664 client: fix tasks with PID 0 cannot be forced to delete

Update warnings for deprecated CRI config fields (#10512)

9afb8dcdf deprecation: update warnings for CRI config fields

Regenerate introspection UUID if state is empty (#10510)

b140792e4 introspection: regenerate UUID if state is empty

Set stderr to empty string when using terminal on Windows. (#10499)

f9beac3db Set stderr to empty string when using terminal on Windows.

Dependency Changes

github.com/moby/sys/userns  v0.1.0 new

Previous release can be found at v1.7.20

I opened https://github.com/containerd/containerd/pull/10633 for the above 👍

Rebased to include go1.21 change

/ok-to-test

@samuelkarp Ack, re-ran with -g and updated notes in description

I've labeled a few more PRs to show up in the release notes and reworeded a bit.

@samuelkarp Regenerated notes and put in description


aggregator-service imagepullbackoff

Describe the bug
The aggregator-service does not seem to exist
europe-docker.pkg.dev/dynatrace-demoability/docker/easytrade/aggregator-service:d863a2e

To Reproduce
Steps to reproduce the behavior:

Deploy the YAMLs in kubernetes-manifests
. See error

Expected behavior
Image exists and is pulled correctly.
NAME                                         READY   STATUS             RESTARTS      AGE
accountservice-6b85584c45-ctdx9              1/1     Running            0             43m
aggregatorservice-7bcb8c988b-nmmfn           0/5     ImagePullBackOff   0             30m

  Warning  Failed     30m                  kubelet            Error: ImagePullBackOff
  Normal   Pulling    29m (x2 over 30m)    kubelet            Pulling image "europe-docker.pkg.dev/dynatrace-demoability/docker/easytrade/agv/dynatrace-demoability/docker/easytrade/aggregatorservice:d863a2e": rpc error: code = NotFound desc = failed to pull and unpack image "europe-docker.pkg.dev/dynatrace-demoability/docker/easytrade/aggregatorservice:d863a2e": failed to resolve reference "europe-docker.pkg.dev/dynatrace-demoability/docker/easytrade/aggregatorservice:d863a2e": europe-docker.pkg.dev/dynatrace-demoability/docker/easytrade/aggregatorservice:d863a2e: not found

image restored


ENH: Pin Python version in non-Python Azure pipelines

Pin Python version in non-Python Azure pipelines so that the required Python package versions used match those used in the Azure pipelines testing the Python wrapping.
PR Checklist

[X] No API changes were made (or the changes have been approved)
[X] No major design changes were made (or the changes have been approved)

Thanks @jhlegarreta @tbirdso !
We are getting a timeout in the ITK.macOS build?:
https://open.cdash.org/viewBuildError.php?buildid=8253109
  Error running test executable.

    Path: '/.../s-build/bin/ITKSmoothingGTestDriver'
    Result: Process terminated due to timeout
    Output:

Restarting:
\azp run ITK.macOS

/azp run ITK.macOS


Show total disk space saved by deleting files

It would be nice to see how much disk space is or would be saved by running a sweep. For example, you might keep fewer days (at the cost of more recompiling later) if you really need to save disk space.

Sounds like a good idea! Should not be that hard to add that as a default output, i.e both to dry-runs but also to the normal cleaning output.
Will try to have this out this weekend as part of 0.3.0 which I am currently working on :)


Connect the navigation bar to their respective layout.

Right now, only the transition of the navigation bar is working. Your work will be to assign each option in the navigation bar to their respective layout screen. The dependency of the navigation bar used in this project is https://github.com/ismaeldivita/chip-navigation-bar. You can go through this and know how this navigation bar is working.

I would like to work on this, please assign me.

Sorry, but it's already assigned to one member.


Vela CLI not installed and gzip issue

I've followed the documentation here https://kubevela.io/docs/install to install on a windows system with the latest docker desktop.
First when running "velad install" I got an error message "Fail to set up cluster: failed to setup k3d: failed to extract k3d images: exec: "gzip": executable file not found in %PATH%"
I've installed cygwin and added the bin folder to the user environment variables to get it working.
When checking with "velad status" I got this:

vela cli is not installed.
What is missing in the docu to install vela cli?
Versions:

This is because velad unzip the image tarball before loading it in docker, and can be resolve by loading the tarball directly into docker.
cc @chivalryq

About the Vela CLI, how do I install it manually?

A quick install can be:
curl -fsSl https://kubevela.net/script/install.sh | bash

You can refer to the detail doc here: https://kubevela.io/docs/platform-engineers/advanced-install#2-install-kubevela-cli

For Windows users, powershell -Command "iwr -useb https://kubevela.net/script/install.ps1 | iex". See the doc posted by @wonderflow

This is because velad ungzip the image tarball (which uses gzip) before loading it into docker, and can be resolved by loading the tarball directly into docker. We should not rely on gzip in Windows.

Yes, it can be unusual for Windows user have gzip in their cmd PATH. We should either try if it's possible to load tarball to docker or use gzip golang lib to decompress the image file.

We should either try if it's possible to load tarball to docker or use gzip golang lib to decompress the image file.

Yes, the docker daemon can read compressed data.
https://github.com/moby/moby/blob/9100e3c087216343e4149887d43f1e7ae272968a/daemon/images/image_import.go#L95

We finally remove the dependency for gzip in PATH! 🎉


Fixing Gradle warnings associated with publishPluginZipPublicationToXxx tasks

Signed-off-by: Andriy Redko<EMAIL_ADDRESS>Description
Fixing
> Task :publishPluginZipPublicationToMavenLocal
Execution optimizations have been disabled for task ':publishPluginZipPublicationToMavenLocal' to ensure correctness due to the following reasons:
  - Gradle detected a problem with the following location: '/home/opensearch-plugin-template-java/build/distributions/rename-unspecified.pom'. Reason: Task ':publishPluginZipPublicationToMavenLocal' uses this output of task ':generatePomFileForNebulaPublication' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

Issues Resolved
Related to https://github.com/opensearch-project/opensearch-plugin-template-java/pull/35
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff
[X] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@prudhvigodithi @lukas-vlcek please take a look guys

@dblock thanks! the backports are not possible at the moment, they are stacked on top https://github.com/opensearch-project/OpenSearch/pull/4360 which is still in main only, @lukas-vlcek fyi

Ok, we need to speed up back-ports of changes to zip publishing changes.

Hey @reta joining late thanks for the PR :)
yes we have to backport this, https://github.com/opensearch-project/OpenSearch/pull/4156 and https://github.com/opensearch-project/OpenSearch/pull/4360 to make sure all these changes are reflected in 2.x (for 2.4 release) I have created a campaign once backported we can update the groupID for each plugin.
@bbarani @lukas-vlcek


Better image load and save

Currently Shapelogic Scala is using javax.imageio for image load and save.
This created a dependency on Oracle JDK.
The load and save needs more work.
Contenders for a solid io library:

javax.imageio
commons-imaging
imglib2

Now there is a full image writer

Now it has been lightly tested.

This is working pretty well now with JavaFX loaders used in GUI


stc fails to find type alias circular references

Given this input
type A = A2;
type A2 = A;

stc will print

Log

ERROR (1) Failed to find type: A2#2
    at crates/stc_ts_file_analyzer/src/analyzer/scope/mod.rs:2261
    in Expander::expand_ref
    in Expander::expand_type
    in Expander::expand_type
    in Expander::expand_ref
    in Expander::expand_type
    in expand
    in normalize with ty: A;
    in normalize with ty: A;
    in Stmt with line_col: "(2017:1-2017:13)"

but for a non-circular reference stc will find the type just fine
type A = A2;
type A2 = number;

declare var x: A;
x = "" // error cant assign string to type number

My guess is that having a self-referencing type breaks how type aliases are hoisted (which I presume they are hoisted), but i haven't been able to confirm.

stc calculated evaluation order based on the dependency graph, but it can't handle cycles yet.


Provide ansible_distribution when building inventory

Hi,
We would need to know beforehand if a host if Windows, or Debain or CentOS, this way we can put them in appropriate groups.
For sure windows needs to be divided from the other hosts since other connection parameters are needed when using Ansible.
It would be great if more information of the server was specified.
Worst case just having the initial template name would be a great step forward ;)
Atm this is quite blocking to get 100% automation...

Hi there!
We should be able to make this grouping available soon. Currently it's not yet available in our API (only in control panel) and you'd need to set this by yourself with our server labels (and then filtering with those), but as it will be made available with other changes, we can start supporting grouping these. I don't yet know the time when this will be available, but we should be getting back to this right after it's available.


DBeaver 7.2.5 dosn't show all sections for table in PostgreSQL DB

Hello!
DBeaver 7.2.5 dosn't show all sections for table in PostgreSQL DB.
In my table there is 2 sections, but only one is shown. The first one.
In version 7.2.4 it's okey.

Hello @tvgis
Thank you for bug report!
The problem was fixed not so long ago in this ticket https://github.com/dbeaver/dbeaver/issues/10426
Fix will be available in release 7.3.0 at Monday (30.11)

If the problem is still actual after downloading the new version, then you are free to create a new ticket then.


Support for TravisCI added.

Build on travisci will happen in docker environment, in order to run integration tests.

Really cool stuff, thank you @swiec , this is going to be very handy going forward!


string vs hex

\x is a string escape code in python which cause some confusion for example in the reset function.
b = '\x40'
print(b)

'@'

because \x40 is the ascii code for '@'

Not sure what you mean here. Constants were intentionally written in the hexadecimal form. I don't think it's a good idea to use "@" instead of "\x40". Another possible approach is to use integers in the constants (i.e. RESET_BYTE = 0x40), but it will require additional conversions in the code and I don't think this change worth it

The problem is only about visualization in the log. To check if the frame is the good one. I mean that in the log it is writtent "message send : @" in place of "\x40" and it is confusing and really not convenient. I added a function to convert str in the real hex representation - and not the unicode caracter to print in the log.


feature request: toggle between site versions (releases)

I was wondering if this is do-able ? I wanna be able to toggle my site between versions, like how did the website look like in release 1.0.0 and 2.0.0 is that possible with minimal-mistakes

Not sure why you'd want to do this, but from my perspective it's probably next to impossible to impliment.
Each major version of the theme can be wildly different between the underlining HTML and CSS. 4.0 is a complete rebuild and almost none of it shares the same code from prior versions.
If it was just CSS changes you could probably rig up something that swaps what .css is loaded, but because the actual class names and structure of most _layouts and _includes change between versions that won't work.

oh I meant the content of my site, like let say I have a api documentation and each time I have a major change in api doc, I want users to go back in time and be able to see the docs exactly the way it was for previous version of the api.
would it be better if I just copy the current site files to a folder ?

so maybe my question could be changed to this,
can I toggle the site to reffer to a different folder based on a dropdown ? with a default of Latest Folder?

Probably. I don't have much experience with doing that. I think that's more of a Jekyll question than a theme question.
Might get some better help asking on the Jekyll Talk forum. You could look at the Bootstrap repo too for ideas. They use Jekyll to build their docs and I'm pretty sure they structure it in a way to archive each major version.

sweet thanks a lot.

I've been working on solving to add versions using Minimal Mistakes and wrote up my findings in this blog post: https://justwriteclick.com/2017/07/30/investigating-jekyll-for-versioned-content/
tl;dr - It was easiest to use a one-off _config.version.yml file for each version with a new baseurl: /n.n setting. I'm still working on the UI menu itself, but one super-simple idea would be to add the versions to the top menu in _data/navigation.yml and make each version's URL selectable there.

@annegentle thanks will check it out.


Validate IP source for whitelist in entrypoint

Do you want to request a feature or report a bug?
Bug
What did you do?
I have misconfigured my traefik instance including a wrong IP address in the Whitelist.SourceRange, this make the complete rule do not work at all (than expect only the current wrong IP is ignored).
Let's suppose we have 10 IPs that are allowed, if I misconfigure only one IP address, the whole whitelist rules is ignored and there are no rules that stop access to the endpoint instead of only 9 IPs are allowed.
What did you expect to see?
Connection from IP <IP_ADDRESS> are blocked
What did you see instead?
Connection from IP <IP_ADDRESS> are allowed
Output of traefik version: (What version of Traefik are you using?)
Version:      v1.7.2
Codename:     maroilles
Go version:   go1.11.1
Built:        2018-10-04_01:44:36PM
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml, provider, platform, ...)?
debug = false
logLevel = "ERROR"
checkNewVersion = false
defaultEntryPoints = ["http", "https"]

[entryPoints]
  [entryPoints.http]
    address = ":80"

    [entryPoints.http.redirect]
    entryPoint = "https"

  [entryPoints.https]
    address = ":443"
    [entryPoints.https.tls]

[docker]
domain = "sample.test"
exposedbydefault = false

than in docker-composer.yml file
version: '2'
services:
  whoami:
    labels:
      - "traefik.enable=true"
      - "traefik.port=8080"
      - "traefik.frontend.passHostHeader=true"
      - "traefik.frontend.whiteList.sourceRange=<IP_ADDRESS>/32,1.2.3/32"

Hello, happy to see you again.
In your case you have:
time="2018-10-14T12:27:58Z" level=error msg="error creating IP Whitelister: parsing CIDR whitelist [<IP_ADDRESS>/32 1.2.3/32]: parsing CIDR white list <nil>: invalid CIDR address: 1.2.3/32. Skipping frontend frontend-Host-whoami-docker-localhost-0..."

It means that the frontend is completely ignored, not only the whitelisting.
This is the expected behavior because the most secure.
If you do that:
# ...
  reverse_proxy:
    image: traefik:v1.7
    command: --api --docker --entryPoints='Name:http Address::80 WhiteList.SourceRange:<IP_ADDRESS>/32,1.2.3/32'

you have:
time="2018-10-14T12:35:46Z" level=fatal msg="Error creating whitelist middleware: parsing CIDR whitelist [<IP_ADDRESS>/32 1.2.3/32]: parsing CIDR white list <nil>: invalid CIDR address: 1.2.3/32"
quick_reverse_proxy_1 exited with code 1

This means that Traefik will not launch at all.
This is the expected behavior because the most secure.


Clicking on hidden ToC entry seems to change CSS

Before clicking the ToC entry:

After clicking the ToC entry:

Might only be due to the custom CSS: https://github.com/pawamoy/mkdocstrings/blob/master/docs/custom.css

Fixed in 0.13.6. Note that the recommended CSS rules were updated, see https://pawamoy.github.io/mkdocstrings/handlers/python/#recommended-style-material


Remove make build-all, refactor and fix make test

When running make build-all on macOS, the following is seen:
% make build-all

Makefile:86: warning: overriding commands for target `test'
Makefile.darwin:34: warning: ignoring old commands for target `test'
Building /Users/michaeldockter/senzing.git/init-database/target/darwin-amd64/init-database
Building /Users/michaeldockter/senzing.git/init-database/target/linux-amd64/init-database
# github.com/senzing/go-sdk-abstract-factory/factory
../../go/pkg/mod/github.com/senzing/go-sdk-abstract-factory@v0.3.2/factory/factory.go:109:46: undefined: g2configbase.G2config
../../go/pkg/mod/github.com/senzing/go-sdk-abstract-factory@v0.3.2/factory/factory.go:144:52: undefined: g2configmgrbase.G2configmgr
../../go/pkg/mod/github.com/senzing/go-sdk-abstract-factory@v0.3.2/factory/factory.go:179:54: undefined: g2diagnosticbase.G2diagnostic
../../go/pkg/mod/github.com/senzing/go-sdk-abstract-factory@v0.3.2/factory/factory.go:214:46: undefined: g2enginebase.G2engine
../../go/pkg/mod/github.com/senzing/go-sdk-abstract-factory@v0.3.2/factory/factory.go:249:48: undefined: g2productbase.G2product
make: *** [linux/amd64] Error 1

Since go-sdk-abstract-factory isn't able to cross-compile, neither is init-database.
Also in make test this issue:
% make test
Makefile:86: warning: overriding commands for target `test'
Makefile.darwin:34: warning: ignoring old commands for target `test'
dyld[11299]: Library not loaded<EMAIL_ADDRESS>  Referenced from: '/private/var/folders/rd/zwh2c8ns7sl8k2b07rv56d100000gn/T/go-build4256273226/b001/init-database.test'
  Reason: tried: '/usr/local/lib/libG2.so' (no such file), '/usr/lib/libG2.so' (no such file)
FAIL	github.com/senzing/init-database	0.363s
dyld[11313]: Library not loaded<EMAIL_ADDRESS>  Referenced from: '/private/var/folders/rd/zwh2c8ns7sl8k2b07rv56d100000gn/T/go-build4256273226/b373/cmd.test'
  Reason: tried: '/usr/local/lib/libG2.so' (no such file), '/usr/lib/libG2.so' (no such file)
FAIL	github.com/senzing/init-database/cmd	0.246s
dyld[11327]: Library not loaded<EMAIL_ADDRESS>  Referenced from: '/private/var/folders/rd/zwh2c8ns7sl8k2b07rv56d100000gn/T/go-build4256273226/b376/initializer.test'
  Reason: tried: '/usr/local/lib/libG2.so' (no such file), '/usr/lib/libG2.so' (no such file)
FAIL	github.com/senzing/init-database/initializer	0.234s
dyld[11341]: Library not loaded<EMAIL_ADDRESS>  Referenced from: '/private/var/folders/rd/zwh2c8ns7sl8k2b07rv56d100000gn/T/go-build4256273226/b379/senzingconfig.test'
  Reason: tried: '/usr/local/lib/libG2.so' (no such file), '/usr/lib/libG2.so' (no such file)
FAIL	github.com/senzing/init-database/senzingconfig	0.227s

Pull requests

https://github.com/Senzing/init-database/pull/139


How does Heartbeat work on iOS?

When I was testing App Launching, I noticed that if the Heartbeat Timeout is set to anything but 0, the iOS applications disconnect after the configured number of seconds before reconnecting.
Does the developer have some responsibilities to implement or enable heartbeat?

@smartdevicelink/ios We are still looking for an answer here

@hugh22 @adein Could we please get an answer here?

@hugh22 @adein Bump

I have no idea.  I'll see if Stefan or someone can give me some info.

@khburdette
Adding Kevin.  He did much of the architecture behind Heartbeat.

The heartbeat is a protocol V3 feature and is sent on the control service (0x00) as protocol messages.
Heartbeat should start immediately after first StartService.
Every session is responsible for it’s own heartbeat.
Both the mobile proxy and core need to have the capability to send a heartbeat and respond to a heartbeat.
Each side is responsible for letting the other side know it’s there. Sending data and/or RPC’s satisfies this requirement.
If no data or RPC’s are being exchanged from either side, it is the responsibility of the mobile to send the heartbeat.

Use case: Media app finishes all the command and control it needs and begins streaming via A2DP

App could play an entire song before sending another RPC
Mobile should send a heartbeat every X seconds to keep it’s connection alive

Use case: Navigation app is streaming H.264

If core relies on another component for it’s service data ACK (eg. a gstreamer callback), it could wait longer on this component than the heartbeat allows for
Because the mobile is sending the H.264, it is satisfying it’s requirement to let core know it’s still there
Core should send a heartbeat every X seconds to keep it’s connection alive

Use case: mobile is sending something to core that doesn’t require a response (doesn’t currently exist)

Because the mobile is sending this, it is satisfying it’s requirement to let core know it’s still there
Core should send a heartbeat every X seconds to keep it’s connection alive

Both the mobile proxy and core should keep track of the heartbeat in both directions:

If the mobile proxy hasn’t sent a message to core in X seconds it should send a heartbeat and if core hasn’t sent a message to the mobile proxy in X seconds it should send a heartbeat.
If the mobile proxy doesn’t see a message from core in N seconds it should close the connection and if core hasn’t seen a message from the mobile proxy in N seconds it should close the connection.

Any and all activity will reset the heartbeat timer.

@khburdette For iOS specifically, is the app developer responsible for sending and responding to heartbeats?
I see sendHeartbeat in the SDLProtocol class but it doesn't have any callers. Besides that I noticed
    if (self.version >= 3) {
        // start hearbeat
    }

In the -[handleProtocolSessionStarted:sessionID:version] method, so it seems like it's an incomplete implementation?

@khburdette @hugh22 @Heath-FoMoCo We're still waiting for an answer here

@khburdette @adein
We have a proxy that is negotiating Version 4 right now, and if there are head units that say version 3 to start sending heartbeats which disconnect after the timeout we're going to have a problem. We need to figure out the priority on this issue and select and milestone and assign someone asap.


Component: Buttons

Ad missing Styles
Ad Font Styles from Foundations
Finalize documentation

Hi @rouvenpost to finalize the component, we need to add the label to the foundations with a strike-through for the disabled buttons. Then I think we will also need to talk about motion and also document, what the rules are.

To discuss:

[ ] Focus background color on negative buttons


quick character selection in teammate selection UI

Currently need to add each character to the team one by one. Could implement a "quick select" like in game.
Will likely need to add a separate "quick select" button?
need to add a new character select that allows selecting multiple characters, and in order

I'll start poking away at this


build(deps-dev): update to git-revision-webpack-plugin 5.0.0

change code accordingly as described in https://github.com/pirelenito/git-revision-webpack-plugin/issues/66#issuecomment-832473036
fix secvisogram/secvisogram#10
supersedes #44, #46

resolves #44


Add an additional option to work around AKS limitation

On a large Enterprise I found a way to achieve this for hub and spoke networking, the secret is to deploy AKS with no DNS Zone and then create a seperate Zone where you can add the aks subnet to the linked network and add the corresponding A records

Learn Build status updates of commit f96b084:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/aks/private-clusters.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Looping in @phealy to review this and verify this suggested approach is supported by the product group before proceeding. Thanks!

Learn Build status updates of commit 0c53143:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/aks/private-clusters.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 8c1cf3b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/aks/private-clusters.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit e239d28:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/aks/private-clusters.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Expose static methods for plugins to detect whether they're running on Forge or Vanilla

SpongeAPI | SpongeCommon | SpongeForge
See common PR for related issue.

Why?

Why?

Quoting from the related issue on the SpongeCommon PR:

it would be useful for plugins to have some static methods to detect the environment they're running in before the game has actually started.
They can be used to apply a certain mixin only to either SpongeForge or SpongeVanilla but not both (similar to what we do currently in SpongeVanilla/SpongeForge).

This was already implemented. I've moved it from SpongeImplHooks (see SpongeImplHooks) to expose it to plugins.

What should return Lanternpowered server?

I was thinking the same.
And other implementations.

What should return Lanternpowered server?

True.
Lantern is a minecraft server.
isVanilla being false just means this is a Forge Server.
The issue is [...] detect whether they're running on Forge or Vanilla [...], guess I should have linked it here.

I personally think that it would be useful for the mixin developers (I am not one myself) but I don't think that this is the way.
Personally I think there needs to be a single function that returns the implementation name even on PreInitialisation.

@mosemister You should take a look at Sponge#getPlatform, you will be able to get the implementation PluginContainer.
Also, I think the method needs some documentation to explain when it should return what.

@RedNesto
I already knew that, because im not a mixin guy I thought that wasnt available in the PreInitialisation state which is where I believe mixins are required to be initialized. If it is then I dont see the point for exposing this at all

Sponge.getPlatform().getContainer(Component.IMPLEMENTATION).getId() == "spongeforge" can be easily added to a plugin if really needed.
The thing is that vanilla/modded is a blurred line, if you add a plugin to a sponge server, is it still vanilla? And even with lantern isn't even "vanilla", because you will never be able to replicate the features exactly. Another example, is forge without mods vanilla? Or is a forge server without client mods vanilla? What about server side mods?
Basically "vanilla" is minecraft without amything else, the moment sponge/forge comes into play it's no longer "vanilla". Unless you only use optimizations (and they aren't game changing).

@ImMorpheus but lantern isn't vanilla server. Someone may use isVanilla for some NMS hacks.

The SpongeAPI isn't a place for NMS hacks, if you want that, depend on SpongeCommon instead. You can add the method there if you really need it. This breaks compatibility with any non NMS based impl.

I can see the ambiguity with the "vanilla" term.
Input wanted, whether this should be closed (with the related issue) or renamed to something else ("supportMods" or smth).

Ultimately, why should a plugin that purely relies on the Sponge API alone care about this? This is exposing an implementation detail - and checking whether the implementation is a Vanilla one when the Sponge system is agnostic to this.
Just because it exists in Common doesn’t mean it should exist in the API.
So, to go back to @kashike’s question - why is this useful? Why should a non-implementation dependent plugIn care about this? @Cybermaxke has already talked about the platform, surely that gives you everything you need to know already?

That's what I wanted to hear.
I'm closing this (and the related issue) as "invalid".
Just a sligthly unrelated nitpicking:

Just because it exists in Common doesn’t mean it should exist in the API.

I've opened this PR because there was a feature request in common.

I've opened this PR because there was a feature request in common.

I think something needs to be clarified here as to what that issue was asking for.
The problem is that the request was in SpongeCommon and should be solved in SC because it's an implementation detail. It was open to explore exposing whether the impl was Vanilla to those that use the MCP implementation (that is, ours). Plugin-provided mixins intentionally depend on the implementation, so this doesn't need to be in the API layer. As such, it was never intended to hit the API, I'm sure Minecrell would have opened it in this repo if it was.
This PR probably would not have solved that issue because all you're doing is moving a method - if it was that easy, the original issue would not have been created. It might be that the original issue is no longer valid, it probably needs checking in the context it is presented in.

This is needed as per the original ticket.
It's needed to be done in it's own class outside the rest of SpongeAPI so that mixins / transformers DO NOT load the rest of SpongeAPI / SpongeCommon too early.
It NEEDS to be in the API, otherwise it's impossible for other implementations to implement, and have plugins be potentially compatible with other platform internals / extended API.
isVanilla() isn't enough in my eyes, and it also needs to be somewhere where it won't chain class load everything else.

Again, I never said the original issue wasn’t needed. I said this is the wrong place for the solution.

mixins / transformers

These two words explain exactly why it does NOT go in the API. When you use mixins or transformers, you’re intentionally interacting with the implementation. In particular, this is wanted before the transformation takes place, particularly with Mixins - this makes a determination whether a mixin should be applied before any mixins are applied, meaning for the use case in the original issue, this would always say the impl was vanilla at the point it would most likely be checked.
(Aside: this PR would not have worked because of this fact, it relies on a transformation of an API method but the info would be needed before this happened)
Plugin provided mixins are designed as an MCP impl feature. There is no support for them in the Sponge API, the API and its dependency set makes no guarantee that you will be able to use them. I expect that Lantern doesn’t support mixins, why would it want to use them if it has control of the full stack?
The API is a runtime object that can already provide this information when needed at runtime, though a plugin generally does not need this information. The problem that needs to be solved is an implementation level, specifically our implementation. Any mixins or transformers need, as you rightly say, to know WAY more information than just if it’s vanilla, and the API will not be ready at the time this info is needed.
It doesn’t need to be in the API layer, we should not pollute the layer with implementation specific calls. By making a call rely on a Mixin, we are creating a dependency (even if the dependency doesn’t move to the API) on Mixin.
The solution to this needs to be in Common, for our impl. There is nothing stopping there being class or system outside the rest of SC but within the SC jar that does this, no need for the API to contain it.

I'll move my reply to the API issue, since it's been reopened, but originally I replied to this, since it was relating to it being implemented on the API side.