fix: three things vm4006 said after the update #73

2026-09-15T21:32:00+02:00

mi commented

2026-09-15 21:32:00 +02:00

Processor time: a Docker build's work runs in containers below the
daemon, not below the docker run client Werkator started, so sampling
that tree measured the log relaying. An eight-minute build recorded
cpu=0 and the page would have read "used no processor". BuildRunner now
says whether its tree is the build's own, the dispatcher routes that
question the same way it routes start(), and an unmeasurable runtime
records nothing at all.

File names: artifacts went out under Spring's reflected-file-download
default, inline; filename=f.txt, so a build's jar was saved as f.txt.
The response now carries the artifact's own name — inline for what a
browser renders, attachment for the rest.

The unit: a stop sends SIGTERM and the JVM exits 143, which systemd was
journalling as Failed with result 'exit-code' — every clean stop, a
deployment's swap included, looked like a crash. SuccessExitStatus=143.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com

Processor time: a Docker build's work runs in containers below the daemon, not below the `docker run` client Werkator started, so sampling that tree measured the log relaying. An eight-minute build recorded cpu=0 and the page would have read "used no processor". BuildRunner now says whether its tree is the build's own, the dispatcher routes that question the same way it routes start(), and an unmeasurable runtime records nothing at all. File names: artifacts went out under Spring's reflected-file-download default, `inline; filename=f.txt`, so a build's jar was saved as f.txt. The response now carries the artifact's own name — inline for what a browser renders, attachment for the rest. The unit: a stop sends SIGTERM and the JVM exits 143, which systemd was journalling as `Failed with result 'exit-code'` — every clean stop, a deployment's swap included, looked like a crash. SuccessExitStatus=143. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

mi added 1 commit 2026-09-15 21:32:00 +02:00

fix: three things vm4006 said after the update

werkator build succeeded after 02:04

Details

fff1f94f7b

Processor time: a Docker build's work runs in containers below the
daemon, not below the `docker run` client Werkator started, so sampling
that tree measured the log relaying. An eight-minute build recorded
cpu=0 and the page would have read "used no processor". BuildRunner now
says whether its tree is the build's own, the dispatcher routes that
question the same way it routes start(), and an unmeasurable runtime
records nothing at all.

File names: artifacts went out under Spring's reflected-file-download
default, `inline; filename=f.txt`, so a build's jar was saved as f.txt.
The response now carries the artifact's own name — inline for what a
browser renders, attachment for the rest.

The unit: a stop sends SIGTERM and the JVM exits 143, which systemd was
journalling as `Failed with result 'exit-code'` — every clean stop, a
deployment's swap included, looked like a crash. SuccessExitStatus=143.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

mi merged commit 4a76e4afc4 into main

2026-09-15 21:32:04 +02:00

mi deleted branch three-bugfixes

2026-09-15 21:32:04 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: mi/werkator#73