-
Notifications
You must be signed in to change notification settings - Fork 12
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
MAINT: Update for latest API #75
Conversation
Made things green in mne-tools/mne-bids#1081 |
And in mne-tools/mne-bids#1083 |
Download steps appear to be succeeding in mne-tools/mne-bids-pipeline#634 / https://app.circleci.com/pipelines/github/mne-tools/mne-bids-pipeline/3354/workflows/47b0dfe0-90d0-4e3a-9211-492bca84c886 |
@larsoner I've pushed the following changes
WDYT? |
Okay for me! This can take 30-60 sec so as long as there is actually some output to tell people "it's not broken, it's just slowly working" I'm happy |
Yes, it keeps updating!! See: Screen.Recording.2022-10-14.at.23.18.04.mov |
@larsoner Feel free to merge if happy |
The only comment I have with this iteration is that the |
Now that it's faster, and seeing how simple it is with the entities/files (and how complicated it would have to be to support directories) -- I don't think it's worth it. I push a commit to speed it up by a factor of ~2 by avoiding the "snapshot check" during file iteration, as we've already validated that the snapshot exists by that point. So I've marked this for merge. Feel free to create a release after this is in @hoechenberger ! |
Amazing, great work, @larsoner!!!! |
We forgot to do that in #75
We forgot to do that in #75
@larsoner Do you have any idea why in this workflow: the version number is reported as 2022.1.0 and not as the latest one (2022.2.0)? It works for me locally, but it seems that workflow is ignoring the newly-added tag?? |
Oh … not true, even locally I get the old version number! Ouch… |
Oooohhh… we're not using setuptools-scm here! OUCH :) |
All good, new release was automatically pushed to PyPI!! |
Locally I get something that seems to work:
I've tried it half a dozen times and so far no retry limit problem on the traversal. So I think we can leave it for future work to combine the filename traversal (which uses a generator/yield already) with file download queuing.
@hoechenberger feel free to try and merge if you're happy. I'm going to tell MNE-BIDS-Pipeline to use this branch in an upcoming PR, too, so we'll get some feedback there.
Closes #64
Closes #73