feat: implement configurable post-stop actions for stop conditions#81
Merged
takitsu21 merged 13 commits intotakitsu21:mainfrom Mar 23, 2026
Merged
Conversation
theguy000
force-pushed
the
feat/configurable-stop-behavior
branch
from
9304384 to
fa44123
Compare
takitsu21
requested changes
Mar 21, 2026
Owner
takitsu21
left a comment
takitsu21
left a comment
There was a problem hiding this comment.
Hello,
The idle state does not work I have just tested it and it keeps uploading even after a condition is met if you can check please.
Maybe we should rename the Stop seeding to Stop because maybe the user is only leeching (rare but possible) and same for Continue seeding (Idle) => Continue (Idle) .
Thanks for your contributions !
When stop conditions are met (ratio, upload, download, or time), users can now choose the post-stop action: continue seeding (idle), stop seeding completely, or automatically delete the instance. The backend tracks stop_condition_met state and executes the chosen action. On the frontend, a new Settings dropdown appears in stop condition settings when any threshold is configured, allowing selection of the desired behavior. This works seamlessly across web UI, CLI, and desktop applications.
This reverts commit 514896f.
…ditions Change stop condition checks (ratio, uploaded, downloaded) to compare against cumulative values across all sessions rather than session-only values. This fixes the stop condition not working as intended.
theguy000
force-pushed
the
feat/configurable-stop-behavior
branch
from
1c2c917 to
6212c10
Compare
Contributor
Author
|
Note: When resuming a stopped instance, there will be a brief moment of upload (one tick) before it recognizes the stop condition and stops again. This is expected and the amount is negligible. Same goes for when the stop condition is met while the instance is running. |
takitsu21
approved these changes
Mar 23, 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.
When stop conditions are met (ratio, upload, download, or time), users can now choose the post-stop action:
-automatically delete the instance.
The backend tracks stop_condition_met state and executes the chosen action. On the frontend, a new Settings dropdown appears in stop condition settings when any threshold is configured, allowing selection of the desired behavior. This works seamlessly across web UI, CLI, and desktop applications.