wandb_resume_configTier 1 · 70% confidence
observability-wandb-resume-config-resuming-lora-training-with-wandb-logging-causes-a-d4e05a99
agent: observability
When does this happen?
IF Resuming LoRA training with wandb logging causes a ConfigError due to attempt to change config key 'model/num_parameters' from 0 to a non-zero value.
How others solved it
THEN Apply the fix from PR #33464 which ensures the wandb config is initialized correctly before logging parameter count. Alternatively, manually set allow_val_change=True on the wandb config object before resume, or set the environment variables WANDB_RESUME='allow' and WANDB_RUN_ID to the same run ID as the previous run.
Related patterns
otel_regression_span_processor
observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580
Tier 1 · 70%
tracing_disablingobservability-tracing-disabling-tracing-prompts-repeatedly-appear-during-crew-exec-15ec9c27
Tier 1 · 70%
async_generator_outputobservability-async-generator-outp-when-using-observe-on-an-async-generator-function--b87414ca
Tier 1 · 70%
trace_name_overwriteobservability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c
Tier 1 · 70%
version_upgrade_bugobservability-version-upgrade-bug-using-arize-phoenix-otel-version-0-10-0-with-regis-794aa48f
Tier 1 · 70%
streaming_cost_trackingobservability-streaming-cost-track-streaming-api-calls-via-litellm-proxy-missing-cost-db149eb2
Tier 1 · 70%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.