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

[24.0] Add require_default_history route argument #17755

Draft
wants to merge 3 commits into
base: release_24.0
Choose a base branch
from

Conversation

mvdbeek
Copy link
Member

@mvdbeek mvdbeek commented Mar 15, 2024

Fixes #17703. The strategy introduced in #17657 started failing when applied to 24.0, since /api/users/current was ported to FastAPI and so didn't result in the creation of a history. The effect of this was that if you didn't have a session cookie your first visit would fail to load the history panel.

Going forward I think this is a nice way to provide resources conditionally per endpoint, instead of setting up everything in trans, whether it is needed or not for a given route.

How to test the changes?

(Select all options that apply)

  • I've included appropriate automated tests.
  • This is a refactoring of components with existing test coverage.
  • Instructions for manual testing are as follows:
    1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

  • I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

@mvdbeek mvdbeek marked this pull request as draft March 16, 2024 16:28
mvdbeek added a commit to mvdbeek/galaxy that referenced this pull request Mar 16, 2024
This is probably the simplest way to fix the anon user issue.
If we don't have a history the size is 0, that's fairly simple.

We might still want to do galaxyproject#17755
for those FastAPI endpoints that do actually require a default history.
@jdavcs jdavcs modified the milestones: 24.1, 24.0 Mar 19, 2024
@mvdbeek mvdbeek removed this from the 24.0 milestone Mar 19, 2024
@jdavcs jdavcs added this to the 24.1 milestone May 23, 2024
@jdavcs jdavcs removed this from the 24.1 milestone Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants