EPMRPP-77905 || preparation to highlight error log #3249
Merged
Conversation
This file contains 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
chivekrodis
force-pushed
the
EPMRPP-77905_highlighting_flow_for_error_log
branch
from
25ce15e to
5b8acff
Compare
Vadim73i
reviewed
Aug 31, 2022
Vadim73i
approved these changes
Aug 31, 2022
chivekrodis
added a commit
that referenced
this pull request
Sep 26, 2022
* EPMRPP-77905 || preparation to highlight error log * EPMRPP-77905 || code review fixes - 1 (cherry picked from commit eac3575)
chivekrodis
added a commit
that referenced
this pull request
Sep 26, 2022
* EPMRPP-77905 || preparation to highlight error log * EPMRPP-77905 || code review fixes - 1 (cherry picked from commit eac3575)
AmsterGet
pushed a commit
that referenced
this pull request
Oct 19, 2022
* EPMRPP-77905 || preparation to highlight error log * EPMRPP-77905 || code review fixes - 1 (cherry picked from commit eac3575)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
system get first error log id from stacktrace request
if error log inside nested step operator should expand nested step manually