Moe Hamade 821ec7c5f7 fix: check the cooldown on every attempt, not once before the loop ...

Addresses review on #812.

Each retry resampled the route but never rechecked the gate against it,
so a route change during a request or its backoff walked straight past a
cooldown. A Tor attempt failing with a 500, then the user switching to a
direct connection that is already rate limited, and the next attempt
contacts it regardless.

The check moves inside the loop, immediately after the route is sampled,
which makes it cover the first attempt too -- the separate post-wait
check it replaces was only ever that first iteration. The check before
the route wait stays: knowing the selected route is blocked is worth
avoiding a sixty-second Tor bootstrap for.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-02 15:56:25 +03:00

..

src

fix: check the cooldown on every attempt, not once before the loop

2026-08-02 15:56:25 +03:00

build.gradle.kts

fix: lock wear dependencies in CI

2026-07-29 12:20:48 +02:00

gradle.lockfile

fix: restore Android Studio sync with strict Gradle security

2026-07-29 18:15:50 +02:00

lint-baseline.xml

bump targetSdk (#526)

2025-12-14 21:55:41 +07:00

proguard-rules.pro

persist

2026-07-29 03:41:16 +02:00