-
Notifications
You must be signed in to change notification settings - Fork 19
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
Exporter silently stops scraping after 73181 artifacts #5
Comments
Same error. |
Sadly, no. Had to resort to a web-scraper (HTTrack) to get the job done.
tir. 1. feb. 2022, 10:52 skrev scrhall ***@***.***>:
… Same error.
you found a solution or workaround? @SnorreSelmer
<https://github.com/SnorreSelmer>
—
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEWMEQDUJMSWATZ47JWKV43UY6UMRANCNFSM5CWLJKQQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I run the exporter with Java 11, and it works great ... for a while. It runs fine, downloading 73818 artifacts, and then seems to stop fetching lists of more artifacts to download, for the worker-threads finish their workload, and then just halts. The app is still running, waiting for something that never arrives.
2021-08-24 10:36:13.452 INFO 2736 --- [pool-1-thread-3] fr.kage.nexus3.DownloadRepository : Downloaded 73174 assets on 73181 found
The discrepancy between found and downloaded is that it tries to download artifacts that have already been downloaded.
I'm at a loss how to attack this for debugging purposes. I'm not sure if there's some artifact that causes this behavior or if it's the exporter itself, or even our Nexus instance.
The text was updated successfully, but these errors were encountered: