fix(tags): resolve CI failures on tag spend reset PR

- suppress BLE001 for the Redis best-effort catch, matching the
  sanctioned pattern used elsewhere for intentional broad catches
- regenerate schema.d.ts so the dashboard types include the new
  spend field on TagUpdateRequest
This commit is contained in:
Arnold Galovics 2026-09-18 09:21:20 +02:00
parent 89f80f1976
commit b902bf210e
2 changed files with 4 additions and 1 deletions

View file

@ -484,7 +484,7 @@ async def update_tag(
if spend_counter_cache.redis_cache is not None:
try:
await spend_counter_cache.redis_cache.async_set_cache(key=counter_key, value=tag.spend, ttl=60)
except Exception as redis_err:
except Exception as redis_err: # noqa: BLE001 # best-effort refresh: a Redis failure must not fail the request
verbose_proxy_logger.warning(
"Failed to update spend counter %s in Redis after tag spend update: %s. "
"Budget checks may use stale value until counter expires.",

View file

@ -16344,6 +16344,7 @@ export interface paths {
* - description: Optional[str] - Updated description
* - models: List[str] - Updated list of allowed LLM models
* - budget_id: Optional[str] - The id for a budget to associate with the tag
* - spend: Optional[float] - Set the tag's accumulated spend (e.g. 0 to reset it). Omit to leave unchanged. Does not change budget_reset_at; the current budget window is left as-is
*
* ### BUDGET UPDATE PARAMS ###
* - max_budget: Optional[float] - Max budget for tag
@ -45505,6 +45506,8 @@ export interface components {
rpm_limit?: number | null;
/** Soft Budget */
soft_budget?: number | null;
/** Spend */
spend?: number | null;
/** Tpm Limit */
tpm_limit?: number | null;
};