Self cleanup during publishing (prevent failure of large channels)
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 40
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
more than 90% of the space has been used. use --skip-space-check to ignore. Used: 92.9%
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 searching the repository for the quoted space-check message and trace the publishing path that emits it. Clarify the intended cleanup behavior and define a reproducible large-channel case; done means publishing no longer fails because of this space condition, with coverage for that case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100