Skip to content

research: finalize #18 read-path + upstream pool audit - #94

Draft
Skywind5487 wants to merge 2 commits into
devfrom
research/39-read-ctx-upstream-audit
Draft

research: finalize #18 read-path + upstream pool audit#94
Skywind5487 wants to merge 2 commits into
devfrom
research/39-read-ctx-upstream-audit

Conversation

@Skywind5487

@Skywind5487 Skywind5487 commented Aug 16, 2026

Copy link
Copy Markdown
Owner

Research artifact

Canonical finding: docs/research/issue-39-read-ctx-upstream-audit.md

Refreshes the earlier #39 exploration against:

  • fork dev@fa5ed679cc6559c619038f327e6276f4b7e8d735
  • upstream NousResearch/hermes-agent@main@fc9cbc872d8050c22f1192b16bc5ff4aed471e10

Final research decision for #18

  1. Import the accepted bounded SessionDB read pool first, using the two preserved fix(state,desktop,runtime): EMFILE cascade — bounded WAL read pool, orphan serve reap, nofile floor NousResearch/hermes-agent#83406 contributor commits (9cc5c463…, then 5eaabc9e…) rather than the unrelated whole bundle.
  2. Then migrate only the remaining pure search/lookup projection reads; highest-value seam is get_compression_tip() because session listing/search already uses _read_ctx() and then re-enters the writer lock during compression-tip projection.
  3. Fix fork-only SessionDB(read_only=True) message-CJK serving parity without marking the read-only attach as a CJK rebuild worker.
  4. Add RED-first peak-pool, writer-lock convoy, real CJK serving, semantic-equivalence, and contention tests.

Upstream status reconciliation

Research-only PR. No #18 implementation code is included here.

Final recon: RECON FINAL @ fa5ed679…

Refs #18
Refs #39

@Skywind5487 Skywind5487 changed the title research: audit #39 read-only search paths and upstream cherry-picks research: finalize #18 read-path + upstream pool audit Aug 21, 2026
@github-actions

github-actions Bot commented Aug 21, 2026

Copy link
Copy Markdown

૮ >ﻌ< ა ci review

ran on c7dcd98 — research: refresh #18 read-path audit against current upstre

all good!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant