Open alexander-held opened 2 months ago
Could it be that you triggered some rate limiter on the server or something like that? I haven't been able to reproduce it.
It's certainly possible that the issue originated from the remote file source, I cannot reproduce it at the moment either. I suspect that my thinking when I opened this originally was maybe that the error message is somewhat confusing? I would expect something like a ClientResponseError
or FileNotFoundError
, but this specific error message feels like something perhaps should have been caught earlier in a more descriptive way. Unfortunately without being able to reproduce this failure mode, feel free to close and I can get in touch again if I manage to do reproduce this in a more stable manner.
Yeah, that's a good point. A better error message would be nice.
During debugging I ran into some surprising crashes. I was processing the same file multiple times in a setup that can be broken down to this:
The first loop iteration is fine, the second one results in a crash:
The error is not reproducible with local files for me.
I am using
uproot
version5.3.10
.Full trace: