-
Notifications
You must be signed in to change notification settings - Fork 26
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
test_nwb2asset_remote_asset timed out in test (ubuntu-latest, 3.8, dandi-api) #1450
Comments
@yarikoptic That's normal. The test performs three methods calls on the remote asset object that each ultimately end up having to request the asset's metadata from the server. |
ah, if that is not a sign of repeated rerequests -- can you tell from above what is timing out? |
@yarikoptic fsspec is timing out while trying to read the asset over S3. |
ok, let's shelf it for now but if we keep coming to it, might need smaller asset I guess. |
it hit us in daily tests again https://github.com/dandi/dandi-cli/actions/runs/10026093264/job/27710002745 and apparently it is quite common
|
@yarikoptic I don't believe there's anything that can be done about this. It's almost certainly a network and/or S3 problem (or conceivably some inefficiency in fsspec, but I'm not about to debug that). |
I would expect some layer to time out more promptly and so that we have a record that some attempts are repeated. If it just stalls -- it might be something more severe/worth fixing. Let's see how often it would come about (there was a fresh cases in dandi-schema) |
https://github.com/dandi/dandi-cli/actions/runs/9395898413/job/25876096821
@jwodder please remind what those trailing requests are for -- waiting for validation or smth? I wonder if it is result of some recent change...
The text was updated successfully, but these errors were encountered: