Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Respect zero for tenant vector resource limits

Open Beginner friendly
#1,589 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@hsusul is already working on this.

Since Oct 22, 2026.

  • #1594 by @hsusul — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
73/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
postgresql, typescript
Domain
backend, databases

Research direction

Read the multitenant plugin code that selects tenant limits and the VectorStoreManager enforcement path; the payload does not name their files or tests. Trace how a zero tenant limit is passed through while missing or null values use the global default. Done when zero rejects bucket or index creation and missing or null limits retain the global default.

Written by the indexing model from the issue text.

Description

Bug

In multitenant mode, setting a tenant's vector bucket or index limit to 0 does not disable creation. The plugin uses tenantLimit || globalLimit, so zero is replaced by the global limit before VectorStoreManager enforces it.

Reproduction

Configure features.vectorBuckets.maxBuckets as 0 (or maxIndexes as 0) for a tenant and keep the corresponding global limit above zero. Then create a vector bucket (or index). The request is allowed up to the global limit instead of being rejected at the tenant's zero limit.

The admin tenant schema accepts these finite numeric values, and the multitenant migration stores them as integer limits. VectorStoreManager already rejects creation when the current count is greater than or equal to its configured limit.

Expected

A tenant limit of zero should prevent creation. Missing or null limits should continue to use the global default.

Dominant language
TypeScript
Stars
1.3k
Forks
314
Avg merge
1d 12h
Merged PRs (30d)
88

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from supabase/storage

All issues in supabase/storage

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.