-
Notifications
You must be signed in to change notification settings - Fork 287
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
pybids shipped/used by 20.2.1 LTS is still curious about all things .git/ #2426
Comments
@effigies et al -- any guidance to guide a user would be appreciated (insofar it was |
We may be able to specifically ignore these things, since we'll have a pinned pybids in the lts. But thanks for looking into this. Have a bit of a backlog... |
Trying to reproduce inside a docker container fails. Are you able to provide a minimal reproduction? |
will try later on, meanwhile received another user's report with
|
Hey @yarikoptic, did you finally find the issue or further info for @effigies to replicate? |
will try to provide a complete reproducer today but I guess any broken symlink'ed .json under |
I think it might have been resolved as of 20.2.3 here is a quick and dirty dump from bash history on how I reproduced first in 20.2.1:
so I got a "random" (first) dataset from openneuro, created broken links to .json files in locations implicated in the issue report, and then (since still lacking space to
and now running 20.2.3 using
and it looks like doing useful stuff now (might leave this session open overnight to see it complete), but staying positive, let's consider this resolved for now. edit: finished without a fail -- great! |
What version of fMRIPrep are you using?
20.2.1-LTS
What kind of installation are you using? Containers (Singularity, Docker), or "bare-metal"?
I believe a container (dunno details)
crashes with
within pybids -- not sure why to look under
.git/
at all.here is the traceback user provided
didn't try yet to dig deeper, but may be something (like "aha -- was addressed in pybids X which isn't included in this LTS, or didn't make it into LTS) rings a bell?
The text was updated successfully, but these errors were encountered: