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

Reject fractional maxResults in vector list operations

Closed
#1,571 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@ferhatelmas is already working on this.

Since Oct 23, 2026.

  • #1573 by @hsusul — merged

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
postgresql, typescript

Research direction

Read the /ListVectorBuckets and /ListIndexes request schemas and the route-level regression test described in the issue. Change both maxResults schemas from number to integer, then verify both routes reject 1.5 before invoking the vector store. An open linked pull request already addresses this issue.

Written by the indexing model from the issue text.

Description

Bug

The /ListVectorBuckets and /ListIndexes request schemas define maxResults as a JSON number. The validator therefore accepts fractional values such as 1.5, even though the S3 Vectors API defines this field as an integer in the range 1–500. The fractional page size is forwarded through the vector store and can fail when used for database pagination.

Expected behavior

Both operations should reject a fractional maxResults value as an invalid request before invoking the vector store.

Evidence

A direct route-level regression test sends maxResults: 1.5 to both endpoints. At current master, both requests pass validation and invoke the list handler. AWS documents maxResults as an integer for ListVectorBuckets and ListIndexes.

Scope

Change both request schemas from number to integer and retain regression coverage for both routes.

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

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.