SETTLE_WALK_UNINITIALIZED_SOURCE
Internal: settle walk reached a source that never produced a value (reported).
What you saw
- Kind:
lifecycle - Severity:
error(broken behavior)
The console report opens with [SETTLE_WALK_UNINITIALIZED_SOURCE] and the message, then an in line naming the owners that enclose the subject, root first, and an at line with the source location when the code was compiled with one.
In a captured artifact the same finding is an event with code: "SETTLE_WALK_UNINITIALIZED_SOURCE", ownerPath, and loc.
Diagnostics explains each line.
Why it fires
The runtime tried to settle a source before it produced a value or an error. Waking its parked readers at that point would expose its initial value instead of settled data. This is an internal consistency check, reported in development.
How to fix it
Keep the full diagnostic and reduce the async sequence to a reproduction when reporting it; adding flush() or silencing the diagnostic does not repair the missing value.
In tests
captureArtifact from @solidjs/diagnostics runs a scenario with the diagnostics channel open and returns the events it saw.
expectNoDiagnostics(artifact) fails while SETTLE_WALK_UNINITIALIZED_SOURCE is among them, with the events as evidence; after the fix, the code is gone from artifact.diagnostics.
Check for regressions in tests shows the loop and the Vitest matcher form.
Learn more
- Diagnostics: every code, with its kind, severity, and trigger.
- Debugging reactivity: how to read a report and what each group of codes points at.