The background daemon now records why it refused a queued dispatch file.
What's wrong with this entry?
The background daemon records a specific reason when it refuses a queued dispatch file, so failures are distinguishable instead of silent.
- Reasons:
bad_name,not_a_file,oversized,read_failed,stale,schema,bad_json,transform_throw,symlink. - A shared helper logs
[bg-dispatch] rejected …and emitstengu_bg_dispatch_rejectedwith a truncated reason. - A newer storage path reads dispatches with a byte cap and deletes the entry once handed off.
daemon_bg_dispatch_ingest
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
Daemon lock can now live in the v5 storage backend
Both mention daemon
-
v2.1.246
Background daemon start failures are classified, and a sleeping machine gets one retry
Both mention daemon
-
v2.1.248
Background daemon can retire a same-version instance
Both mention daemon