Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use force_unlock in copy_exemplars Python workflow #396

Merged
merged 1 commit into from
Jan 16, 2025
Merged

Use force_unlock in copy_exemplars Python workflow #396

merged 1 commit into from
Jan 16, 2025

Conversation

tsalo
Copy link
Member

@tsalo tsalo commented Jan 16, 2025

Closes none, but addresses a bug I noticed in #394. It looks like copy_exemplars() uses the force_unlock argument when running in a container, but not when running just with Python.

Changes proposed in this pull request

  • Use force_unlock when initializing CuBIDS object in copy_exemplars workflow function.

@tsalo tsalo added the bug Something isn't working label Jan 16, 2025
@tsalo tsalo marked this pull request as ready for review January 16, 2025 19:42
@tsalo tsalo requested a review from tientong98 January 16, 2025 19:42
@tsalo tsalo mentioned this pull request Jan 16, 2025
Open
@tientong98 tientong98 merged commit 5c90ae5 into main Jan 16, 2025
10 checks passed
@tientong98 tientong98 deleted the exemplar-force-unlock branch January 16, 2025 19:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@tientong98 tientong98 tientong98 approved these changes

Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@tsalo @tientong98