Fix rendering bug in security report generation due to PBA section #762
Conversation
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
Codecov Report
@@ Coverage Diff @@
## develop #762 +/- ##
========================================
Coverage 60.31% 60.31%
========================================
Files 161 161
Lines 4899 4899
========================================
Hits 2955 2955
Misses 1944 1944 Continue to review full report at Codecov.
|
ShayNehmad
approved these changes
Aug 5, 2020
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.
If the post-breach results have no changes, nothing is returned from
aggregateShellStartupPba()which causes a rendering issue (te replicate, try running only thetrapcommand PBA).This makes sure the results are returned back as it is if there are no changes.