fix: explain cancelled Somnia network changes - #90
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Summary
Catch add/switch-network errors at their source. Cancellation explicitly requires Somnia Testnet; other failures explain manual network selection. Both stop before order preparation and submission. No contracts/database/dependencies changed. README and hardening evidence updated. Refs #8.
Validation
67 Node + 89 Vitest tests pass; typecheck/build pass. Two new component cases cover nested 4001 cancellation and other provider failures, verify no prepareOrder/sendPlan invocation, and check review is available again. Initial full run hit the new test's default one-second lazy-load wait; aligned it with the existing five-second UI helper, then full rerun passed. Existing bundle-size warning remains.
Owner production screenshot demonstrated the vague original error; successful network recovery still requires owner acceptance.