feat: Log backend exit code#9581
Merged
Merged
Conversation
Owner
|
PR merged 👍 |
richiejp
force-pushed
the
feat/log-backend-exit-code
branch
from
c393d3a to
afee2ca
Compare
Signed-off-by: Richard Palethorpe <io@richiejp.com>
richiejp
force-pushed
the
feat/log-backend-exit-code
branch
from
e74d54e to
a16ba53
Compare
Collaborator
Author
|
OK, updated git module reference |
mudler
approved these changes
Apr 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Helps diagnose backend crashes when the backend log doesn't contain anything useful. This requires:
mudler/go-processmanager#4
AFAIK the process return code is already logged to a file, but we don't read it. Instead of reading the file
we can get the exit code more directly and without needing to watch for updates to the file.
Notes for Reviewers
Signed commits