mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-07-25 17:18:11 +00:00
A background queue drain (fromQueue: true) whose runtime binding was reaped by the gateway fires with sessionId=null. The expression options?.sessionId ?? activeSessionIdRef.current falls back to whichever runtime id the foreground happens to hold, landing the queued prompt in the session the user is currently viewing instead of the session that owns the queue entry — a cross-session message leak. Guard the fallback: only inherit the foreground runtime when the drain targets the current view (no storedSessionId, or it matches the foreground). A background drain (storedSessionId differs) is left with sessionId=null so the existing session.resume path rebinds the correct runtime before prompt.submit fires. Includes a regression test: "a fromQueue drain with null runtime id does NOT land in the foreground session (cross-session leak guard)". All 53 existing tests pass. |
||
|---|---|---|
| .. | ||
| emails | ||
| README.md | ||
Contributor email → GitHub login mappings
This directory replaces appending entries to AUTHOR_MAP in
scripts/release.py. The old dict caused constant merge conflicts when
several salvage PRs landed at once — every PR edited the same lines of the
same file. Here, each mapping is its own file, and file additions never
conflict.
Adding a mapping
One file per commit-author email, under emails/:
python3 scripts/add_contributor.py <email> <github-login>
# or by hand:
echo "<github-login>" > contributors/emails/<email>
- File name = the exact commit-author email (as shown by
git log --format='%ae'). - File content = the GitHub login on the first non-comment line.
Lines starting with
#are comments (use them for the PR reference).
Example — contributors/emails/jane.doe@example.com:
janedoe
# PR #12345 salvage (gateway: fix session key routing)
Rules
- Do NOT add new entries to
AUTHOR_MAPinscripts/release.py. That dict is frozen legacy data; the release tooling merges it with this directory (directory entries win on duplicates). - GitHub noreply emails (
<id>+<login>@users.noreply.github.comand<login>@users.noreply.github.com) auto-resolve — no file needed. - The
Contributor Attribution CheckCI job fails a PR whose commits carry an unmapped email; the failure message prints the exact command to run.