-
-
Notifications
You must be signed in to change notification settings - Fork 14
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
Sync sessions have no observability for Loro known-part trims — peer-id collisions discard writes with Applied acks and green counters
area:crdt-syncCRDT, edge-to-cloud syncCRDT, edge-to-cloud synctype:featureNew capability or behavior changeNew capability or behavior changeStatus: Open.#214 In NodeDB-Lab/nodedb;CREATE VECTOR INDEX ignores unrecognized option tokens and accepts DIM 0, creating an index that never matches
area:sqlParser, planner, SQL semanticsParser, planner, SQL semanticsengine:vectorVector engineVector enginepriority:P1Fix in the current milestoneFix in the current milestonesev: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.#213 In NodeDB-Lab/nodedb;SEARCH rejects a quoted collection name while accepting a quoted column argument
area:sqlParser, planner, SQL semanticsParser, planner, SQL semanticsengine:vectorVector engineVector enginepriority:P3Backlog / somedayBacklog / somedaysev: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.#212 In NodeDB-Lab/nodedb;SEARCH ... USING VECTOR() cannot be used as a derived table or IN-predicate subquery
area:sqlParser, planner, SQL semanticsParser, planner, SQL semanticsengine:vectorVector engineVector enginepriority:P2Scheduled, not urgentScheduled, not urgentsev:3-mediumFeature wrong, but operational and a workaround existsFeature wrong, but operational and a workaround existstype:featureNew capability or behavior changeNew capability or behavior changeStatus: Open.#211 In NodeDB-Lab/nodedb;Spatial accessors ST_AsText / ST_X / ST_Y return empty and ST_DWithin rejects ST_GeomFromText arguments
area:sqlParser, planner, SQL semanticsParser, planner, SQL semanticsengine:spatialSpatial engineSpatial enginepriority:P1Fix in the current milestoneFix in the current milestonesev: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.#210 In NodeDB-Lab/nodedb;Sync listener address is hardcoded (0.0.0.0:9090); bind failure is non-fatal so a second instance runs silently without sync
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.#209 In NodeDB-Lab/nodedb;Origin sync: interleaved KV deferred-flush delta silently halts document materialization (rejected=0, silent_dropped=0)
area:crdt-syncCRDT, edge-to-cloud syncCRDT, edge-to-cloud syncengine:documentDocument engine (schemaless + strict)Document engine (schemaless + strict)sev: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.#208 In NodeDB-Lab/nodedb;[Epic] P6 — Conformance Matrix + Chaos/Crash-Recovery Suite (v0.9)
area:pgwirePostgreSQL wire protocol / client compatPostgreSQL wire protocol / client compattype:epicTracking issue spanning multiple sub-issuesTracking issue spanning multiple sub-issuesStatus: Open.#168 In NodeDB-Lab/nodedb;[Epic] P4 — Multi-Tenant Isolation & Resource Governance (v0.8)
area:memoryMemory governance, arenas, budgetsMemory governance, arenas, budgetstype:epicTracking issue spanning multiple sub-issuesTracking issue spanning multiple sub-issuesStatus: Open.#167 In NodeDB-Lab/nodedb;[Epic] P3 — Backup, Restore & PITR (v0.7)
area:storage-walWAL, durability, flush/replayWAL, durability, flush/replaytype:epicTracking issue spanning multiple sub-issuesTracking issue spanning multiple sub-issuesStatus: Open.#166 In NodeDB-Lab/nodedb;[Epic] P2 — Cluster Consensus Safety (v0.6)
area:cluster-raftRaft, replication, consensus safetyRaft, replication, consensus safetytype:epicTracking issue spanning multiple sub-issuesTracking issue spanning multiple sub-issuesStatus: Open.#165 In NodeDB-Lab/nodedb;[Epic] P1 — Durability Correctness & Crash Safety (v0.5)
area:storage-walWAL, durability, flush/replayWAL, durability, flush/replaytype:epicTracking issue spanning multiple sub-issuesTracking issue spanning multiple sub-issuesStatus: Open.#164 In NodeDB-Lab/nodedb;