-
Notifications
You must be signed in to change notification settings - Fork 29
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
BatchtoolsParam fails to propagate errors in bpiterate #257
Comments
Session info:
Session info for the compute cluster, in which the same error is observed:
|
Note: I originally discovered this issue in the context of the use of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've discovered a case where BatchtoolsParam behaves differently from other backends. Consider the following reprex:
Created on 2023-07-07 with reprex v2.0.2
With any other backend (SerialParam, MulticoreParam, SnowParam), the
bpiterate
call throws an error (verified here by callingexpect_error
). However, BatchtoolsParam does not throw an error and instead returns a list with all NULL elements and an attribute "errors" containing the errors thrown during iteration. Furthermore,bpok
says this object is totally fine. I would expect BatchtoolsParam to behave the same as the other backends here.The text was updated successfully, but these errors were encountered: