queryEvidence keeps the five-second signal while the traversal signal moved to thirty

Open
#2,184 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, sql
Domain
databases

Research direction

Read hypaware-core/plugins-workspace/context-graph/src/query.js around queryEvidence and queryNeighbors, then review the traversal budget tests in test/plugins/context-graph-query.test.js:178-201. The issue is explicitly backlog-only until an evidence-lookup surface exists; when one is added, decide and test the budget on both sides, and update the recorded split if needed.

Written by the indexing model from the issue text.

Description

Source: #2180 at 074860a333b58dce2d6125ba6d83fca15bbbeb1c
Location: hypaware-core/plugins-workspace/context-graph/src/query.js:352
Severity: low

Evidence

At head 074860a3, queryEvidence arms AbortSignal.timeout(5000) at query.js:352 while queryNeighbors arms AbortSignal.timeout(30_000) at :143. The PR's rationale (sequential reads on cold or unindexed storage) applies to queryEvidence identically: it issues up to three sequential executeQuerySql reads over node/edge and then ai_gateway_messages/enrichment_committed, which are much larger tables.

Why deferral is safe

Safe outside this PR because the path is unreachable by users today: git grep for queryEvidence outside test/ returns only the function's own definition at query.js:349, and the plugin registers only the graph neighbors verb / graph_neighbors MCP tool (verb.js:22-28), so no user can hit the 5s abort. LLP 0428's blockquote at head now records the split as deliberate ('Evidence lookups keep the five-second signal'), so the corpus is coherent. Raising a budget on an unreached path is speculative consistency cleanup, not an observed misbehavior.

Acceptance condition

When an evidence-lookup surface (CLI verb or MCP tool) is added, decide the queryEvidence signal budget deliberately, cover it on both sides like the traversal budget tests at test/plugins/context-graph-query.test.js:178-201, and update the LLP 0428/0431 recorded split if the value changes.

Review preference; backlog only. A human may explicitly delegate it with neutral:fix.

Dominant language
JavaScript
Stars
11
Forks
0
Avg merge
2h 55m
Merged PRs (30d)
294

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hyparam/hypaware

All issues in hyparam/hypaware

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.