-
Notifications
You must be signed in to change notification settings - Fork 370
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
IncompleteRead Error while trying to load demo videos #1414
Comments
I'll start looking into this locally, although I thought I had taested this earlier; is there any chance your HD may have filled up resulting in corrupt files, or anything like that? |
There's about 100 GB of storage remaining, so I doubt that's the issue. It also fails pretty fast - within a minute. |
Ok, I'll see what I can figure out then; I may have followup questions (e.g. opencv version) depending on how that goes. |
Having tried to reproduce this and having looked more carefully at the error,
So, we have a few routes forward to see if we can resolve this; my two main theories are that either: A) You're somplace with unusual network issues, or This chunk of code shows where the download_demo() function retrieves demo files from: https://github.com/flatironinstitute/CaImAn/blob/main/caiman/utils/utils.py#L66 If you go into ~/caiman_data/example_movies/ and remove the bad file and then do a (adjust to use curl if you don't have a wget) This should help us figure out what's going on (you may also see, if you're on a laptop if you get the same issue while running on another network, e.g. at home or in a coffeeshop) |
Sorry about the delay @pgunn. yes, running |
I have just successfully run wget https://caiman.flatironinstitute.org/~neuro/caiman_downloadables/msCam13.avi to download the same video file that the |
This is puzzling; for now you can work around this with manual fetches of the demo data; it may be useful to see if you get the same results from the CLI demos. Occasionally in the past we saw issues with certs in python, but that usually would cause an upfront failure rather than a failure partway through a download. I'd expect that if a router might cancel big downloads, it'd do it the same for wget vs python doing the same thing. Unless perhaps it's different http headers leading to different treatment. It's also possible OSX itself is being weird, although that seems unlikely. Knowing you have a pretty easy workaround, it may not be worth your time to debug this the rest of the way, but you have me curious and I'm happy to do it - up to you. Have you tried doing this from some different network? e.g. a coffeeshop, home, or some other place where you've seen this issue? |
Yeah, those were my expectations, as well. I haven't tried As far as I'm concerned, it does not actually impact my workflow anymore since you have identified a workaround for me :) I am happy to pair with debugging, if you'd like to RCA. |
demo_online_cnmfE.ipynb
,demo_realtime_cnmfE.ipynb
Downloading demo videos fails in
demo_online_cnmfE.ipynb
, anddemo_realtime_cnmfE.ipynb
notebooks. They throw identical errors.within
demo_realtime_cnmfE.ipynb
,throws:
and within
demo_online_cnmfE.ipynb
,throws a similar error.
The read/expected byte size change every trial. While
demo_online_cnmfE.ipynb
can bypass the error by fetching thedata_endoscope.tif
file instead (changingmovie_ind
to1
.), there is no similar option fordemo_realtime_cnmfE.ipynb
The text was updated successfully, but these errors were encountered: