Handle unsigned int errorcodes more gracefully in Windows Batch #232
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.
We have a job on a Windows machine which executes a Matlab project within a batch-file, and has actually a quite high error code of
3221225477
. We are using the binary wrapper, and so this quite high number gets written into the text file. The parsing fails with anIOException
and the connection gets lost to the agent. I was first confused, but actually windows uses an unsigned int for the error codes, as documented here. I decided to set it to max integer, which is from my point of view better than throwing the exception, but I added a warning log message about it.Testing done
Added a unit test which reproduces the error and verifies that it is resolved like this.
Submitter checklist