Bug: TablesDB listRows total:false uses a GET encoding that does not suppress totals in measured Cloud requests
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- nodejs, typescript
- Ambito
- api, backend-api-design
Direzione di ricerca
Start with the pinned src/client.ts source and the corresponding SDK Generator platform templates, then verify GET boolean parsing against a nonempty list; the report notes that an empty-table fixture is insufficient. Confirm the intended server contract before choosing whether the serializer, server parser, or both should change. Done means regression coverage for true, false, omission, query arrays, and POST-body behavior, while preserving JSON booleans and booleans inside serialized Query JSON.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Reproduction steps
With an isolated, frozen install of [email protected], run the following .mjs file with Node 26. It sends one HTTP GET to a local server and requires no Appwrite credentials or Cloud writes.
import { Client, TablesDB } from "node-appwrite";
import assert from "node:assert/strict";
import { createServer } from "node:http";
let observed;
const server = createServer((request, response) => {
observed = new URL(request.url, "http://fixture.invalid").searchParams.get("total");
response.writeHead(200, { "content-type": "application/json" });
response.end('{"total":0,"rows":[]}');
});
await new Promise(resolve => server.listen(0, "127.0.0.1", resolve));
try {
const client = new Client().setEndpoint(
`http://127.0.0.1:${server.address().port}/v1`,
).setProject("fixture-project");
await new TablesDB(client).listRows({
databaseId: "db",
tableId: "cost",
total: false,
});
console.log({ observed }); // { observed: 'false' }
assert.equal(observed, "false"); // Characterization, not the desired fix.
} finally {
server.closeAllConnections();
await new Promise(resolve => server.close(resolve));
}
Expected behavior
Passing total: false should suppress total counting on a nonempty list. The SDK and the server should agree on the GET boolean representation. In the measured Cloud boundary below, total=0 produced the intended response while total=false did not. Please confirm the intended server contract before deciding whether to fix the serializer, server parser, or both.
Actual behavior
The published SDK emits the string false in the GET URL. A separate, read-only Appwrite Cloud SGP probe queried an existing nonempty table with identical limit/order queries:
| GET flag | Response total | Rows returned |
|---|---|---|
total=false |
8 | 1 |
total=0 |
0 | 1 |
total=true |
8 | 1 |
total=1 |
8 | 1 |
The returned row hash matched between the false/zero variants. The behavior held with and without X-Appwrite-Response-Format: 2.3.0. No row was inserted or changed. An empty-table fixture alone cannot establish that counting was suppressed. This is a response/counting observation, not a measured billing or query-performance claim.
Environment and source pin
- Published dependency:
[email protected], exact frozen lock. - SDK tag
29.0.0resolves to commitf333acaff4fcc23956b6086a537c51c87123f40d: client source. - Fresh local replay: Windows, Node 26.10.0, pnpm 12.9.0. The real-SDK compatibility suite passed two tests, including raw string-false characterization and an explicit GET-total-only zero/one shim. The same pinned suite also passed Linux CI.
- Cloud measurement: SGP, captured October 2026. The Cloud engine version was not independently identified;
2.3.0above is the requested response-format header, not a claim about the deployed engine. - No claim that other SDK/server versions behave identically. Project IDs, credentials, private receipts and row content are excluded.
Suggested investigation and regression coverage
Please verify GET boolean parsing against a nonempty list and the corresponding SDK Generator platform templates. If zero/one serialization is required, preserve JSON request-body booleans and booleans inside serialized Query JSON. Cover true, false, omission, query arrays and POST-body behavior; make the desired-fix regression fail against the previous implementation first.
Our prototype uses an explicit local shim for the GET total flag. We have not patched the vendor package or migrated production Functions to the Node SDK. A general upstream change should be reviewed at the generator/server contract boundary rather than copying that narrow workaround.
Duplicate check
Searched open and closed sdk-for-node issues/PRs for total and false, and sdk-generator issues/PRs for total with false; no matching report was found at posting time. Only this report is being opened; no parallel issue is being filed in the generator repository.
- Lingua principale
- TypeScript
- Stelle
- 256
- Fork
- 45
- Merge medio
- 8h 59m
- PR unite (30g)
- 4
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di appwrite/sdk-for-node
-
bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 82/100
appwrite/sdk-for-node#132 · 2 commenti · 1 reazione ·
-
🐛 Bug Report: 22.1.0 causing errors on nextjs actions.Forse di nuovo libera @ChiragAgg5k l’ha presa 266 giorni fa e non c’è nessuna pull request aperta. Apertabug
appwrite/sdk-for-node#141 · 1 assegnatario ·
-
Node SDK: "createTable" does not create columnsForse di nuovo libera @ChiragAgg5k l’ha presa 266 giorni fa e non c’è nessuna pull request aperta. Aperta
appwrite/sdk-for-node#136 · 3 commenti · 1 assegnatario ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
appwrite/sdk-for-node#133 · 2 commenti · 1 reazione ·
Tutte le issue di appwrite/sdk-for-node
Issue simili
-
clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster maturity:stable P3
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
openclaw/openclaw#200937 · 1 commento · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
accepted bug needs-info triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
zts212653/clowder-ai#2025 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
letehaha/moneymatter#906 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
blinkospace/blinko#1287 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
Feyisara2108/stellargive#1379 ·
I maintainer di solito rispondono entro 1 giorno