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

External ObjectStores provided by the user are taken into account into the default quota #19320

Open
davelopez opened this issue Dec 12, 2024 · 0 comments

Comments

@davelopez
Copy link
Contributor

Found by a user and reported by @wm75

Galaxy Version and/or server at which you observed the bug
Galaxy Version: 24.1
Commit: (run git rev-parse HEAD if you run this Galaxy server)

Browser and Operating System
Operating System: Windows, Linux, macOS
Browser: Firefox, Chrome, Chrome-based, Safari

To Reproduce
Steps to reproduce the behavior:

  1. Add a user object store from a template in User -> Preferences -> Manage Your Storage Locations
  2. Change the default storage location for your history
  3. Upload a file to the history
  4. Check that your default disk quota gets increased

Expected behavior
The default quota should not be affected by external storage provided by the user

Screenshots

Here is a single history with a single file stored in an S3 bucket that fills the user quota.

image

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant