Answer A-422: the SDK's event hub binds the kept seat streams in its own start
This commit is contained in:
@@ -1068,3 +1068,11 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
entry with no `fp-src` is matched to the release whose parts' digests are the digests its fingerprint's `build.ended`
|
||||
made, as the assigner already hears it; an entry with `fp-src` is matched as A-419 says. An entry neither finds is
|
||||
said as A-419 says, with which of the two was tried.
|
||||
- **A-422** (A-397; live, the bus 2026-11-15 03:45: the indexer, the assigner, the checker, the teller, the forge bridge,
|
||||
the view, distribution and nats each have a durable on a kept seat stream their manifest consumes that was never
|
||||
delivered, since only the builder binds its kept streams; the indexer never heard a package-published; principles 1,
|
||||
3 and 7) The SDK's event hub binds a part's kept seat streams in its own start, after the stream `EVENTS`, so every
|
||||
part hears each kept event its manifest consumes on its own durable there, as A-397 says, with no call of its own;
|
||||
a stream it cannot bind is said in its log and its start goes on. The replay of what waited is heard as any event;
|
||||
a part whose handler cannot take its backlog is a finding of the change, read before its delivery. (Thorough fix,
|
||||
said: the indexer's own call, b0242f68, is the quick fix placed meanwhile.)
|
||||
|
||||
Reference in New Issue
Block a user