Flip task and stream name around in log output to reduce vertical shifts when looking through multiple log lines. #639
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
when looking through multiple log lines. For me, it's easier to figure out the stream name (ERR or OUT) when it always sits at the same place in the log line, like this: ``` 2025-02-13 08:48:29.933 [OUT govulncheck] Scanning your code and 1222 packages across 148 dependent modules for known vulnerabilities... 2025-02-13 08:48:29.933 [OUT govulncheck] 2025-02-13 08:48:29.933 [OUT govulncheck] Fetching vulnerabilities from the database... 2025-02-13 08:48:29.933 [OUT govulncheck] 2025-02-13 08:48:30.139 [OUT govulncheck] Checking the code against the vulnerabilities... 2025-02-13 08:48:30.139 [OUT govulncheck] 2025-02-13 08:48:30.141 [OUT anothertaskname] blablablabal 2025-02-13 08:48:30.141 [ERR anothertaskname] blablablabal 2025-02-13 08:48:30.139 [ERR govulncheck] oh no an error ``` This is how the output currently looks: ``` 2025-02-13 08:48:29.933 [govulncheck OUT] Scanning your code and 1222 packages across 148 dependent modules for known vulnerabilities... 2025-02-13 08:48:29.933 [govulncheck OUT] 2025-02-13 08:48:29.933 [govulncheck OUT] Fetching vulnerabilities from the database... 2025-02-13 08:48:29.933 [govulncheck OUT] 2025-02-13 08:48:30.139 [govulncheck OUT] Checking the code against the vulnerabilities... 2025-02-13 08:48:30.139 [govulncheck OUT] 2025-02-13 08:48:30.141 [anothertaskname OUT] blablablabal 2025-02-13 08:48:30.141 [anothertaskname ERR] blablablabal 2025-02-13 08:48:30.139 [govulncheck ERR] oh no an error ``` Signed-off-by: Josh Gwosdz <[email protected]>
erdii
changed the title
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #639 +/- ##
=======================================
Coverage 62.21% 62.21%
=======================================
Files 13 13
Lines 1003 1003
=======================================
Hits 624 624
Misses 340 340
Partials 39 39 ☔ View full report in Codecov by Sentry. |
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.
For me, it's easier to figure out the stream name (ERR or OUT) when it
always sits at the same place in the log line, like this:
This is how the output currently looks:
Signed-off-by: Josh Gwosdz [email protected]