Conversation
dipu-bd
force-pushed
the
claude/tor-rotation-scheduling-venf7r
branch
from
August 4, 2026 09:45
1892e8d to
535d271
Compare
- EXIT_TTL (default 3h) queues an instance for a new circuit once it has held one exit identity that long, which is the only thing that pre-empts a site quietly scoring an IP: an exit that is unwelcome rather than broken never reaches the failure ladder, so the instance keeps it indefinitely. - A queued instance rotates only when no session is pinned to it, active or idle. The clock must not change the exit IP under a caller that asked to be sticky, so EXIT_TTL is a floor on an identity's age and SESSION_TTL is what frees an abandoned instance. - One rotation per tick, and none while a pool-wide sweep runs: instances all start their clocks together at boot, so a batch is exactly what a naive sweep would do on the first tick past the TTL. - The clock restarts in endRotation, whether the rotation succeeded or not, so an attempt against a wedged control port waits another EXIT_TTL rather than retrying every tick. Restarts reset it separately, having handed back an identity the clock was not measuring. - Instances report rotate_pending, and the dashboard tags them "rotate queued", so a queue held up by its sessions explains itself.
dipu-bd
force-pushed
the
claude/tor-rotation-scheduling-venf7r
branch
from
August 4, 2026 10:00
535d271 to
31f2821
Compare
This branch has not been deployed
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
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.
held one exit identity that long, which is the only thing that pre-empts a
site quietly scoring an IP: an exit that is unwelcome rather than broken
never reaches the failure ladder, so the instance keeps it indefinitely.
idle. The clock must not change the exit IP under a caller that asked to be
sticky, so EXIT_TTL is a floor on an identity's age and SESSION_TTL is what
frees an abandoned instance.
start their clocks together at boot, so a batch is exactly what a naive
sweep would do on the first tick past the TTL.
an attempt against a wedged control port waits another EXIT_TTL rather than
retrying every tick. Restarts reset it separately, having handed back an
identity the clock was not measuring.
queued", so a queue held up by its sessions explains itself.