chroma-core/chroma · error · ChromaValueError

transactional filter reads require a positive limit

Error message

transactional filter reads require a positive limit

What it means

Error "transactional filter reads require a positive limit" thrown in chroma-core/chroma.

Source

Thrown at clients/new-js/packages/chromadb/src/collection.ts:1619

    if (this.readToken === null) {
      this.readToken = readToken;
    }
  }

  private validateGetRequest(request: ConditionalGetRequestPayload): void {
    const ids = request.ids ?? undefined;
    if (ids) {
      for (const id of ids) {
        if (this.bufferedWriteIds.has(id)) {
          throw this.invalidReadAfterWrite(id);
        }
      }
      return;
    }

    const limit = request.limit ?? undefined;
    if (!Number.isInteger(limit) || (limit as number) <= 0) {
      throw new ChromaValueError(
        "transactional filter reads require a positive limit",
      );
    }
  }

  private validateReadToken(
    expectedReadToken: number | null,
    actualReadToken: number | null | undefined,
  ): void {
    if (actualReadToken === null || actualReadToken === undefined) {
      throw new ChromaValueError(
        "transactional get response did not include an OCC read token",
      );
    }
    if (!Number.isSafeInteger(actualReadToken) || actualReadToken < 0) {
      throw new ChromaValueError(
        `transactional read token offset ${actualReadToken} is not a safe integer`,
      );

View on GitHub (pinned to aecdd12c8a)

When it happens

Trigger: Thrown at clients/new-js/packages/chromadb/src/collection.ts:1619 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of chroma-core/chroma@aecdd12c8a (2026-08-16). Data as JSON: /api/errors/03a7c7d2b297aad6. Report an issue: GitHub.