7 views
-/https://github.com/berriai/litellm/issues/26647
GitHub ยท issue

#26647 Error while testing Avocado locally

  • State: open
  • Author: @szadissa71
  • Labels: llm translation, stale

szadissa@szadissa-mac szadissa-tbench % harbor run -p szadissa_tbench_task5_DmaCacheCoherency -a terminus-2 -m "openai/avocado_dvsc_tester" --timeout-multiplier 3.0 -k 5 โ ‡ 0/5 Running trials... โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ” 0:00:28 -:--:-- โ ‡ 0:00:27 szadissa_tbench_task5_DmaCacheCo__9EdHFFd: starting environment... โ ‡ 0:00:27 szadissa_tbench_task5_DmaCacheCo__hisEaed: running agent...

Give Feedback / Get Help: https://github.com/BerriAI/litellm/issues/new LiteLLM.Info: If you need to debug this error, use `litellm._turn_on_debug()'. โ ด 0/5 Running trials... โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ” 0:00:28 -:--:-- โ ผ 0:00:27 szadissa_tbench_task5_DmaCacheCo__9EdHFFd: starting environment...

Give Feedback / Get Help: https://github.com/BerriAI/litellm/issues/new LiteLLM.Info: If you need to debug this error, use `litellm._turn_on_debug()'. โ ฆ 0/5 Running trials... โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ€ฆ

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (3 events)
#0 of 0 ยท 31d18h26m28s ago โ€” entered ยท #import:https:::github.com:berriai:litellm post #2511
The left issue requires open-ended debugging across an external evaluation workflow, model integration, and runtime environment, with no clear failure point or narrowly defined implementation path. The right issue is a bounded dashboard change involving reuse of an existing component across a few forms, with server support already available.
#0 of 0 ยท 31d18h22m4s ago ยท #import:https:::github.com:berriai:litellm post #2581
The left issue is harder because it requires tracing provider-specific cache metadata through request transformation and callback/logging serialization while preserving existing observability behavior. The right issue appears narrower and more environment-specific, with likely limited diagnostic or configuration changes.
#0 of 0 ยท 31d17h59m3s ago โ€” current ยท #import:https:::github.com:berriai:litellm post #2981
The right issue is harder because it lacks a concrete failure point and may require cross-component environment investigation, while the left is a bounded API change with a known implementation area.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search