uPj4 xUdZddlZddlmZmZmZmZddlmZddl m Z m Z m Z ddl mZddlmZmZmZmZddlmZdd lmZe rdd lmZehd Ze ed <ed dhZe ed<eddhZe ed<eddGddZ ee geefZ!e ed<de defdZ"de#de#de#dee#fdZ$dZ%d d!de&fd"Z'd d!de&fd#Z(e"fde d$e!ddfd%Z)d7d&Z*d d!d'eddfd(Z+d'ede&fd)Z,d'ede&fd*Z-eddGd+d,Z.iZ/e0e1e.fed-<d.e1d/d0ddfd1Z2d'e3d2ee1e3fd3e1dd4fd5Z4e"fd.e1d$e!ddfd6Z5y)8a Cost tracking for background interactions. A create request with ``background=true`` returns ``in_progress`` with no usage block, and GET polls are deliberately never billed (billing them would double-charge every poll; the GET response also does not echo ``background``, so a poll cannot be told apart from a re-fetch of an already-billed interaction). The create call is therefore the only place that can own billing: it schedules a poll task that fetches the interaction until it reaches a terminal status and logs the final usage as a single success event attributed to the original request. ``requires_action`` is terminal for the interaction it names. The API has no operation that resumes one: a caller answers a tool request by creating a new interaction whose ``previous_interaction_id`` points at it, and that new interaction bills itself. The paused interaction keeps the tokens it already spent producing the tool request, so it is billed and settled where it stops rather than polled until the timeout, which would both lose that usage and hold its budget reservation open for the whole timeout window. Deleting an interaction makes every subsequent poll fail, which would let a caller retrieve the completed output themselves and then delete it before the poll task settles, leaving the work unbilled and the budget reservation refunded at the poll timeout. ``adelete`` therefore settles any pending poll for the interaction before dispatching the delete: it fetches the current state with the create's credentials, bills it if it is terminal with usage, and releases the reservation otherwise. A settlement gate on the create's logging object makes the poll task and the delete path mutually exclusive, so the interaction is billed exactly once no matter who settles first. N) AwaitableCallableIteratorMapping) dataclass) TYPE_CHECKINGFinal TypeAlias)verbose_logger)9BACKGROUND_INTERACTION_COST_POLL_INITIAL_INTERVAL_SECONDS5BACKGROUND_INTERACTION_COST_POLL_MAX_INTERVAL_SECONDS0BACKGROUND_INTERACTION_COST_POLL_TIMEOUT_SECONDS+BACKGROUND_INTERACTION_COST_POLLING_ENABLED) get_litellm_metadata_from_kwargs)InteractionsAPIResponseLogging>failed cancelled completed incompletebudget_exceededrequires_action_TERMINAL_STATUSES in_progressqueued_POLLABLE_STATUSESrr_STATUSES_THAT_PRODUCED_OUTPUTT)frozenslotsc~eZdZUeed<eed<ded<dZedzed<dZedzed<eZe ed<e Z e ed <e Z e ed <y) BackgroundInteractionPollContextinteraction_idcustom_llm_providerLiteLLMLoggingObj logging_objNapi_keyapi_baseinitial_interval_secondsmax_interval_secondstimeout_seconds)__name__ __module__ __qualname__str__annotations__r'r(r r)floatr r*rr+q/home/oem/CyberBrain26-unified/.venv/lib/python3.12/site-packages/litellm/interactions/background_cost_polling.pyr"r";sP$$GS4ZHcDj&_e_"W%WMOUMr3r"FetchInteractioncontextreturncKddlm}|d|j|j|j|j dddid{S7w)Nr)aget)r#r$r'r(zno-logTr2)litellm.interactionsr9r#r$r'r()r6r9s r4_fetch_interactionr;JsX)--#77!!  d   sAA AA initialmaximumtimeoutc#Kd}|}|dkDr1||z|kr(|||z }t|dz|}|dkDr ||z|kr&yyyyw)Ngr)min)r<r=r>elapsedintervals r4_poll_intervalsrDXs^GH Q,7X-88x!|W- Q,7X-8,8,s7>>background_interaction_settledr&r%cD|jjtduS)NT)model_call_detailsget _SETTLED_KEYr&s r4 _is_settledrKds  ) ) - -l ;t CCr3cBt|ryd|jt<y)z Exactly-once gate between the poll task and the delete-time settlement: both run on the same event loop and neither awaits between reading and setting the flag, so whichever claims first owns billing or release. FT)rKrGrIrJs r4_claim_settlementrMhs" ;37K""<0 r3fetch_interactioncKd}t|j|j|jD]}t j |d{t |jry ||d{}|j}|jtvrgt|jsy|j!t!|j|d{yt#|jd{yt|jsy|5|t$vr-tj&d|j|j|n+tj(d|j|jt#|jd{y7H7##t$r,}tjd|j|Yd}~d}~wwxYw777Gw)N)r<r=r>z>Background interaction cost poll for %s failed, will retry: %sr&responserJzGave up cost polling for background interaction %s after %ss: its last status %r is in neither the pollable nor the terminal set, so this proxy never learned how to settle it and its usage will not be trackedz[Gave up cost polling for background interaction %s after %ss; its usage will not be tracked)rDr)r*r+asynciosleeprKr& Exceptionr debugr#statusrrMusage_bill_settled_interaction _release_open_budget_reservationrerrorwarning)r6rNlast_seen_statusrCrQes r4(poll_and_log_background_interaction_costr^ts$(#00,,'' mmH%%% w** +  .w77H$?? ??"4 4  !4!45  >> %+8K8KV^_ _ _ 3w?R?RS S S56 W00 1#(8@R(R "  " "  # #     i  " "  # # +w7J7J KKKO &8   P&&     ` S&LsA G F G) F4F5F9AGGG5G6BGGGF G#!G G GGGGcKt|j}|jd}t|tsyddlm} ||d{y7#t$rtjdYywxYww)a The proxy keeps the pre-call budget reservation open for an in-progress background interaction so concurrent creates cannot stack past the budget. The completion success event reconciles it to the actual cost; when the interaction terminates without billable usage (or polling gives up, or it is deleted before settling), no such event fires, so whoever claims the settlement must release the reservation here or the spend counters stay pinned at the estimated cost. )kwargsuser_api_key_budget_reservationNr)release_budget_reservation)budget_reservationzKFailed to release budget reservation for an unbilled background interaction) rrGrH isinstancedict/litellm.proxy.spend_tracking.budget_reservationrbrTr exception)r&metadatarcrbs r4rYrYsm0{7U7UVH!&GH ($ /Zp(zDmaybe_schedule_background_interaction_cost_polling..s n^f@gr3)*litellm.litellm_core_utils.litellm_loggingrrrdrrprHrRget_running_loop RuntimeErrorr"rnr/ create_taskr^rtrwr#add_done_callback) rQr|r$rr&r'r(r6rvs r42maybe_schedule_background_interaction_cost_pollingrs C 6 h 7 8 -h 7##$9:K k7 +  " *G  ,H.{{/%gs3'#6D G   GP QD,AtU\,]M'(()(/(>(>g K! s D D&%D&c(Ktj|}|y|j} ||d{}t |jsy|jtvr,|j t|j|d{yt|jd{y7w#t$rU}t j d||t |jrt|jd{7Yd}~yd}~wwxYw77jw)NzVCould not fetch background interaction %s before delete, releasing its reservation: %srJrP) rwrHr6rTr rUrMr&rYrVrrWrX)r#rNrzr6rQr]s r41maybe_settle_background_interaction_before_deleter!s   n -E }mmG *733 W00 1,,1K'G4G4GRZ[[[ *w7J7J KKK4  d   W00 12w?R?RS S S \Ksi%D B-B+B-ADDD%D&D+B-- D 6AD;C><DDD  DD)r&r%r7N)6__doc__rRcollections.abcrrrr dataclassesrtypingrr r litellm._loggingr litellm.constantsr r rr'litellm.litellm_core_utils.core_helpersrlitellm.types.interactionsrrrr% frozensetrr0rrr"r5r;r1rDrIrmrKrMr^rYrXrprrrtrwrer/r{objectrrr2r3r4rsT>BB!22+ U>W%\E&}h&?@E@(1;@Q2R(SS $d#NN$N'(H'I9UlKm'mn)n &F Kb .U.U.U.xPU.0 D0DTD #6 4 +=1L -1L'1L 1Lhp. 1D Pg lp G1HGTG" A(? AD A $d#..$. 35 tC../4*#*-A*d* ""3;'""! "N+=LL'L Lr3