promote(emex): Floxy residential primary transport #125

root · 2026-06-10T22:24:19+03:00

root commented

2026-06-10 22:24:19 +03:00

Cherry-pick of dev ef4ab9b (63908b1). Moves EMEX egress (fetchEmexHtml HTTP + EmexBrowserService chromium) off DataImpulse-first onto Floxy residential sticky primary. Fixes the demonstrated 25s budget-burn where a Ford VIN ate the budget on dead DataImpulse ports before reaching Floxy. Dev-validated: 6 EMEX-via-Floxy successes, 0 DataImpulse retries, 0 budget aborts; Ford VIN now 201 (was 400). Rollback: EMEX_PROXY_PROVIDER=dataimpulse.

Cherry-pick of dev ef4ab9b (63908b1). Moves EMEX egress (fetchEmexHtml HTTP + EmexBrowserService chromium) off DataImpulse-first onto Floxy residential sticky primary. Fixes the demonstrated 25s budget-burn where a Ford VIN ate the budget on dead DataImpulse ports before reaching Floxy. Dev-validated: 6 EMEX-via-Floxy successes, 0 DataImpulse retries, 0 budget aborts; Ford VIN now 201 (was 400). Rollback: EMEX_PROXY_PROVIDER=dataimpulse.

root added 1 commit 2026-06-10 22:24:19 +03:00

perf(emex): Floxy residential primary transport (was DataImpulse-first)

QA Gate (P0/P1) / Test affected app (pull_request) Has been cancelled

Details

63908b1fca

EMEX egress was DataImpulse-first: fetchEmexHtml tried 3 dead-prone DataImpulse
ports before falling to the Floxy fallback, and the browser scraper launched on a
random DataImpulse port. With ~50% of DataImpulse ports dead, this burned the 25s
decode budget before reaching Floxy (observed: a Ford VIN where pcat correctly
returned null fast, then EMEX's DataImpulse retries ate the budget).

ssd tokens are replayed from emex's own HTML and are NOT strictly IP-bound on the
.aspx endpoints (the prior random-port-per-call primary proved that), so a sticky
Floxy IP across the flow is strictly safer.

- EMEX_PROXY_PROVIDER (default "floxy" | "dataimpulse" | "none"). floxy →
  fetchEmexHtml schedule = [floxy, floxy, dataimpulse] (Floxy sticky primary,
  rolls IP on transport failure, single DataImpulse last-ditch). dataimpulse →
  legacy [di,di,di,floxy,floxy]. Default HTTP agent (image-dims) follows provider.
- EmexBrowserService launches chromium on a sticky Floxy session (one residential
  exit IP for the browser lifetime; fresh id per relaunch) under the same flag.
- Reuses the existing EMEX_FLOXY_* config (same Floxy account pcat now uses).

Rollback: EMEX_PROXY_PROVIDER=dataimpulse. typecheck+biome+11 emex tests green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

root merged commit 4b5f3bb41e into main

2026-06-10 22:24:21 +03:00

root referenced this issue from a commit

2026-06-10 22:24:22 +03:00

Merge pull request 'promote(emex): Floxy residential primary transport' (#125) from promote-emex-floxy into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: root/sase.tr#125