Distinguish not scheduled probes from erroneus not executed probes in report - #158
Merged
Merged
Conversation
The report is now prefilled with `NOT_EXECUTED_YET` for all scheduled probes. All other properties results return `NOT_SCHEDULED`. `NOT_EXECUTED_YET` is now considered an internal error if it persists until the report is done.
mradoy99
approved these changes
Aug 20, 2026
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
2 participants
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.
The report is now prefilled with
NOT_EXECUTED_YETfor all scheduled probes. All other properties results returnNOT_SCHEDULED.NOT_EXECUTED_YETis now considered an internal error if it persists until the report is done.Before this, if a probe was not scheduled, the scanner would print "not scheduled yet" in the final report.