text:
Not processing @font-face fully

With input css of
@font-face {
    font-family: 'myfont';
    src: url('fonts/myfont.eot');
    src: url('fonts/myfont.eot?#iefix') format('embedded-opentype'),
         url('fonts/myfont.woff') format('woff'),
         url('fonts/myfont.ttf') format('truetype'),
         url('fonts/myfont.svg#myfont') format('svg');
    font-weight: normal;
    font-style: normal;
}

the output is (base64 shortened for brevity)
@font-face {
    font-family: 'myfont';
    src: url(data:application/vnd.ms-fontobject;base64,VE0AADRMA...EVzM=);
    src: url(data:application/vnd.ms-fontobject;base64,VE0AADRMA...EVzM=) format('embedded-opentype'),
         url('fonts/myfont.woff') format('woff'),
         url('fonts/myfont.ttf') format('truetype'),
         url('fonts/myfont.svg#myfont') format('svg');
    font-weight: normal;
    font-style: normal;
}

For some reason only the .eot files are being processed. My gulpfile.js is below:
var gulp = require('gulp'),
    base64 = require('gulp-base64'),
    concat = require('gulp-concat');

gulp.task('build', function () {
    return gulp.src('css/myapp.css')
        .pipe(base64({
            extensions: ['woff', 'ttf', 'eot', 'svg'],
        }))
        .pipe(concat('main.css'))
        .pipe(gulp.dest(''));
});

And finally, the full output (with full base64 code) is below. Note that my editor doesn't fully syntax highlight the base64 code, suggesting something may be wrong with the output?
@font-face {
    font-family: 'myfont';
    src: url(data:application/vnd.ms-fontobject;base64,[encoded data, 26396 characters]);
    src: url(data:application/vnd.ms-fontobject;base64,[encoded data, 26396 characters]) format('embedded-opentype'),
         url('fonts/myfont.woff') format('woff'),
         url('fonts/myfont.ttf') format('truetype'),
         url('fonts/myfont.svg#myfont') format('svg');
    font-weight: normal;
    font-style: normal;
}

You can exclude specific URLs by regular expression, as documented in the Readme.md.

authors: Harrisonbro dobesv


text:
ioa_stftCompute函数没有找到

老师您好，sound-source-localization-algorithm_DOA_estimation/ssl_tools/doa_mvdr.m 文件中第33行的ioa_stftCompute函数

我没有找到，请问我该如何解决？
可以使用spectrogram函数替换吗？

可以，也可以用doa_srp.m中的ssl_stft函数

感谢您的解答

你好，你最终怎么改的？

老师您好，sound-source-localization-algorithm_DOA_estimation/ssl_tools/doa_mvdr.m 文件中第33行的ioa_stftCompute函数  我没有找到，请问我该如何解决？ 可以使用spectrogram函数替换吗？

你最终如何解决的？

source: gharchive/issue

authors: Wenzhe-Liu letnnn longRookie

license_type: permissive

license_source: github-api


text:
Session persistence

implementado verificação de token para persistencia de login

Por mim ok!

source: gharchive/pull-request

authors: WesleyDiasSilva lodustitan

license: MIT


text:
Farokh

Before reporting a bug, please see our FAQ in FAQ.md!
Description

Failed Step

More Details

only work on AWS VPS

repo: WhatsApp/proxy


text:
Problems with functions without declarations

/mnt/c/Users/H A M/Metroid/mf# python3 ../decomp-permuter-agbcc/permuter.py nonmatchings/CoreXShell
Loading...
nonmatchings/CoreXShell/base.c (CoreXShell)
No perm macros found. Defaulting to randomization.
Will try 1 different base sources.

