Treat continue-mode hits as successful at iteration limit#16
Open
gorizontniy wants to merge 1 commit into
Open
Treat continue-mode hits as successful at iteration limit#16gorizontniy wants to merge 1 commit into
gorizontniy wants to merge 1 commit into
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
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
max_iterations=1Why
A real run found and kept a target IP, sent Telegram, and protected the success cloud/folder. Because
continue_after_success=trueand the old runtime hadmax_iterations=1, the loop ended afterward and incorrectly returned code 2 withNo requested IP reserved after max_iterations=1.Tests
python -m unittest .\bin\test_yc_ip_hunter.py -vpython -m unittest discover -s .\bin -p "test_*.py" -vgit diff --checkLive-mode risk
This changes live-run exit status only after at least one target IP has already been reserved in the current run. It does not allocate extra resources by itself; it prevents successful bounded collection runs from being marked as failed.