fix: progress messages leaking into --output files; bump to 0.6.3#5
Merged
Conversation
progress_cb was wired directly to console.print, the same recording console save_report() exports from. The "Probing <target>:<port> for PQC key exchange…" progress line was appended to the record buffer, so --output files started with that line before the actual report.
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
1 participant
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.
Summary
progress_cbwas wired directly toconsole.print, the same recording consolesave_report()exports from, so the "Probing : for PQC key exchange…" progress line was baked into--outputfiles before the actual report.Consoleinstead.Test plan
pytest— 252 passed, 100% coverageruff check quantumvalidator/— clean--output report.txtrun confirmed no leaked progress text