-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add Compy endpoint to Globus file #274
Comments
See #275 and please feel free to edit the PR without consultation :) |
Note that, |
@mahf708 Did you (or can you) run the following on Compy?
I'm getting the following error on both
That error message isn't terribly helpful. (It looks like my Globus endpoint is activated: https://app.globus.org/file-manager/collections/68fbd2fa-83d7-11e9-8e63-029d279f7e24/overview) Perhaps related, using the latest Unified RC, I get:
|
@forsyth2 I will test tomorrow or Friday; if you don't hear from me, please nudge me again (I actually don't like using compy because it is so annoying lol ... but I also need to get some files from compy to NERSC so this is a good chance to test) |
Ah, I knew I had seen this error before. Searching GitHub, I found In #250 (comment), Xylar says:
Changing @mahf708 If you can run the test on Compy and see if you run into the same issue, that would be helpful in my debugging. Thanks! |
Sorry, I let you down on this. I am on it right now. I will report back shortly. |
|
No worries, thanks!
I get the same errors as in your image. Clicking "view details", I get:
I wasn't aware of the extra detail there; that matches what you got.
I don't think so? At least, it wasn't a big enough problem to remember. And almost certainly not on this small test case. |
Do you see anything in the diffs that may be helpful? v1.3.0...v1.4.0rc2 |
The type of error tells me it's either you changed settings/names or it is an external auth library... |
The fair-research-login diff: - fair-research-login 0.3.0 pyhd8ed1ab_0 conda-forge
+ fair-research-login 0.2.6 pyhd8ed1ab_0 conda-forge |
@mahf708 Thank you for pointing out the diff from the latest release version. I just ran on the latest official release of Unified, and the Globus test actually gives the same result. That seems to indicate something happened with the way Globus, |
Actually, anything involving a package wouldn't make sense, because we have the version pinned. That means it must be something that changed with Globus, right? |
I see, please see below the globus changes: - globus-cli 3.10.1 pyhd8ed1ab_0 conda-forge
- globus-sdk 3.15.0 pyhd8ed1ab_0 conda-forge
+ globus-cli 3.15.0 pyhd8ed1ab_0 conda-forge
+ globus-sdk 3.21.0 pyhd8ed1ab_0 conda-forge
|
But these are still packages. We know |
Let me test something for you, just give me a second. Does this fail similarly anywhere else or just here? |
The Globus test on Compy is the only issue I'm having with the upcoming |
(I suppose now I should have made these comments in a separate issue, but I thought this endpoint change might be the necessary fix. Apparently that's not the case). |
Btw, I just tested and it fails similarly with older release zstash / e3sm-u... not sure how to help 😢 |
(I also tried different permutations of the libraries to no avail) |
@mahf708 Thank you for helping to debug. I'm going to open an issue specifically to address this, since it's now clearly unrelated to this pull request. |
I created #279. Unfortunately, I can't test this pull request on Compy until that is resolved. |
No worries about this PR. It's not essential and the workaround is pretty straightforward. |
Add Compy endpoint to Globus file.
In https://github.com/E3SM-Project/zstash/blob/main/zstash/globus.py, add Compy's Globus endpoint.
The text was updated successfully, but these errors were encountered: