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.

Sign up for GitHub

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

Jump to bottom

history storage client works with unencoded IDs #17729

Closed
martenson opened this issue Mar 14, 2024 · 1 comment
Closed

history storage client works with unencoded IDs #17729

martenson opened this issue Mar 14, 2024 · 1 comment
Assignees
@davelopez
Labels
area/backend kind/bug release-testing-24.0
Milestone
24.0

Comments

@martenson
Copy link
Member

martenson commented Mar 14, 2024 •
edited
Loading

These two links (from https://usegalaxy.org/storage/history/213e34fd40cc3941) go to the URLs below instead of using the proper datasets ID f9cad7b01a472135ada5934941e2bb74. I assume those are decoded database ids which should not be used on client or returned from the API for that matter.

Screenshot 2024-03-14 at 9 15 38 AM

https://usegalaxy.org/datasets/115168806/details
https://usegalaxy.org/api/histories/213e34fd40cc3941/contents/datasets/115168806

Galaxy Version and/or server at which you observed the bug
Galaxy Version: 24.0
@jdavcs jdavcs added this to the 24.0 milestone Mar 18, 2024
@davelopez davelopez self-assigned this Mar 19, 2024
@davelopez davelopez mentioned this issue Mar 19, 2024
Merged
6 tasks
@jdavcs
Copy link
Member

jdavcs commented Mar 21, 2024

Fixed in #17793

@jdavcs jdavcs closed this as completed Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@davelopez davelopez

Labels
area/backend kind/bug release-testing-24.0
Projects
None yet
Milestone
24.0
Development

No branches or pull requests
3 participants
@martenson @jdavcs @davelopez