novox/hq issue 163. After every apply the host asks whether a newer host is delivered than the one running — and asked with the link-time stamp, which every delivered host carries as development build now that the version comes from where the binary sits.
So a delivered host never matched the newest delivered version: it stood aside on every push, and because standing aside cancels the report, the mesh never heard from it again. Measured on two machines: each push logged host <v> is delivered; standing aside for the version already running, then applied, and could not tell the mesh: reporting: context canceled. A machine restarting its host on every push and reporting nothing, reading as healthy.
Asked with the running version now — the other half of the 0142 change.
make check clean.
novox/hq issue 163. After every apply the host asks whether a newer host is delivered than the one running — and asked with the **link-time stamp**, which every delivered host carries as `development build` now that the version comes from where the binary sits.
So a delivered host never matched the newest delivered version: it stood aside on **every** push, and because standing aside cancels the report, the mesh never heard from it again. Measured on two machines: each push logged `host <v> is delivered; standing aside` for the version already running, then `applied, and could not tell the mesh: reporting: context canceled`. A machine restarting its host on every push and reporting nothing, reading as healthy.
Asked with the running version now — the other half of the 0142 change.
`make check` clean.
novox/hq 04-ISSUES/163. The host asks after every apply whether a newer
host is delivered than the one running, and asked with the link-time
version stamp — which every delivered host carries as "development
build", because the version comes from where the binary sits now (0142).
So a delivered host never matched the newest delivered version, stood
aside on every push for ever, and because standing aside cancels the
report, the mesh never heard from it again.
Measured on two machines: each push produced "host <v> is delivered;
standing aside" for the version already running, then "applied, and could
not tell the mesh: reporting: context canceled". A machine restarting its
host on every push and reporting nothing, reading as healthy.
Asked with the running version now. Half of 0142 was applied to the
report and the known-good record and not here; this is the other half.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
novox/hq issue 163. After every apply the host asks whether a newer host is delivered than the one running — and asked with the link-time stamp, which every delivered host carries as
development buildnow that the version comes from where the binary sits.So a delivered host never matched the newest delivered version: it stood aside on every push, and because standing aside cancels the report, the mesh never heard from it again. Measured on two machines: each push logged
host <v> is delivered; standing asidefor the version already running, thenapplied, and could not tell the mesh: reporting: context canceled. A machine restarting its host on every push and reporting nothing, reading as healthy.Asked with the running version now — the other half of the 0142 change.
make checkclean.