Skip to content

Distinguish not scheduled probes from erroneus not executed probes in report - #158

Open
XoMEX wants to merge 1 commit into
mainfrom
fix/distinguish-not-scheduled-vs-not-executed
Open

Distinguish not scheduled probes from erroneus not executed probes in report#158
XoMEX wants to merge 1 commit into
mainfrom
fix/distinguish-not-scheduled-vs-not-executed

Conversation

@XoMEX

@XoMEX XoMEX commented Aug 18, 2026

Copy link
Copy Markdown
Member

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.

Before this, if a probe was not scheduled, the scanner would print "not scheduled yet" in the final report.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants