Update status code error message to adopt standardized conventions (i.e. toolset + code defined).#596
Merged
Merged
Conversation
….e. toolset + code defined).
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
1 participant
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.
There is a possibility that multiple toolsets will emit status codes as part of the execution of Virtual Client as a runtime platform. This change is meant to help standardize the format of the status code message for upstream execution/orchestration systems so that both the toolset emitting the status code as well as the status code itself can be parsed from the standard error.
e.g.
Status Code: Toolkit SDK = 200000 <--- ToolsetError in the Toolkit SDK script.
Status Code: Virtual Client = 211527 <--- ToolsetError with fail/fast in Virtual Client caused by the Toolkit SDK script failure.