-
Couldn't load subscription status.
- Fork 536
BF: Fix DataFinder bug introduced in d985f677 #761
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
Conversation
| Changes Unknown when pulling 87133b1 on moloney:bf-datafinder into * on nipy:master*. |
1 similar comment
| Changes Unknown when pulling 87133b1 on moloney:bf-datafinder into * on nipy:master*. |
| Thanks for fixing this. If possible, it would be nice to get a test case to cover this, since apparently the testing suite missed it. |
| Yes! A test would be very welcomed! |
| A merge of this one would be awesome -- we experience a full stop of most of the nipype operations on our cluster after upgrading it to Debian wheezy/stable... and with the fix |
| We will do a quickfix release as soon as there is a test for this. On Wed, Jan 8, 2014 at 12:09 PM, Michael Hanke notifications@github.comwrote:
|
| @chrisfilo do you mean that these lines are not included in those whooping 70%? !!! ay yay yay ;-) |
| IMHO no need to wait for a test, it is obviously a typo which was introduced Thus using my god powers (someone of cause is still welcome to provide a unittest), but we should kick out bugfix snapshot release asap for this |
BF: Fix DataFinder bug introduced in d985f67 (Test is TODO)
| I was just trying to motivate someone to add a test so this would not On Wed, Jan 8, 2014 at 3:40 PM, Yaroslav Halchenko <notifications@github.com
|
| yikes, according to coveralls.in |
|
me too |
| Sorry to go MIA after opening the PR. I will see if there is anything I can contribute over in #765. |
No description provided.