Skip to content

dbus: clarify PropExecStart uncleanIsFailure semantics - #526

Open
MsfPablo wants to merge 1 commit into
coreos:mainfrom
MsfPablo:fix/prop-exec-start-docs
Open

dbus: clarify PropExecStart uncleanIsFailure semantics#526
MsfPablo wants to merge 1 commit into
coreos:mainfrom
MsfPablo:fix/prop-exec-start-docs

Conversation

@MsfPablo

Copy link
Copy Markdown

Fixes #510

The PropExecStart argument uncleanIsFailure and the corresponding
execStart.UncleanIsFailure field are named after the negation of the
systemd property they map to: true means ignore unclean exits
(equivalent to prefixing the command with - in a unit file and to
systemd's arg_ignore_failure), while false (the default) treats
unclean exits as failures. Without explanation, users reasonably assume
the opposite, as flagged in #510.

This change only updates the doc-comments for the field and the function
so the inverted semantics are spelled out. The public API
(field name, argument name, dbus property name) is intentionally left
unchanged for backward compatibility — a rename would be a breaking
change to a documented public function with no deprecation path.

AI disclosure

This patch was authored with the assistance of an AI coding assistant
(Claude). I reviewed the change, ran gofmt, go vet, and go build ./dbus/... locally — all clean.

The argument and the corresponding field are named after the negation of
the systemd property they map to: true means *ignore* unclean exits, not
treat them as failures. Without explanation, users reasonably assume the
opposite, as flagged in issue coreos#510.

Clarify the doc-comments for both the field and the function so the
inverted semantics are spelled out, while keeping the public API
(field name, argument name, dbus property name) unchanged for backward
compatibility.

Fixes coreos#510
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PropExecStart argument uncleanIsFailure is named badly

1 participant