codesandbox / codesandbox/codesandbox-client
Bug in storage management leads to reaching quota
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
🐛 bug report
Preflight Checklist
- I have read the Contributing Guidelines for this project.
- I agree to follow the Code of Conduct that this project
adheres to. - I have searched the issue tracker for an issue that matches the one I want
to file, without success.
Description of the problem
I am constantly reaching quota, and there's no easy way to proceeed. When i upload files and delete them, for instance changing an image or a model, i would expect codesandbox to not count the old stuff but still i reach quota just by repeatedly uploading new versions (and deleting the old of course).
I see dozens of instances in my storage management panel, csb seems to not be aware that many of them are the same file (should it share files across boxes even? that would be nice!) and i start to think that deleting anything (by clicking the x) doesn't actually delete:
scene.glb
scene.glb
scene.glb
scene.glb
scene.glb
scene.glb
...
so also makes it hard to fix, i could be deleting a file that was vital. overall right now i have no idea what to do. i'm blocked, can't upload anything. and again it happened just by re-iterating on a model that i kept refining and deleting.
my account: https://codesandbox.io/u/drcmda
ps. CSB maintainer were so nice to give me 1000mb storage already, it happened at 500mb, and countless of other times since then. but since i do delete it leads me to believe there must be a bug in storage.
Contributor 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.
Research direction
No implementation file, test, or entry point is identified. Start by reproducing the quota increase after uploading and deleting successive versions, then inspect the storage-management flow and its deletion records. Done means deleted files no longer count toward quota and the storage panel accurately represents remaining files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100