Design 47 H: lead answers H-A-114 and H-A-115 (a held take-in is acknowledged and kept; code dependents by go.sum) #783
@@ -487,3 +487,12 @@ Where two preparers disagreed, the chosen one is named.
|
||||
is still readable, P4). (2) §752 and ADR 0682 §10 mean every verb of every seat: the grants part grants each module's
|
||||
account every seat's verbs, not only the seats its manifest invokes (acceptance test 118's case); that change is this
|
||||
developer's, in the same pass. P6.
|
||||
- **H-A-114 (indexer developer, 04:40; a held take-in across a restart)** A held take-in is acknowledged on the bus and
|
||||
kept only in the indexer's state `held` (H-A-97); the indexer takes the held ones in again from that state on its own
|
||||
`room` and at its start. No message stays unacknowledged, so the consumer's acknowledgement wait bounds nothing and a
|
||||
restart loses nothing; H-A-12's and H-A-50's "held, unacknowledged" are read so. P3 (a stuck message for the length of
|
||||
the acknowledgement wait would be a silent failure), P2.
|
||||
- **H-A-115 (indexer developer, 04:40; the movers' code dependents)** In H1 a code dependent of a mover is a module
|
||||
whose Go module requires the mover's (the go.sum reading built), which moves a module that requires the package
|
||||
without importing a changed package; the finer reading by imported package is H2's refinement of the same line
|
||||
(§743, A-476a). P7 for H1, said.
|
||||
|
||||
Reference in New Issue
Block a user