Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Fix dataset downloading #7864
Fix dataset downloading #7864
Changes from 12 commits
d7bb1c1
7f151b1
f48e807
4c58bf5
d7fa31d
5c22d28
49baadf
de73fe6
35ce1f6
7b671f5
4a4b5d0
05f6dd1
2c4be73
5dc3e56
4c24e10
98ad20e
963f657
2bf19db
c0769f0
087ac42
0d75d4a
ea71c7d
7085076
f8d142f
9479888
da06903
700bf2c
9ccafc5
c2b3049
228e82e
4ddc79d
447b4df
2a67f2e
4471aa9
de2c805
e76382d
2af76a8
aafc369
275a274
297d686
8d5401c
664ed28
6fc3f63
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could at least log a warning if the lock was unlocked? It seems like it could cause hard-to-debug issues, so some diagnostics would be helpful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But there's still no diagnostic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it happens, it's being logged in both worker callbacks as a regular exception. For requests, it can be logged there once there is such logic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand, how can it be logged when
get_export_cache_lock
doesn't report this case in any way? Maybe we're talking about different things? I'm talking about the scenario where the code within the scope of the context manager takes too long and the lock unlocks by itself.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, restored the exception. However, I only expect these exceptions to be obtainable in downloading endpoints, as the rq workers should be killed before the lock is expired, if they work for too long.