Expand description
Continuation chains (issue #231): a launch with --continues <id> stores
the UUID it continues, so a supervisor that relaunches fresh instead of
--resume-ing in place can still treat every execution of one task as a
whole. --status prints the chain and --upload-log uploads one file with
every execution of it, oldest first.
Structs§
- Chain
Log - A temporary combined log, removed when dropped.
Functions§
- build_
chain - Records of the chain
recordbelongs to, oldest first. Backward links come fromcontinues; forward, the most recently started record that continues the current one is followed. Cycles stop the walk. - identity_
text_ lines - Text-format lines for the identity fields of a status record.
- prepare_
chain_ upload - Combined log
--upload-loguploads forrecordwhen it belongs to a chain of more than one execution;Nonefor a single execution. - resolve_
continues - Resolve
--continues <id>for a new launch to the UUID it stores. - status_
identity - Fields
--statusreports right afteruuid: the names the execution answers to (aliases, once--alias/--renamegave it one) and its continuationchain, when it has more than one member. - write_
chain_ log - Concatenate the logs of a chain into one temporary file, oldest first,
each preceded by a lifecycle header in the format
--resumewrites.