galaxyproject / galaxyproject/galaxy
Short term storage expiration does not take into account "exporting time"
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 1.2k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 169
Description
When we export something using the `ShortTermStorageManager`, it will be deleted automatically after a fixed duration (usually 24h). However, in some cases, depending on the size of the data exported, the export process itself may take hours, and then the expiration will trigger shortly after.
To calculate the expiration time, we should probably use the "finalization time" instead of the "creation time" of the export.
Contributor guide
Research direction
Start by locating ShortTermStorageManager and the export finalization path. Trace how the expiration time is calculated, then verify that a long-running export remains available for the configured duration after finalization, including with a focused test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100