chore: release 0.12.3 - #71
Merged
Merged
Conversation
Two fixes, both from one incident on a live host. #68 — ensureDaemon launched `process.execPath`, which inside the omp binary is omp: a compiled Bun executable that ignores a script argument and boots an interactive session. So daemon.ts never ran from an omp host, and every spawn was a session that claimed a permanent Telegram topic and exited. 83 of them, five seconds apart, before the loop was broken by hand. The runtime is now resolved by name, the poll lock is read before spawning rather than discovered by spawning, and a daemon child cannot claim a topic at all. #61 — an inbound message now leaves a durable receipt, written before the handoff, so a supervising process can verify delivery without parsing another program's transcript. #67 — /cleanup can select: exact ids, or the crash-loop set identified by evidence (a recorded session file that never existed). Its old dead-pid-only predicate would have deleted eight days of unrelated history along with the spam, irreversibly, in a DM host. Also fixed on the way: registry claims were an unserialised read-modify-write through a shared temp file, so concurrent claims silently lost rows — and a lost row is a topic nothing can ever find again, because the registry is the only index that exists.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Patch release closing #61, #67 and #68 — all three open issues.
/cleanupcan select exact ids or the crash-loop setAlso in #69, found on the way: registry claims were an unserialised read-modify-write through a shared temp file, so concurrent claims silently lost rows — and a lost row is a topic nothing can ever find again, since the registry is the only index that exists.
Contents
Verified
Master is already deployed to the affected host and byte-identical to this branch's
src/. In the exact condition that produced 83 topics:Patch rather than minor at the maintainer's request, though #61 and #67 add surface (
last-inbound.json,/cleanup go <ids|never-ran>).After merge
npm whoamireturns 401 on the affected host, so publishing needs an operator credential: