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

Unable to renew or see Toolshed API keys due to internal server error 500 #18242

Closed
hechth opened this issue May 28, 2024 · 5 comments
Closed
Assignees
Labels
area/backend area/database Galaxy's database or data access layer area/toolshed kind/bug

Comments

@hechth
Copy link

hechth commented May 28, 2024

Describe the bug
Currently it is not possible for us to update tools on the toolshed and testtoolshed via the CI (https://github.com/RECETOX/galaxytools/actions/runs/9254908691/job/25486748998) or via the planemo CLI.

We get an API key invalid error on the testtoolshed bioblend ERROR: GET: error 401: b'{"err_msg":"Provided API key is not valid.","err_code":401001}', 0 attempts left and a unknown error 500 when trying to update the regular toolshed.

Additionally, it is not possible to update the Galaxy toolshed API key through the toolshed UI.
Is there a different way to update the API key?

Browser and Operating System
Operating System: Windows
Browser: Firefox, Librewolf and Chrome persistently have the same problem displaying the API key.

Expected behavior
I'd expect the toolshed UI to allow me to update API keys.

Screenshots
This should display the API key though it just doesn't display anything. I am logged in.
image

@mvdbeek mvdbeek added kind/bug area/toolshed area/database Galaxy's database or data access layer area/backend labels May 28, 2024
@mvdbeek
Copy link
Member

mvdbeek commented May 28, 2024

@natefoo @jdavcs maybe a broken migration ? https://sentry.galaxyproject.org/share/issue/04adfef3d6cc4370bfe2a5bfca671b7c/

@hechth
Copy link
Author

hechth commented May 29, 2024

Seems like the toolshed is now completely down :D

@jdavcs
Copy link
Member

jdavcs commented May 30, 2024

Apparently this was the last migration on the old sqlalchemy migrate system, and it somehow fell through the cracks.
Here's the old one: https://github.com/galaxyproject/galaxy/pull/14489/files#diff-fa487f1639fd05014a3ec90f54d78393aa5ae32290b65e3a33d746863d2e91d9

Fix coming up. I'll add a migration and we'll apply it to the TS database.

@mvdbeek
Copy link
Member

mvdbeek commented May 30, 2024

We never intended for the deleted column to be manadatory on the TS side, there's more to it.

mvdbeek added a commit to mvdbeek/galaxy that referenced this issue May 30, 2024
@mvdbeek
Copy link
Member

mvdbeek commented May 31, 2024

That's fixed now.

@mvdbeek mvdbeek closed this as completed May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/backend area/database Galaxy's database or data access layer area/toolshed kind/bug
Projects
None yet
Development

No branches or pull requests

3 participants