Closed galaxyproject-sentryintegration[bot] closed 1 day ago
And maybe we should do this via the API ?
I'm happy to move this to the API as a FastAPI endpoint. But it wouldn't be correct to target 24.0 for the fixes or is it still ok?
I thought we can do with the API already, but I guess just on a single history basis. Yeah, new API is not for 24.0.
OK, thanks! I will then do the minimal fixes in the existing client controller for 24.0
and follow up on dev
(after merge) replacing it with the new API :+1:
Should be fixed in https://github.com/galaxyproject/galaxy/pull/18200
This might not actually be a bug, but there is probably a usability issue here. You can make all your histories private, and I think that should probably also work for archived and purged histories ? Alternatively we should probably not fail hard here as soon as a single history can't be made private ?
The other issue is that the controller method appears to not turn MessageExceptions into a regular 400 style response. And maybe we should do this via the API ?
Sentry Issue: GALAXY-MAIN-SGB