Closed alexandruz closed 9 months ago
.../node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/...
This looks a lot like a circular dependency. We had issues like this before, but fixed them. So this could be a regression.
@fviernau, could it be that this broke in 3b6ad90ade82085d3bb8bfaa293c6d7c7c1dca93 as that removed the log about "Not adding circular dependency '$identifier' to the tree"?
fviernau, could it be that this broke in 3b6ad90 as that removed the log about "Not adding circular dependency '$identifier' to the tree"?
This commit does not remove the log output, it left it here: https://github.com/oss-review-toolkit/ort/commit/3b6ad90ade82085d3bb8bfaa293c6d7c7c1dca93#diff-28d89c724dd945fe93dec5700d61d4dcdaab02f492e09613c8fee6ac5c76cbe6R397
There have been quite a bit of commits since back then, any special reason besides the mentioned "removal of log output", to investigate it from this point?
@alexandruz - this can be reproduced by running the analyzer on [1], right?
Apart from that, which params did you provide for the max memory to java ? -Xmx
?
There have been quite a bit of commits since back then, any special reason besides the mentioned "removal of log output", to investigate it from this point?
No, I was just searching for removals of "circular" and landed straight there.
I didn't change any of the default settings, but I'll try with some more memory. @fviernau yes, those debug messages are from running analyzer on the respective project
ort seems to take advantage of entire free memory on the system, but in this case nothing happens, as it can with 16 CPUs and a maximum of 7952 MiB of memory
(ec2 instance), but the same behavior as described.
some of the logs:
10:58:47.358 [DefaultDispatcher-worker-35] DEBUG org.ossreviewtoolkit.analyzer.managers.Npm - Found a 'package.json' file in '/builds/alexandruz/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/table/node_modules/ajv'.
10:58:47.358 [DefaultDispatcher-worker-35] DEBUG org.ossreviewtoolkit.analyzer.managers.Npm - Finished parsing '/builds/alexandruz/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/pixi-v6-iife/node_modules/@pixi/particle-emitter/node_modules/table/node_modules/ajv/package.json' to 'NPM::ajv:8.6.2'.
I've create a test package, similar to particle-emitter:
├── package.json
└── test
└── my-ort-test-package
└── package.json
with the following contents of these files:
$ cat package.json
{
"name": "my-ort-package",
"version": "1.0.0",
"workspaces": {
"packages": [
"./",
"test/my-ort-test-package"
]
},
"private": true
}
cat test/my-ort-test-package/package.json
{
"name": "my-ort-test-package",
"version": "1.0.0",
"dependencies": {
"my-ort-package": "*"
},
"workspaces": {
"nohoist": [
"my-ort-package"
]
},
"private": true
}
And I get a similar result:
08:49:31.945 [DefaultDispatcher-worker-7] DEBUG org.ossreviewtoolkit.plugins.packagemanagers.node.Npm - The package directory '/ort/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package/node_modules/my-ort-test-package/node_modules/my-ort-package' links to '/ort'.
hello @fviernau,
testing the created package I realized that there is a circular dependency that ort analyzer
doesn't pick up on, because it doesn't manage correctly the workspaces
setting with the nohoist
options.
Can you provide some help where should I look it the code for this issue?
Thanks.
there is a circular dependency that
ort analyzer
doesn't pick up on, because it doesn't manage correctly theworkspaces
setting with thenohoist
options.
Actually, ORT itself isn't interpreting the nohoist
option at all. Instead, we simply call yarn install
and parse the resulting node_modules
directory hierarchy. That's where the issue is located. I'll propose a fix soon.
The OSS Review Toolkit, version e57fed5.
docker buildOSS Project: https://github.com/pixijs/particle-emitter/
after a couple hundred MB of logs:
Something is amiss and I can't figure it what/why. 🙏🏻
tried with: