KofTwentyTwo/Jarvis
2
0 Fork 0
Code Issues 111 Pull Requests 16 Actions Packages Projects Releases 4 Wiki Activity

v1.1 F-Q-E: long-running query cancellation for Memory.searchFacts and Turn.listTurns #79

New Issue
Open
opened 2026-05-12 19:30:10 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-05-12 19:30:10 +00:00 (Migrated from github.com)
Copy link
Copy source

Summary

Add cancellation-on-disconnect semantics to `Memory.searchFacts` and `Turn.listTurns`. Currently bounded by `limit:` parameter only; long-running queries on large stores can't be interrupted when the client disconnects mid-request.

Evidence

  • Migration plan §10: `.planning/architecture/JARVIS-API-MIGRATION-PLAN.md:733` — "F-Q-E (long-running query cancellation) — Memory.searchFacts/Turn.listTurns gain cancellation-on-disconnect semantics. Currently bounded by limit: only."

Gap classification

"design-mapped but not built" — F-Q-E is an explicit v1.1 deferral in the API design open-questions table.

Recommended action

File against v1.1 milestone. Pattern: thread a `CancellationToken` (or Swift `Task` cancellation) through the SQLite query path; check on row-batch boundaries.

Cross-references

  • Migration plan §10 v1.1
  • API design v0.2 F-Q-E
## Summary Add cancellation-on-disconnect semantics to \`Memory.searchFacts\` and \`Turn.listTurns\`. Currently bounded by \`limit:\` parameter only; long-running queries on large stores can't be interrupted when the client disconnects mid-request. ## Evidence - Migration plan §10: \`.planning/architecture/JARVIS-API-MIGRATION-PLAN.md:733\` — \"F-Q-E (long-running query cancellation) — Memory.searchFacts/Turn.listTurns gain cancellation-on-disconnect semantics. Currently bounded by limit: only.\" ## Gap classification \"design-mapped but not built\" — F-Q-E is an explicit v1.1 deferral in the API design open-questions table. ## Recommended action File against v1.1 milestone. Pattern: thread a \`CancellationToken\` (or Swift \`Task\` cancellation) through the SQLite query path; check on row-batch boundaries. ## Cross-references - Migration plan §10 v1.1 - API design v0.2 F-Q-E
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
area:agent
area:build
area:bus
area:devtool
area:hud
area:logging
area:mcp
area:memory
area:vision
area:voice
audit-finding
bug
Something isn't working
 carry-forward
comment-cleanup
Comment / docstring cleanup per .planning/code-commenting-guide.md
 dependencies
Dependency updates
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 epic
good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 javascript
Pull requests that update javascript code
 migration
question
Further information is requested
 severity:critical
severity:high
severity:low
severity:medium
wontfix
This will not be worked on
No labels area:agent area:memory enhancement severity:low
Milestone
No items
No Milestone v1.1 — Backlog (Orpheus, WhisperKit, Voice Log, presence, advanced)
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/Jarvis#79