product · inferred from evidence
Weave
A product that provides tracing and context management for operations, including those decorated with @weave.op().
- `@weave.type()` does not work with pydantic `BaseModel`
If Weave throws a 500 ('too many values to unpack') when tracing a function that takes a nested pydantic model, check whether one of the fields is called 'name'. The maintainers confirmed 'name' is reserved and used to build internal weave-
- @weave.op() doesn't appear to work with **kwargs argument type.
A practical guide for Weights & Biases Weave. weave.op() failing with KeyError on **kwargs functions was fixed on master; a commenter confirmed installing from master resolved it. If your @weave.op() decorated function takes **kwargs and bl
- error when running code in `tutorial-rag`
The `tutorial-rag` errors were fixed by the reporter's pull request, which the maintainer merged as PR #1840. Update to a Weave release containing that merge and the tutorial runs cleanly; no local workaround is needed.
- Cannot use Weave with HuggingFace?
Teaches how to cannot use Weave with HuggingFace?. Based on a real issue report and its verified fix.
- weave.monitoring.openai ignores openai.api_key (requires kwarg)
Weave's openai monitor wrapper only picked up the API key when passed as an explicit kwarg; `openai.api_key value ...` (the documented OpenAI SDK behavior) was ignored. This was addressed in a later Weave release (maintainer confirmed 2024-
- Weave ops not tracing when called from Flask endpoints
What this covers: Functions decorated with `@weave.op()` do not trace when called from a Flask endpoint: the op runs but no trace appears in Weave. The fix that worked: This was a context-management bug in Weave: the trace context did not s