[CoreXShell] base score = 0
iteration 1, 0 errors, score = 410
[CoreXShell] internal permuter failure.
Traceback (most recent call last):
  File "/mnt/c/Users/H A M/Metroid/decomp-permuter-agbcc/src/permuter.py", line 269, in try_eval_candidate
    return self._eval_candidate(seed)
  File "/mnt/c/Users/H A M/Metroid/decomp-permuter-agbcc/src/permuter.py", line 197, in _eval_candidate
    self._cur_cand.randomize_ast()
  File "/mnt/c/Users/H A M/Metroid/decomp-permuter-agbcc/src/candidate.py", line 81, in randomize_ast
    self.randomizer.randomize(self.ast, self.fn_name)
  File "/mnt/c/Users/H A M/Metroid/decomp-permuter-agbcc/src/randomizer.py", line 2456, in randomize
    method(fn, ast, indices, region, self.random)
  File "/mnt/c/Users/H A M/Metroid/decomp-permuter-agbcc/src/randomizer.py", line 2346, in perm_inline
    if match_cut(cand2, cut_expr, cut_types, [], typemap):
  File "/mnt/c/Users/H A M/Metroid/decomp-permuter-agbcc/src/randomizer.py", line 2307, in match_cut
    return ast_util.equal_ast(node, cut_node, cmp)
  File "/mnt/c/Users/H A M/Metroid/decomp-permuter-agbcc/src/ast_util.py", line 205, in equal_ast
    return equal(a, b)
  File "/mnt/c/Users/H A M/Metroid/decomp-permuter-agbcc/src/ast_util.py", line 201, in equal
    if not equal(getattr(a, name), getattr(b, name)):
  File "/mnt/c/Users/H A M/Metroid/decomp-permuter-agbcc/src/ast_util.py", line 181, in equal
    res = cmp(a, b)
  File "/mnt/c/Users/H A M/Metroid/decomp-permuter-agbcc/src/randomizer.py", line 2301, in cmp
    tp = decayed_expr_type(expr, typemap)
  File "/mnt/c/Users/H A M/Metroid/decomp-permuter-agbcc/src/ast_types.py", line 196, in decayed_expr_type
    return pointer_decay(expr_type(expr, typemap), typemap)
  File "/mnt/c/Users/H A M/Metroid/decomp-permuter-agbcc/src/ast_types.py", line 179, in expr_type
    fptr_type = resolve_typedefs(rec(expr), typemap)
  File "/mnt/c/Users/H A M/Metroid/decomp-permuter-agbcc/src/ast_types.py", line 104, in rec
    return expr_type(sub_expr, typemap)
  File "/mnt/c/Users/H A M/Metroid/decomp-permuter-agbcc/src/ast_types.py", line 127, in expr_type
    return typemap.var_types[node.name]
KeyError: 'CountPrimarySprite'

To reproduce the failure, rerun with: --seed 7743607712773704045

CoreXShell.zip
And here's what I'm permuting

now i realmatched it without permuter
https://decomp.me/scratch/2ioU9

I don't know why I didn't get an email about this, but regardless this is the wrong venue. decomp-permuter-agbcc's scope is changing the import script to be easier for agbcc compared to upstream. Any changes to the permuter itself are outside of this repository's scope, and should be handled by upstream.

authors: H-A-M-G-E-R WhenGryphonsFly

repo: WhenGryphonsFly/decomp-permuter-agbcc


text:
Fix the compilations warnings.

A lot of warning appears when compiling the projects. Those are related to variables unused, CSS issues, and so on.

 Allow the user to contact us through a form

repo: Whichost/frontend


text:
Milestone 5: Application deploy

Please find here the link to my portfolio project:

Repo: https://github.com/WilfriedM01/WilfriedM01.github.io
URL: https://wilfriedm01.github.io/

Hi @WilfriedM01 ,
Good job so far!
There are some issues that you still need to work on to go to the next project but you are almost there!

Highlights
📌 Descriptive pull request✅
📌 Your deployment link works properly :+1:
📌 Professional README file ✅
Required Changes ♻
Check the comments under the review.

[ ] From the project requirement, you should include the link to the live demo of your project in your readme file under the live demo section but currently the link under the live demo section of your readme is not the live demo link. :blush:

Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

:green_circle:  Approved! :partying_face:
Hi @WilfriedM01 👋,

Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Highlights 🌟

✔ Deploy the website using GitHub pages.
✔ README is updated to include a link to the online version.

Optional suggestions 🤷♂
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you take them into account as they can make your code better.
Cheers and Happy coding!👏👏👏
Important Notes 📝

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

authors: Owusu-Desmond WilfriedM01 abdulhamiid


text:
[US] Login View & Logic

As an application user, I want to login to the platform to gain access to my corresponding data.

MoSCoW
Risk
Story Points

Must have
7
13

Acceptance Criteria

There is a login view for an application user to enter its credentials into
The login view is linked to the PostgREST api and calls the appropriate database functions
Logs in the user successfully
Handles alternative scenarios successfully

