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

TypeError raised when a bad stdout/stderr path is provided. #104

Closed
yadudoc opened this Issue Feb 28, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@yadudoc
Contributor

yadudoc commented Feb 28, 2018

When a bash app is provided a non-existent file path for stdout/stderr instead of BadStdStreamFile, a TypeError is being thrown now. This is due to a bug in parsl.app.errors.BadStdStreamFile having a type mismatch.

A fix is being tested.

Reported by @djf604

@yadudoc yadudoc added the bug label Feb 28, 2018

@yadudoc yadudoc added this to the Parsl-0.5.0 milestone Feb 28, 2018

@yadudoc yadudoc self-assigned this Feb 28, 2018

yadudoc added a commit that referenced this issue Feb 28, 2018

Fixing bug in errors code. Fixes #104
Adds more exception handling around setting stdout/stderr streams
in bash apps.

@yadudoc yadudoc closed this in 376d798 Feb 28, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment