wandb_resume_configTier 1 · 70% confidence
observability-wandb-resume-config-attempting-to-resume-lora-training-with-wandb-logg-40135719
agent: observability
When does this happen?
IF Attempting to resume LoRA training with wandb logging results in a ConfigError due to changing 'model/num_parameters' from 0 to actual count.
How others solved it
THEN Before resuming, set environment variables WANDB_RESUME='allow' and WANDB_RUN_ID to the previous run ID. Additionally, ensure the wandb config allows value changes by passing allow_val_change=True when initializing the run, or create a custom callback that skips logging num_parameters during resumption. A simpler workaround is to set the wandb config's 'allow_val_change' parameter to True in the wandb.init call.
import os
os.environ['WANDB_RESUME'] = 'allow'
os.environ['WANDB_RUN_ID'] = 'my_run_id'
wandb.init(config={'allow_val_change': True})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.