Answer A-419 (release matched by the fingerprint's source) and A-420 (a message given up is said)
This commit is contained in:
@@ -1052,3 +1052,14 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
entry's artifact reference (`<module>:<artifact>`), the name the build step and the builder publish it under; the
|
||||
entry stays the one source of the name, and no `package` is added to it. A name that matches no entry is said in the
|
||||
builder's log with the entries looked at.
|
||||
- **A-419** (A-96, A-67; read from the code 2026-11-15: the assigner finds a trunk build's released version and parts by
|
||||
its module and the source revision of the kept assignment graph, so after any merge that does not rebuild a module,
|
||||
its wants and candidates carry no version and no parts; principles 2 and 7) A trunk build's release is matched by its
|
||||
module and the source revision its fingerprint was built at, read from its catalog entry's `fp-src`, which is
|
||||
`version-released.source` for that build; A-96's "matched to `version-released.source`" is read so. A want or a
|
||||
candidate whose entry's release is not heard says so, naming the module, the fingerprint and that source.
|
||||
- **A-420** (principle 3; the builder and the indexer hear their events with five deliveries, and the bus drops a message
|
||||
after the fifth without either saying so) On the last delivery its consumer allows, the builder and the indexer each
|
||||
say in their log that they give the message up, naming its subject, the artifact and version it carries, and the
|
||||
last refusal. (Quick fix, said: the same silence holds for every part that hears an event; the thorough fix is the
|
||||
SDK's hearing saying it once for every part, noted on the issue of the hand start.)
|
||||
|
||||
Reference in New Issue
Block a user