`gjdZddlZddlZddlZddlmZdaejZdZ dZ dddd d e d e d e d e de f dZ dedefdZdedzdedzdedefdZe dd e dedzdedzdede de dee edzffdZe fde de fdZy)uRetry utilities — jittered backoff for decorrelated retries. Replaces fixed exponential backoff with jittered delays to prevent thundering-herd retry spikes when multiple sessions hit the same rate-limited provider concurrently. N)Any)g>@gN@gV@^@g@rg? base_delay max_delay jitter_ratioattemptrrr returncJt5tdz at}dddtd|dz }|dk\s|dkr|}nt|d|zz|}t j dzz dz}t j|}|jd||z} || zS#1swYxYw)aCCompute a jittered exponential backoff delay. Args: attempt: 1-based retry attempt number. base_delay: Base delay in seconds for attempt 1. max_delay: Maximum delay cap in seconds. jitter_ratio: Fraction of computed delay to use as random jitter range. 0.5 means jitter is uniform in [0, 0.5 * delay]. Returns: Delay in seconds: min(base * 2^(attempt-1), max_delay) + jitter. The jitter decorrelates concurrent retries so multiple sessions hitting the same provider don't all retry at the same instant. Nr?lyn<l) _jitter_lock_jitter_countermaxmintimetime_nsrandomRandomuniform) r rrr tickexponentdelayseedrngjitters D/root/.hermes/venv/lib/python3.12/site-packages/agent/retry_utils.pyjittered_backoffr $s. 11gk"H2~qJ!x-0)< LLNdZ/ 0J >D -- C [[L50 1F 6>s BB"errorc|t|ddt|ddt|ddg}djd|DjS)zCBest-effort flattened provider error text for retry classification.messageNbodyresponse c38K|]}|t|yw)N)str).0parts r z_error_text..UsD$43CCIDs)getattrjoinlower)r!partss r _error_textr0MsR y$'vt$z4(  E 88D%D D J J LLbase_urlmodelc|xsdj}|xsdj}t|dd}t|}|dk(xrd|vxrd|vxr d|vxsd|vS) aLReturn True for Z.AI Coding Plan transient overload 429s. The coding-plan endpoint reports overload as HTTP 429 with body code 1305 and message "The service may be temporarily overloaded...". Treat only that narrow shape specially so ordinary quota/billing 429s still fail fast through the existing classifier. status_codeNizapi.z.ai/api/coding/paas/v4zglm-5.21305ztemporarily overloaded)r.r,r0)r2r3r!base model_namestatustexts ris_zai_coding_overload_errorr<Xs N ! ! #D+2$$&J UM4 0F u D#  A )T 1 A  # At^ ?74? r1short_attempts default_waitr>ct|||s|dfS||kr|dfSt||z dz ttdz }t|}t d||ddfS)u7Provider-aware rate-limit backoff. For most providers this returns ``default_wait`` unchanged. For Z.AI Coding Plan GLM-5.2 overloads, keep the first ``short_attempts`` retries on the normal short exponential schedule, then switch to progressively longer waits (30s → 60s → 90s → 120s, capped) plus light jitter. ``attempt`` is 1-based, matching the retry loop's logged attempt number. Returns ``(wait_seconds, reason_label)`` where ``reason_label`` is suitable for status/log decoration when a provider-specific policy fired. )r2r3r!Nzai_coding_overload_shortr g?rzai_coding_overload_long)r<rlen!_ZAI_CODING_OVERLOAD_LONG_BACKOFFr )r r2r3r!r?r>idxrs radaptive_rate_limit_backoffrFlsu( (e TT!!. 888 g&*C0Q,RUV,V WC237J A* Y\ ]_y yyr1c,|ttzdzS)uRetry-loop ceiling needed for the full Z.AI overload backoff schedule. The adaptive policy runs ``short_attempts`` short retries, then walks the long-backoff table one entry per subsequent attempt. The retry loop gives up as soon as ``retry_count >= ceiling`` — and that check runs *before* the attempt's backoff is computed — so the ceiling must sit one past the final long-backoff entry for every long tier to actually execute. With the default ``api_max_retries`` (3) equal to ``short_attempts`` (3), the loop always gave up before reaching the long tier, leaving the whole long-backoff schedule as dead code. Callers extend the ceiling to this value for Z.AI Coding overload 429s so the 30/60/90/120s waits run. r )rCrDr=s r!zai_coding_overload_retry_ceilingrHs C AB BQ FFr1)__doc__r threadingrtypingrrLockrrD#_ZAI_CODING_OVERLOAD_SHORT_ATTEMPTSintfloatr r(r0boolr<tuplerFrHr1rrSsI  y~~ %>!'(#  & && &  &  &RMsMsMcDjtTW\`6>z zDjz : z  z  zz 5#* z@=`GcGdgGr1