Preserve an explicit zero tenant file size limit on update
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- postgresql, typescript
Research direction
Find the admin PUT /tenants/:tenantId route and inspect how it adds fileSizeLimit to the tenant update. Preserve an explicitly supplied zero while omitting the field only when it is absent. Confirm the stored limit becomes zero after updating a tenant that had a positive limit.
Written by the indexing model from the issue text.
Description
Bug
The admin PUT /tenants/:tenantId route silently ignores fileSizeLimit: 0. Its schema accepts any finite number, the tenant column is a non-null bigint, and the file-size limit calculation treats zero as a real upper bound. But the route only copies the value into the update when if (fileSizeLimit) is truthy.
Reproduction
Create a tenant with a positive file-size limit, then update it with fileSizeLimit: 0. The request succeeds, but the stored limit remains unchanged.
Expected
Persist an explicitly supplied zero limit. Omit the database field only when fileSizeLimit is absent.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 314
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 88
Getting set up
- Ships a Dockerfile or Docker Compose file
- No 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 supabase/storage
-
Validate tenant integer limits as integersPossibly taken @hsusul claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Respect zero for tenant vector resource limitsPossibly taken @hsusul claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
S3 HEAD/GET overwrite case-insensitive user metadata collisionsPossibly taken @ferhatelmas claimed this 16 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
supabase/storage#1461 · 1 assignee ·
Maintainers usually reply within 1 day
-
The sample application in storage article points to wrong URLMay be free again @prasadf18 claimed this 196 days ago, and no pull request is open. Opendocumentation
Difficulty 1/5 Under an hour Newbie friendliness 62/100
supabase/storage#557 · 1 comment ·
Maintainers usually reply within 1 day
-
Reject fractional maxResults in vector list operationsPossibly taken @hsusul claimed this 3 days ago. Open
Difficulty 1/5 1-3 hours Newbie friendliness 35/100
Maintainers usually reply within 1 day
All issues in supabase/storage
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
lyswhut/lx-music-desktop#3026 ·
-
area: ci type: test
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
schlessera/brain-kit#2769 ·
Maintainers usually reply within 1 day
-
Read a vector index's quantization back on Neo4j 2026.10, which reports vector.quantization.typeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
liberation-data/drivine#231 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
alveusgg/alveusgg#2502 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day