-
-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Long (ever?) running process when combining FETCH_LICENSE=true and PREFER_MAVEN_DEPS_TREE=true #1264
Comments
How interesting... I've been having issues at my org with Maven repositories for the past few months. We use cdxgen in server mode and the BOM processes which used to work flawlessly are now timing out and/or hanging. I've been busy on other deliverables so haven't had time to triage what could be contributing to the stalling |
Hey, @prabhu any insights into this? |
Some debug information. debug log: |
How does it look with the latest version and the master? Lots of fixes have gone in since 10.8.1 |
pardon me, detected it in the latest cdxgen but locally did not update before reproducing. Exact same behavior with cdxgen 10.8.7. |
Found the bug. Example: https://github.com/apache/maven-resolver/tree/${project.scm.tag} Using IriValidationStrategy.Pragmatic makes it finish sooner, so it must be the presence of |
Please test with the branch #1266 |
awesome! works for me now, thx @prabhu. There are quite some errors in the debug.log, like
just in case that's relevant ;) |
@heubeck could you retest with the latest? |
no more errors in the debug output. thx for the quick resolution... as always ;) |
Happy to report our maven workloads are working better than they have in recent months after upgrading to |
Thank you for your confirmation and support! |
Related: comunica/validate-iri.js#19 |
Using my simple test application https://github.com/heubeck/examiner causes cdxgen to run forever when using
FETCH_LICENSE=true
andPREFER_MAVEN_DEPS_TREE=true
.Have seen this on other projects as well, even before using
PREFER_MAVEN_DEPS_TREE=true
, but now it's reproducable.cdxgen version: 10.8.1
as you seen in the screenshot, I aborted the last command after 27 minutes, but during the whole runtime, the node process consumed 100% of a single CPU core.
The text was updated successfully, but these errors were encountered: