Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Kill signal is not checked or logged hiding the actual cause of failure #48

Open
aalexgabi opened this issue Jan 18, 2022 · 0 comments
Open

Kill signal is not checked or logged hiding the actual cause of failure #48

aalexgabi opened this issue Jan 18, 2022 · 0 comments

Comments

@aalexgabi
Copy link

aalexgabi commented Jan 18, 2022 •
edited
Loading

If a process gets killed (by user or by the os due to reaching memory limit) the resulting error hides the actual cause:

`<command>` failed with code null

Currently in the code the signal is not checked nor logged in the exception making it very hard to track down the actual issue.
image

More info about the case in which code can be null here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aalexgabi