Fix: Display signal names instead of exit codes in worker termination logs #3435
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix signal name display in worker termination logs
Previously, when a worker process was terminated by a signal like SIGABRT,the log would display "Worker (pid:X) was sent code 134!" instead of the actual signal name. This happened because the code incorrectly interpreted shell exit codes (128 + signal_number) as signal numbers.
Changes:
signal numbers from process exit status
(e.g., 134 = 128 + SIGABRT)
After this fix, the log correctly displays:
"Worker (pid:X) was sent SIGABRT!" instead of "Worker (pid:X) was sent code 134!"
Fixes signal name logging for all signals including SIGABRT, SIGKILL, SIGTERM, etc.
issue: #3434