You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
First run of 0.9.25: Failed to load persisted index: #797
Root cause: some iii-state adapters return undefined (not null) for a missing key. The sharded-load path checked manifest.value !== null and passed undefined through to loadManifestData, which then read undefined.v. Fixed by treating both null and undefined (plus non-object values) as 'no manifest' and falling through to the legacy load path. The crash itself was cosmetic — the debounced save rebuilt the index a few seconds later — but the boot-time stack trace was scaring every fresh upgrader.
Activity
IamSAL commentedon Jun 3, 2026
Same
chenmijiang commentedon Jun 3, 2026
Same, a new persistent index will be rebuilt after the first error is thrown
rohitg00 commentedon Jun 3, 2026
Thanks for creating this issue.
rohitg00 commentedon Jun 3, 2026
Shipped in v0.9.26 (release notes, PR #804).
Thanks @alxjzx100 for the precise repro + stack trace, and @IamSAL @chenmijiang for confirming.
Root cause: some iii-state adapters return
undefined(notnull) for a missing key. The sharded-load path checkedmanifest.value !== nulland passedundefinedthrough toloadManifestData, which then readundefined.v. Fixed by treating bothnullandundefined(plus non-object values) as 'no manifest' and falling through to the legacy load path. The crash itself was cosmetic — the debounced save rebuilt the index a few seconds later — but the boot-time stack trace was scaring every fresh upgrader.Upgrade:
First-run boot is quiet now.
fix(release): v0.9.26 hotfix for first-run load crash (rohitg00#797) (r…