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.

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

Error for globus transfer failure #162

Closed
kylechard opened this issue Mar 24, 2018 · 3 comments
Closed

Error for globus transfer failure #162

kylechard opened this issue Mar 24, 2018 · 3 comments
Assignees
Labels
Milestone

Comments

@kylechard
Copy link
Collaborator

At the moment if the transfer fails we get a FileNotFoundError. Ideally, we should tell the user that the transfer failed and perhaps relay the Globus error message.

@yadudoc yadudoc added the bug label Mar 24, 2018
@yadudoc yadudoc added this to the Parsl-0.5.0 milestone Mar 24, 2018
@annawoodard
Copy link
Collaborator

We think this is because Kyle was not calling .result()

@annawoodard
Copy link
Collaborator

(deferring this because it relies on #169 and is a substantial enough change it will not be ready for 0.5)

@lukaszlacinski
Copy link
Contributor

Parsl 0.5.0 implements explicit staging, so it requires calling result() on a DataFuture object.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants