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

Globus staging returns unclear error #178

Closed
yadudoc opened this Issue Mar 30, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@yadudoc
Copy link
Member

yadudoc commented Mar 30, 2018

Here's the error we get when we try to stage in a file without setting the globus endpoint path in the config:

globus_sdk.exc.TransferAPIError: (400, 'ClientError.BadRequest.ResourcePropertyValueError', "invalid value '' for property 'destination_endpoint' of type 'string.ascii.endpoint_name': value does not match regex '([a-z][0-9a-z_]+#)?[0-9a-zA-Z_][-0-9a-zA-Z_.]*'", 'gX6cpN9gL')

This is not super helpful. We should catch this in the globus initialization and simply report that the endpoint_name is not set or malformed.

@yadudoc yadudoc added the bug label Mar 30, 2018

@yadudoc yadudoc added this to the Parsl-0.6.0 milestone Mar 30, 2018

@lukaszlacinski

This comment has been minimized.

Copy link
Collaborator

lukaszlacinski commented Apr 2, 2018

  1. I am not able to replicate the error. The config without endpoint_path works for me.
  2. The error says that endpoint_name is set to ''. It is not a bug in Parsl. Parls does not know what is the correct endpoint_name. The Globus service does. Maybe Parsl should present Globus exceptions in a more user friendly form.
@kylechard

This comment has been minimized.

Copy link
Collaborator

kylechard commented Apr 27, 2018

I agree on the final point here:

Parsl should present Globus exceptions in a more user friendly form.

Lets see if we can get this in 0.6

@yadudoc

This comment has been minimized.

Copy link
Member Author

yadudoc commented Jun 18, 2018

Fixed in new config support.

@yadudoc yadudoc closed this Jun 18, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.