Wrong email/password combination
No email/password provided

The roles and schema access for that particular user are correctly applied upon login
User can log out
Login view & logout are accessible from the main UI

Risks

Manipulation of sensitive information
Access right management
Uncertainties

Pre-requisites

[x] Meet with the stakeholder to clarify the requirements
[x] Complete the requirements of this US
[x] Understand the User Management & Authentication proposal (see #89)

Tasks

[x] Design how a user is marked as logged in within the front end and how the VMD would handle it
[x] Design the UI for the Login view
[x] Implement the front-end login view and associated logic

Dependencies
#137 #138

UI Mockups

Initial signup view
Login view
Signup view
User logged in

Demo Video
https://github.com/WillTrem/UInnovate/assets/64431699/4d79e4ab-bfe6-4127-b340-f5c37caec9e8

Signing off!

authors: TheOrangeDuke WillTrem

repo: WillTrem/UInnovate


text:
[question]: Where is list content drawn from?

There doesn't appear to be any available documentation on where these domains are retrieved from. Are you consolidating other public lists? Are they harvested from private servers, like with ShadowWhisperer's lists?

Heya, firstly, thanks for the question!
It's actually a little different, depending on the list itself.
Most are running by themselves nowadays with a, to be perfectly honest, not very well written crawler, which I am sure I will improve soon™, but it does its job for now.
They have a pre based list of servers and look for active sub- and related domains.
TV is actually based on local reverse DNS resolvers that a few friends of mine are nice enough to tolerate in their home.
Suspicious and Tracking are both running via an algorithmic tracking detector that runs with the crawler on every request and determines uniquely identifying cookies, local storage (supercookies), and canvas fingerprinting. If it observes a single third-party host tracking on multiple separate sites, it will be added to the list. This is based on EFF's Badger-Sett.
I generally check up on everything from time to time, but it mostly works without "user" intervention.
Hope that could clear up some stuff for you, I really need to be more transparent and will be working on a new and improved version of it, to open source it, I want to let it automatically interact with this repo in general, but yeah, if there's anything else, always feel free to ask me ^-^

I'm suspecting the YouTube ads list is derived from GoodbyeAds as it contains the watchdog.goodbyeads entry, but the others do seem mostly original. If you'd like to make some of the projects that collect this content public I'd be happy to take a look and clean them up.

repo: WilliDieEnte/BetterBlocklist


text:
First release

To achieve that, we need:

[ ] CRUD methods (https://github.com/strongloop/loopback-datasource-juggler/blob/master/docs/datasource-connector.md)
[ ] Better tests
[ ] Better readme

@Wiredcraft/core-members @Wiredcraft/applicants Any help would be appreciated. Please send me pull requests if you are willing to help.

Hi @CCharlieLi I need this in a week. Do you think you can get it done?

Ok! I was looking at the source code these days, I'll try my best!

Thanks. And please:

Track your time
Let me know your schedule
Show your progress frequently (commit or comment or whatever)

Schedule

Tus
- Deploy Couchbase and this app, run test and get familiar with these code.
Wed & Thu
- Deploy CRUD methods.
Fri & Sat
- Deploy tests and fix bug.

I have already forked this repo and got this run at localhost, it takes me some time to learn about the Couchbase and loopback-connector, and I will commit when I have more progress.

Thanks. Closing.

authors: CCharlieLi makara

license: mit

license_source: bigquery


text:
Mock SAS 2.1 is not initiating server even after providing correct csv file name

Mock SAS 2.1 is not initiating server even after providing correct csv file name.
As current Mock SAS is checking json files defined in csv file. And Mock SAS is checking json file from wrong folder, which is leading to again asking for csv file as input.
Snapshot is attached for latest Mock SAS for your reference.
Mock_SAS_2.1_snapshot.zip

Needs verification in V3.

Yes, We will verify the same once V3 available on github.

@saudawar please verify

Verified with latest Mock SAS. Issue resolved.

authors: awaizkhan pawan25062 saudawar


text:
Remove Python 2 classifier

This change should have been included in Portalocker 2.0.0 release. If we removed it at that time, it might have prevented Python 2.x environments from incorrectly pulling in an incompatible Portalocker 2.x and causing failure. (The MSAL Extensions' build pipeline currently runs into such a problem, I'll find a workaround for it, but it would still be good to make the following change here.)

Coverage remained the same at 100.0% when pulling 5a23e40e5735054f832b6ae555839a766795985e on rayluo:patch-1 into 0f420c8e0b533471754c40b561a350df13bef50f on WoLpH:develop.

That is indeed silly, thanks for the patch!

I've released a new version by the way, so it shouldn't be an issue if you use 2.3.1 or above

Hi Rick, thanks for your quick response and releasing a new version. It turns out, my changes in this PR was only good enough. Sorry for my inexperience on this situation (quoted from here):

Although the list of classifiers is often used to declare what Python versions a project supports, this information is only used for searching & browsing projects on PyPI, not for installing projects. To actually restrict what Python versions a project can be installed on, use the python_requires argument.

Let me know if you want me to send out a new PR for that.

authors: WoLpH coveralls rayluo

repo: WoLpH/portalocker


text:
URL Safe

are you open to the idea of url safe alphabet change option?

Sure! Would you provide a merge request?

authors: WojciechMula victorstewart


text:
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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_46_698Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
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/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @angular/cli --from=@angular/cli@17.0.1 --to=@angular/cli@17.0.3
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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_48_280Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
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: ["nx@17.1.3"]

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_48_792Z-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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_50_137Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
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/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @angular/core --from=@angular/core@17.0.3 --to=@angular/core@17.0.4
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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_51_558Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
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: ["nx@17.1.3"]

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_52_203Z-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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_53_836Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
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/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @angular/core --from=@angular/core@17.0.3 --to=@angular/core@17.0.4
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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_55_248Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
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: ["nx@17.1.3"]

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_55_755Z-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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_57_024Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
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/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/angular --from=@nx/angular@17.1.2 --to=@nx/angular@17.1.3
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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_22_58_377Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
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: ["nx@17.1.3"]

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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_00_185Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
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/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/cypress --from=@nx/cypress@17.1.2 --to=@nx/cypress@17.1.3
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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_01_578Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
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: ["nx@17.1.3"]

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_02_081Z-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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_03_368Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
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/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/eslint --from=@nx/eslint@17.1.2 --to=@nx/eslint@17.1.3
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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_04_752Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
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: ["nx@17.1.3"]

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_05_258Z-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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_06_516Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
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/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/eslint-plugin --from=@nx/eslint-plugin@17.1.2 --to=@nx/eslint-plugin@17.1.3
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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_07_883Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
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: ["nx@17.1.3"]

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_08_390Z-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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_09_661Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
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/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/jest --from=@nx/jest@17.1.2 --to=@nx/jest@17.1.3
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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_11_021Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
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: ["nx@17.1.3"]

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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_12_799Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
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/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/js --from=@nx/js@17.1.2 --to=@nx/js@17.1.3
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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_14_162Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
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: ["nx@17.1.3"]

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_14_667Z-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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_15_948Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
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/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/storybook --from=@nx/storybook@17.1.2 --to=@nx/storybook@17.1.3
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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_17_319Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
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: ["nx@17.1.3"]

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_17_827Z-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: ["nx@17.1.3"]

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_18_429Z-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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_19_125Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
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/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/web --from=@nx/web@17.1.2 --to=@nx/web@17.1.3
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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_20_502Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
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: ["nx@17.1.3"]

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_21_010Z-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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_22_284Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
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/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/webpack --from=@nx/webpack@17.1.2 --to=@nx/webpack@17.1.3
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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_23_654Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
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: ["nx@17.1.3"]

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_24_168Z-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: ["nx@17.1.3"]

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_24_767Z-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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_25_447Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
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/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/workspace --from=@nx/workspace@17.1.2 --to=@nx/workspace@17.1.3
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: ["nx@17.1.3"]

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_26_297Z-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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_26_826Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
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: ["nx@17.1.3"]

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_27_490Z-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: ["nx@17.1.3"]

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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"17.0.3" from @angular/animations@17.0.3
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.0.3" 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! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_28_776Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
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/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate nx --from=nx@17.1.2 --to=nx@17.1.3
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: ["nx@17.1.3"]

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-23T13_23_29_613Z-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: wolsok@3.1.0
npm ERR! Found: @angular/core@17.0.4
npm ERR! node_modules/@angular/core
npm ERR!   @ang

repo: WolfSoko/wol-sok-mono


text:
Not working with the latest version on Angular-cli (beta.17)

Thank you for a great library.
I am getting the error below when I am using version 1.1.0 together with the latest version of Angular-CLI (beta.17)
metadata_resolver.js:700Uncaught Error: moduleId should be a string in "RotatingPlaneComponent". See https://goo.gl/wIDDiL for more information.
If you're using Webpack you should inline the template and the styles, see https://goo.gl/X2J8zc.

My project is very vanilla, I just created a new angular-cli project and then added ng2-spin-kit using the code from the readme.md.
Welcome your thoughts?

@jculverwell Thanks for your feedback ;)
Could you show your code here?
In each component, template and styles are inline. I didn't test components in angular-cli project, but I think that the most important is configuration in your project. Which module bundler do you use?

I get this same issue during runtime when using webpack.
// app.module.ts

...
import * as spinner from 'ng2-spin-kit/app/spinners';

@NgModule({
  declarations: [
    spinner.FadingCircleComponent,
    ...

I'm not actually using it anywhere in html yet, but the import/declaration results in the above error.  Removing the moduleId: module.id line from the component fixes it, but I'm not positive what that's going to do elsewhere.

+1

Yes, I have the same problem with Angular-CLI .21
The hack was to remove the   moduleId: module.id from the spinner component in the Node module folder as mentioned above.

@rodneyjoyce In ng2-spin-kit there is not moduleId in the code. It was before, but newer versions don't have it.

Hmm that's odd, I thought I NPMed the latest package. Thanks

authors: fbarbat jculverwell jgr3go mrzepinski rodneyjoyce


text:
Add listed mentors to the website - Sakirat, Agoro, Tvisha, Sahana

Task
Add the following mentors to the website
URL - https://womencodingcommunity.com/mentors
Mentors to be added
Sakirat Kehinde Usman
Agoro, Adegbenga
Tvisha Dholakia
Sahana Venkatesh
Reference: https://womenwhocode.github.io/london/mentors (helpful to get mentor details)
Acceptance Criteria
Screenshot showing the mentors

I can also take this card.


text:
🛑 Personnal website is down

In 8d9c811, Personnal website (https://woomy.be) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Personnal website is back up in 35b1aa3 after 43 minutes.

repo: Woomymy/status


text:
Handbook clarifications

I've written up a list of ambiguities that I feel the WP CS Handbook page has, which I believe can be addressed by adding a few clarifications. Some are one-line clarifications which shouldn't be an issue to anyone, some would be new sections (namespaces, anyone?) which may need consensus (with who?!) but are still warranted.
@westonruter: as you're a core committer, and can also edit the handbook, please could you take a look through my list and add in the clarifications you feel comfortable doing?
For any others points, I'm open for discussion about the "hole" I've identified, and suggestions on how to get clarification / consensus among the core committers as needed (with the proviso that we know WP Core is historically poor, though improving, at following it's own standards, and that these are coding standards for the WordPress community.
For us here, I feel that having these clarified would potentially allow some of the WordPress-Extras to be in WordPress-Core, or otherwise remove any doubt that something ambiguous in the Handbook is misrepresented in WordPress-Core ruleset.
cc @johnbillion and @jorbin who I believe also have interests here.

we know WP Core is historically poor, though improving

I'd say improving a lot - PHPCS is giving it an A for consistency ;-)
The report might actually be useful to identify additional "hidden" rules: https://squizlabs.github.io/PHP_CodeSniffer/analysis/WordPress/WordPress/index.html

I'd say improving a lot - PHPCS is giving it an A for consistency ;-)

That means:

97.1% of the project's source code conforms to the same coding conventions

...which in turns means it's a consistent code base - not that it's consistent with the standards in the handbook!

True enough, but if you look in more detail, it largely is (on those things which are being measured).

https://github.com/GaryJones/PHP-Coding-Standards is what was started a while ago, with the aim to get the items from my gist, plus other clarifications from others.
It would be really great if a core committer would at least clarify whether this is the right approach to getting the contents of the Handbook improved.

@GaryJones My concern with contributing to a GitHub repo is that it will be difficult to keep it in sync. For one, the Handbook version is HTML but your version is Markdown.
If contribution via GitHub is desired, then I think it would be better if the latest version from WordPress.org were continually synced down via the REST API and then pull requests could be made on top of that version. Ideally the version stored in Git would be the raw post content to make it easier to just copy/paste the new content into the post editor. Nevertheless, it seems the handbook pages aren't currently exposed in the REST API under https://make.wordpress.org/core/wp-json/wp/v2
Maybe I am over-engineering things and it would be better to just propose changes via issues and describe how the changes should be made manually. It seems that commenting has been turned off on the handbook page, but that seems like it would have been a good way to report issues instead of doing it in a separate place. Maybe also this would be something that should be rather tracked in Meta Trac? Each handbook change could be opened as a separate Trac ticket for discussion.

@GaryJones I believe a lot of this has been addressed with the recent changes in the handbook and WPCS. Are you okay with closing this issue ?

authors: GaryJones jrfnl westonruter

repo: WordPress/WordPress-Coding-Standards


text:
Investigate adding pyupgrade to linting checks

Description

We should investigate to see if pyupgrade can be added to the project's pre-commit & linting checks, and whether or not it'd be beneficial to have it as part of our checks.
I have previously used this tool when upgrading projects from python 2 to python 3, however it seems there are even more checks we can locate if we specify a minimum python version with --py3<version>-plus (e.g. --py38-plus): https://github.com/asottile/pyupgrade#remove-parentheses-from-functoolslru_cache
Additional context

Implementation

[ ] 🙋 I would be interested in implementing this feature.

This issue should go in WordPress/openverse. It can be beneficial in the API as well!

Whoever takes this task will have their name on the lines edited by the initial linting, which means incorrect git blame information. If this is a concern, I can run the hook locally to asses the size of changes and then we can determine if a staffer should do it instead.
This is not a concern for #858 since the changes there should be minimal.

@AqeelAT I don't think we'll mind which contributor's name is on the lint-fix commit. But it'll surely be helpful if you can open a PR that shows the impact of the change.
As for the blame issue, we can add a .git-blame-ignore-revs to the repo; see the Black docs for an example of how to use the --ignore-revs-file option.

authors: AetherUnbound AqeelAT dhruvkb

repo: WordPress/openverse-catalog


text:
Collect lighthouse CI on each frontend change

Fixes

Fixes #646 by @obulat
Description

This PR adds a new CI/CD job to collect Lighthouse CI results for each frontend change.
Testing Instructions

The new CI job must pass.... we should see the Lighthouse GitHub App show up in this PR as a result (if I've understood how that works correctly)
Checklist

[x] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[N/A] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[N/A] I tried running the project locally and verified that there are no visible errors.
[N/A] I ran the DAG documentation generator (ov just catalog/generate-docs for catalog
PRs) or the media properties generator (ov just catalog/generate-docs media-props
for the catalog or ov just api/generate-docs for the API) where applicable.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Ah, what a shame, the free "temporary public storage" that is used by Lighthouse CI to support the GitHub app's functionality is (hopefully temporarily) broken: https://github.com/GoogleChrome/lighthouse-ci/issues/1072
We can move forward with this PR as is, and spin up our own Lighthouse CI server on ECS in the meantime. In any case, collecting and running LHCI is the first step to either the publicly available free integration, or an Openverse-specific one where we run the server ourselves (if the free one doesn't come back).

repo: WordPress/openverse


text:
The system supports having sub categories of of work processes that nests skills under it

See example:
WIN_Robotics_Skills_Outline (1).xlsx
And discussion:
Jeanine Soterwood 11:26 AM
Hmm, could we just add a category to the OccupationStandardSkill table with a category…? Or would it really need to be on the Skill table? Like if we added it to the Skill table, then we could be unique across [:category, :description]…?

Or do you feel like we would need another intermediate table?
pcushing 11:28 AM
Honestly, whatever's easiest.
On WorkHands, for the few cases like this, we just stick it in the text like "Safety Procedure - This is a safety procedure skill".
I'd want to be a bit more sophisticated here but dont want to have to tie ourselves in knots, make every other query more difficult, etc. in order to support this

@Pcushing should I modify the import script to handle the new subcategories, or not worry about that for now?

@littleforest yes. Let's do that as it's the main way for us to get this info imported.

authors: Pcushing littleforest

repo: WorkHands/RAPiDSkills


text:
Error parsing json, please check json request

Hello,
I'm experiencing issues creating order with Worldpay API. I tried running your own call as found here https://developer.worldpay.com/jsonapi/docs/make-payment:
curl https://api.worldpay.com/v1/orders -H "Authorization:T_S_<HIDDEN>" -H "Content-type: application/json" -X POST -d '{ "token" : "TEST_SU_<HIDDEN>",  "orderDescription" : "your-order-description", "amount" : 500, "currencyCode" : "GBP" }'
and here's what I get:
< HTTP/1.1 400 Bad Request
< Content-Type: application/json;charset=UTF-8
< Date: Fri, 25 Nov 2016 08:19:49 GMT
< requestId: ef0e0b6b-8a50-4810-b8d1-bbc77d1a7753
* Server Windows NT 3.x is not blacklisted
< Server: Windows NT 3.x
< X-Content-Type-Options: nosniff
< Content-Length: 221
< Connection: keep-alive
<
{"httpStatusCode":400,"customCode":"ERROR_PARSING_JSON","message":"Error parsing json, please check json request","description":"Error parsing Json, please refer to json schema","errorHelpUrl":null,"originalRequest":"'{"}* Connection #0 to host api.worldpay.com left intact

Can you check it please ?
Stephane

Hi Stephane (@VerilySoft) ,
I have checked the logs related to this request and no data was sent with the curl.
Could you please use the below code replacing with your ServiceKey and Token
curl https://api.worldpay.com/v1/orders -H "Authorization:<T_S_value>" -H "Content-type: application/json" -X POST -d '{ "token" : "<TEST_TOKEN>", "orderDescription" : "your-order-description", "amount" : 500, "currencyCode" : "GBP" }'

I just sent a request and here are the details (replaced with my service key and token):
root@vps151644:~# curl -v https://api.worldpay.com/v1/orders -H "Authorization:T_S_c8" -H "Content-type: application/json" -X POST -d '{ "token" : "TEST_RU_", "orderDescription" : "your-order-description", "amount" : 500, "currencyCode" : "GBP" }'

Adding handle: conn: 0x1121b90
Adding handle: send: 0
Adding handle: recv: 0
Curl_addHandleToPipeline: length: 1

Conn 0 (0x1121b90) send_pipe: 1, recv_pipe: 0

About to connect() to api.worldpay.com port 443 (#0)
Trying 52.19.201.7...
Connected to api.worldpay.com (52.19.201.7) port 443 (#0)
successfully set certificate verify locations:
CAfile: none
CApath: /etc/ssl/certs
SSLv3, TLS handshake, Client hello (1):
SSLv3, TLS handshake, Server hello (2):
SSLv3, TLS handshake, CERT (11):
SSLv3, TLS handshake, Server key exchange (12):
SSLv3, TLS handshake, Server finished (14):
SSLv3, TLS handshake, Client key exchange (16):
SSLv3, TLS change cipher, Client hello (1):
SSLv3, TLS handshake, Finished (20):
SSLv3, TLS change cipher, Client hello (1):
SSLv3, TLS handshake, Finished (20):
SSL connection using ECDHE-RSA-AES128-SHA
Server certificate:

   subject: C=GB; ST=London; L=London; O=WorldPay (UK) Ltd; CN=api.worldpay.com

   start date: 2016-09-20 00:00:00 GMT

   expire date: 2018-09-21 23:59:59 GMT

   subjectAltName: api.worldpay.com matched

   issuer: C=US; O=Symantec Corporation; OU=Symantec Trust Network; CN=Symantec Class 3 Secure Server CA - G4

   SSL certificate verify ok.

POST /v1/orders HTTP/1.1
User-Agent: curl/7.32.0
Host: api.worldpay.com
Accept: /
Authorization:T_S_c8d
Content-type: application/json
Content-Length: 147

upload completely sent off: 147 out of 147 bytes
< HTTP/1.1 400 Bad Request
< Content-Type: application/json;charset=UTF-8
< Date: Fri, 25 Nov 2016 14:23:02 GMT
< requestId: c59a05d3-e80a-470b-b6c0-e259e65f87b5
Server Windows NT 3.x is not blacklisted
< Server: Windows NT 3.x
< X-Content-Type-Options: nosniff
< Content-Length: 393
< Connection: keep-alive
<
Connection #0 to host api.worldpay.com left intact
{"httpStatusCode":400,"customCode":"BAD_REQUEST","message":"CVC can't be null/empty","description":"Some of request parameters are invalid, please check your request. For more information please refer to Json schema.","errorHelpUrl":null,"originalRequest":"{'token':'TEST_RU_5','orderDescription':'your-order-description','amount':500,'currencyCode':'GBP'}"}

@VerilySoft That httpResponse appears to be from the second time you've executed that order with the reusable token, is that correct? Could you please provide the first response?

I don't have the first full response because I executed it in a console window I closed. I just run the request you ask me to. I don't have the full response but I added a part in the op:
< HTTP/1.1 400 Bad Request
< Content-Type: application/json;charset=UTF-8
< Date: Fri, 25 Nov 2016 08:19:49 GMT
< requestId: ef0e0b6b-8a50-4810-b8d1-bbc77d1a7753
* Server Windows NT 3.x is not blacklisted
< Server: Windows NT 3.x
< X-Content-Type-Options: nosniff
< Content-Length: 221
< Connection: keep-alive
<
{"httpStatusCode":400,"customCode":"ERROR_PARSING_JSON","message":"Error parsing json, please check json request","description":"Error parsing Json, please refer to json schema","errorHelpUrl":null,"originalRequest":"'{"}* Connection #0 to host api.worldpay.com left intact

The first request I made was done from the browser in JavaScript. Then it passed the token to the web server to charge the customer. The issue then appears here.

Hello, any idea what would be the issue. I created a token from JavaScript then try charging card from server where it reported JSON format isn't valid while it is.

@VerilySoft Can you please confirm that the token you created from Javascript has not been used yet, as this error is often present when you try to reuse a token.

What about when I set reusable to true ?

You shouldn't get 400's with this particular request with reusable=true;

I'm having the same issue, no real error message passed back, apart from "Error parsing json, please check json request".
As the WorldPay library is used to send the JSON, I presume this is either a bug in the library or an error that doesn't actually describe the problem?

I've found what was causing the issue for me (I was sending a non integer amount). @VerilySoft looks like that was the same issue in your JSON you were sending,
Best to double check the JSON string you send as WorldPay doesn't return useful errors. You can do that in the sendRequest function in the Connection class.
Hope that helps someone in future!

I've found what was causing the issue for me (I was sending a non integer amount). @VerilySoft looks like that was the same issue in your JSON you were sending,
Best to double check the JSON string you send as WorldPay doesn't return useful errors. You can do that in the sendRequest function in the Connection class.
Hope that helps someone in future!

Thank you. I solved my problem is same

I'm also having the same problem. But my case is different. Through payment form token generated and charges also happened. When I'm trying to do recurring payment with reusable token Id at the time I'm getting response JSON parse error like that . For the same request data I just removed Address value then It is charging. I have checked my merchant portal by disabling/enabling address verification option even though I'm getting same error.
If world pay returning with proper api response particular error . I could be better to show end user to change their input during charges.
Common error response creating lot of support issue.
Please try to address actual problem for immediate solution.

authors: VerilySoft ao cllakyz markgarbers rprakashqt

repo: Worldpay/worldpay-lib-php


text:
🛑 XAONIX.com is down

In d60919e, XAONIX.com (https://xaonix.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XAONIX.com is back up in 4299ae0.

repo: XAONIX/status


text:
🛑 cc is down

In 74dee44, cc (https://codeforces.cc) was down:

HTTP code: 403
Response time: 493 ms

Resolved: cc is back up in 76e7b12.


text:
Make release v1 0 0

What does the code in this PR do / what does it improve?
Make a new release

Somehow version bump made a strange update...

repo: XENONnT/straxen


text:
Restore #757

#757 was merged but it caused errors downstream. Maybe we need some more testing on this class anyway.

@zhut19 can it be that the map wasn't updated in privevat nt files repo?

Pull Request Test Coverage Report for Build 1588428236

5 of 7 (71.43%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.02%) to 85.47%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

straxen/itp_map.py
5
7
71.43%

Files with Coverage Reduction
New Missed Lines
%

straxen/itp_map.py
2
77.04%

Totals

Change from base Build 1588250126:
0.02%

Covered Lines:
6059

Relevant Lines:
7089

💛  - Coveralls

Thanks for the checks!

authors: JoranAngevaare coveralls l-althueser