-
-
Notifications
You must be signed in to change notification settings - Fork 17
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
- Status: Open.#349 In NodeDB-Lab/nodedb;
CRDT MERGE renders a policy denial as XX000
area:crdt-syncCRDT, edge-to-cloud syncCRDT, edge-to-cloud syncsev:3-mediumFeature wrong, but operational and a workaround existsFeature wrong, but operational and a workaround existstype:bugA defect — broken, incorrect, or lost dataA defect — broken, incorrect, or lost dataStatus: Open.#344 In NodeDB-Lab/nodedb;HTTP drops the shaping failure's class: allowlist 400, else 500; in-band lines carry no code
sev:3-mediumFeature wrong, but operational and a workaround existsFeature wrong, but operational and a workaround existstype:bugA defect — broken, incorrect, or lost dataA defect — broken, incorrect, or lost dataStatus: Open.#343 In NodeDB-Lab/nodedb;Calvin RETURNING swallows shaper errors; a failed row encode answers an ERROR tag
area:pgwirePostgreSQL wire protocol / client compatPostgreSQL wire protocol / client compatsev:2-highMajor functionality broken; no acceptable workaroundMajor functionality broken; no acceptable workaroundtype:bugA defect — broken, incorrect, or lost dataA defect — broken, incorrect, or lost dataStatus: Open.#342 In NodeDB-Lab/nodedb;Routed response-shaper errors flatten to XX000; the numeric SQLSTATE mapper covers 20 of 81 codes
status:in-progressActively being worked onActively being worked onStatus: Open.#338 In NodeDB-Lab/nodedb;pgwire extended protocol collapses duplicate output column names to one cell
area:pgwirePostgreSQL wire protocol / client compatPostgreSQL wire protocol / client compatsev:2-highMajor functionality broken; no acceptable workaroundMajor functionality broken; no acceptable workaroundstatus:in-progressActively being worked onActively being worked ontype:bugA defect — broken, incorrect, or lost dataA defect — broken, incorrect, or lost dataStatus: Open.#337 In NodeDB-Lab/nodedb;Timeseries aggregates drop what the native scan cannot express: ROLLUP/CUBE return count 0, HAVING and GROUP BY expressions are silently ignored, generic scans miss flushed partitions
area:sqlParser, planner, SQL semanticsParser, planner, SQL semanticsengine:timeseriesTimeseries engineTimeseries enginesev:3-mediumFeature wrong, but operational and a workaround existsFeature wrong, but operational and a workaround existsstatus:needs-triageAwaiting maintainer triage (severity + priority)Awaiting maintainer triage (severity + priority)type:bugA defect — broken, incorrect, or lost dataA defect — broken, incorrect, or lost dataStatus: Open.#333 In NodeDB-Lab/nodedb;SERIAL is accepted in FIELDS (...) and rejected in the parenthesised column list
area:sqlParser, planner, SQL semanticsParser, planner, SQL semanticspriority:P2Scheduled, not urgentScheduled, not urgentsev:4-lowMinimal impact / cosmeticMinimal impact / cosmetictype:bugA defect — broken, incorrect, or lost dataA defect — broken, incorrect, or lost dataStatus: Open.#319 In NodeDB-Lab/nodedb;A cross-field typeguard guard passes the DEFAULT gate at declaration and fails at every insert
area:sqlParser, planner, SQL semanticsParser, planner, SQL semanticssev:3-mediumFeature wrong, but operational and a workaround existsFeature wrong, but operational and a workaround existsstatus:needs-triageAwaiting maintainer triage (severity + priority)Awaiting maintainer triage (severity + priority)type:bugA defect — broken, incorrect, or lost dataA defect — broken, incorrect, or lost dataStatus: Open.#318 In NodeDB-Lab/nodedb;INSERT..SELECT with a kv-engine source silently NULLs expression cells
area:sqlParser, planner, SQL semanticsParser, planner, SQL semanticsengine:kvKey-Value engineKey-Value enginepriority:P2Scheduled, not urgentScheduled, not urgentsev:3-mediumFeature wrong, but operational and a workaround existsFeature wrong, but operational and a workaround existsstatus:confirmedReproduced by a maintainerReproduced by a maintainertype:bugA defect — broken, incorrect, or lost dataA defect — broken, incorrect, or lost dataStatus: Open.#311 In NodeDB-Lab/nodedb;ARRAY vector literal loses every element on document_strict INSERT, reported as 0 elements under XX000
area:sqlParser, planner, SQL semanticsParser, planner, SQL semanticsengine:documentDocument engine (schemaless + strict)Document engine (schemaless + strict)engine:vectorVector engineVector enginesev:3-mediumFeature wrong, but operational and a workaround existsFeature wrong, but operational and a workaround existstype:bugA defect — broken, incorrect, or lost dataA defect — broken, incorrect, or lost dataStatus: Open.#306 In NodeDB-Lab/nodedb;Multi-row INSERT emits one CommandComplete per row — drivers report rowcount 1; kv and timeseries DML answer a bare OK tag
area:pgwirePostgreSQL wire protocol / client compatPostgreSQL wire protocol / client compatpriority:P2Scheduled, not urgentScheduled, not urgentsev:3-mediumFeature wrong, but operational and a workaround existsFeature wrong, but operational and a workaround existsstatus:needs-triageAwaiting maintainer triage (severity + priority)Awaiting maintainer triage (severity + priority)type:bugA defect — broken, incorrect, or lost dataA defect — broken, incorrect, or lost dataStatus: Open.#297 In NodeDB-Lab/nodedb;