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

Fix Galaxy ignoring job object_store_id for quota check #19854

Merged
merged 4 commits into from
Mar 26, 2025

Conversation

bernt-matthias
Copy link
Contributor

@bernt-matthias bernt-matthias commented Mar 20, 2025

On my instance I noticed that (irrespective of object_store_always_respect_user_selection) quotas for object stores are ignored.

To me it seems that we ignored the job's object_store_id and only used an (undocumented?) object_store_id param
of job destinations. In the 2nd commit I completely remove destination parameter, because I think that the destination param should have been considered here (in both cases) already.

Opening against dev for better testing. We probably want to backport this?

xref #19589

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.

@github-actions github-actions bot added this to the 25.0 milestone Mar 20, 2025
@bernt-matthias
Copy link
Contributor Author

Hah, seems that I came up with the same solution as: #19589 .. minus the test :)

@mvdbeek
Copy link
Member

mvdbeek commented Mar 25, 2025

The test errors sure look related

seems that we ignored the job's object_store_id and
only used an (undocumented?) object_store_id param
of job destinations.
@mvdbeek mvdbeek merged commit 346ba3d into galaxyproject:dev Mar 26, 2025
52 of 55 checks passed
@mvdbeek
Copy link
Member

mvdbeek commented Mar 26, 2025

Thank you, that's much needed!

Copy link

This PR was merged without a "kind/" label, please correct.

@bernt-matthias bernt-matthias deleted the fix-is_over_quota branch March 26, 2025 09:35
@bernt-matthias
Copy link
Contributor Author

Should this be backported? I would suggest 24.1.

@mvdbeek
Copy link
Member

mvdbeek commented Mar 26, 2025

Really uncomfortable with that, maybe carry that patch if you want to test ?

@bernt-matthias
Copy link
Contributor Author

Really uncomfortable with that, maybe carry that patch if you want to test ?

Sure. I'm already doing this.

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.

3 participants