The indexer publishes manifest-accepted and manifest-refused as events, without waiting for the stream's acknowledgement (issue 1966) #168

Merged

jschoubben merged 1 commits from fix/1966-indexer-event-refused into main 2026-11-07 19:58:28 +00:00

Conversation 1 Commits 1 Files Changed 2

+12 -10

1 Commits

Author	SHA1	Message	Date
jschoubben	71a56d4606	The indexer publishes manifest-accepted and manifest-refused as events, without waiting for the stream's acknowledgement (issue 1966) ... Both were published with the JetStream acknowledgement awaited, a request and response, for ten seconds each, and manifest-accepted once more on failure. On a bus refusing the subject (the old grants do not grant the new indexer mesh.seat.mesh-catalog.event.manifest-accepted) no acknowledgement ever came, so each judging pass took about twenty seconds a manifest and the indexer never reached the forge's messages nor the seat definitions: the take-in stood still. Now both are published plainly on their subject with the dedup id in Nats-Msg-Id, as an event is (the operator, 2026-11-07: everything is event-driven); the stream that keeps the subject drops a duplicate by its id, and a refusal is said on the connection's error handler, as the journal already shows. An error of the publish itself (no connection) still goes to the caller, which retries once and writes the unsaid finding. Quick vs thorough: thorough for these two events (every publish of a seat event by the indexer is now an event); sayTakeIn keeps its acknowledged publish, said in the issue for 47/G. Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i	2026-11-07 20:57:02 +01:00