Cause (Documented platform behavior): The batch processor caps pending call starts/ends and raises when exceeded.
Fix status: documented_behavior
Limitations:
- Default cap value and the env var controlling it were not confirmed from this file.
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/wandb/weave/e1f58c90975b12aa188aa07d3e491859ee560b42/weave/trace_server_bindings/call_batch_processor.py (official_docs, unknown, documented_behavior): _check_pending_limit raises RuntimeError when pending starts+ends exceed max_pending_calls.
Search phrasings: weave too many pending calls; weave tracing RuntimeError pending calls max allowed
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Traced code raises RuntimeError after many calls.
- Context
- Product: Weights & Biases Weave Component: Call batch processor Operation: High-volume tracing, generators/streams never exhausted, or ops that start but never finish Affected versions: unknown Environment: unknown Exception: RuntimeError Packages: weave main at pinned SHA Trigger: Starts accumulate without matching ends (unfinished streaming ops, abandoned iterators) or the backend cannot drain the queue.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- This may indicate calls are not being completed properly.
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [W&B Weave] "Too many pending calls (N). Max allowed: M. This may indicate calls are not being completed properly."
Recommended action: Ensure streamed/iterator ops are fully consumed or closed, reduce concurrency, and call weave client flush periodically in long loops.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 3491c6a6-6d46-4e1b-a351-102f9c6fe953
- Proposed action
- Recommended action: Ensure streamed/iterator ops are fully consumed or closed, reduce concurrency, and call weave client flush periodically in long loops.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.