-
Notifications
You must be signed in to change notification settings - Fork 967
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
ItemImmutableException: History is immutable #18146
Comments
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 |
Should be fixed in #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
The text was updated successfully, but these errors were encountered: