Delete final-round GCS compose inputs after successful uploads
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
Research direction
Read pkg/objectstorage/gcscompose.go, focusing on composeAll and putComposite and the final compose or single-input copy paths. Confirm how final intermediate inputs are tracked and how retries and errors are handled. Done means successful uploads remove the final .compose-* objects after the destination is committed without breaking cleanup on failure.
Written by the indexing model from the issue text.
Description
In pkg/objectstorage/gcscompose.go, composeAll deletes inputs after intermediate rounds, but it does not delete the final inputs after the final compose or single-input copy succeeds. For uploads with more than 32 parts (over 1 GiB at the current part size), final-round .compose-* objects can therefore remain in the bucket after a successful upload. putComposite's deferred cleanup only owns the original .part-* handles. Please clean up the final intermediate inputs after the destination is committed, while preserving retry/error handling.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 473
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 258
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from agent-substrate/substrate
-
[Bug]: e2e script flag parsing is brokenPossibly taken @ericcurtin claimed this today. Openarea/dev-infra area/tests kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
agent-substrate/substrate#2217 · 1 comment ·
Maintainers usually reply within 1 day
-
Reject trailing YAML documents in actor-template create manifestsPossibly taken @ericcurtin claimed this 3 days ago. Openarea/cli kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
agent-substrate/substrate#2156 · 1 comment ·
Maintainers usually reply within 1 day
-
area/storage kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
agent-substrate/substrate#2155 · 1 comment ·
Maintainers usually reply within 1 day
-
docs/api-guide.md: "an actor occupies its whole worker" contradicts multi-actor workersPossibly taken A pull request linked to this issue is open or already merged. Openarea/api kind/docs
Difficulty 1/5 Under an hour Newbie friendliness 88/100
agent-substrate/substrate#2152 ·
Maintainers usually reply within 1 day
-
area/gvisor area/node kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
agent-substrate/substrate#2035 ·
Maintainers usually reply within 1 day
All issues in agent-substrate/substrate
Similar issues
-
`renderLinkedIssues` overshoots its byte budget: unresolved and omitted lists are never boundedOpenagent-butler-finding agent-research-recommend bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
jordansmall/spindrift#4614 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
weaviate/weaviate-go-client#485 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
litmuschaos/litmus#5641 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day