chore(deps): vendor-bump sphere-sdk to 77bbbdc (Profile init tolerance)#313
Merged
vrogojin merged 1 commit intoMay 27, 2026
Merged
Conversation
…t tolerance) Brings in sphere-sdk PR #301 (merged at 77bbbdc onto integration/all-fixes): fix(profile): tolerate corrupt-block bundle refresh during lifecycle init This addresses the SECOND failure surfaced during the migration retest after PR #300 landed. With PR #300, the migration now reached `target-save` but failed with `Provider not initialized` because `tokenStorage.initialize()` had returned false after `db.all()` threw on a corrupt OpLog block left behind by a previous failed migration. With PR #301: - `LifecycleManager.initialize` wraps `refreshKnownBundles()` in try/catch; logs warning + emits `storage:error` with code `BUNDLE_INDEX_REFRESH_FAILED`; proceeds with empty bundle set. - The empty-set branch triggers cold-start recovery (aggregator pointer / legacy IPNS); the recovery's first successful write produces a fresh OpLog entry whose block IS reachable. - The provider reaches `setInitialized(true)`, so `save()` works normally — migration unblocked. - `Sphere.initializeProviders` now subscribes to provider events BEFORE the parallel `Promise.all(...).map(p => p.initialize())` call, so the new `BUNDLE_INDEX_REFRESH_FAILED` event reaches the `connection:changed` bridge in production (consumers — including this sphere.telco — can now react to the degraded state). - 6 new tolerance tests + 2 new ordering tests added in the SDK PR. 2037+/2037+ profile + 525/525 Sphere core green. Three adversarial steelman passes on the SDK PR converged on SHIP IT.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings in sphere-sdk PR #301 —
fix(profile): tolerate corrupt-block bundle refresh during lifecycle init. Addresses thetarget-save: Provider not initializedfailure surfaced during the migration retest after PR #300. Three steelman passes converged on SHIP IT.