simonsobs / simonsobs/librarian
Downstream transfers are left in INITIATED status when queues are failed
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- Avg merge
- 10d 21h
- Merged PRs (30d)
- 1
Description
Not sure why this is. Happens when we go over the 100-transfer globus limit.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the case where more than 100 transfers cause queues to fail, then trace the downstream transfer status handling. Done means downstream transfers are no longer left in INITIATED status after queue failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100