← proxy_allocator · live sandbox

Who actually gets the proxy?

This runs the real allocator code — _do_acquire and _do_acquire_reservation from app/main.py — against an isolated in-memory database, side by side with a preserved copy of the pre-fix logic. Nothing here touches production leases or live Webshare inventory.

Scenario

Step

0 / 0

Free proxy

Leased — colored by holding state

Rotating session, shared by multiple states — by design

Collision — two states hold one exclusive proxy at once

▶ Add a custom step

Script your own sequence — both sides call the real allocator functions for every step you add.

Identity

Action

worker_id

state_code

proxy_type

Pools here are a small fixed sandbox inventory (3 datacenter, 3 static-residential, 2 rotating sessions × capacity 3), not live Webshare data — see app/simulate.py. Every acquire/release on the "Patched" side calls the exact functions the live /api/leases/* and /api/reservations/* routes use; the "Unpatched" side calls a preserved, byte-for-byte copy of the logic before the state/proxy_type check was added.