fix: handle vss key not found #100
Merged
Conversation
This file contains 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
EthanYuan
force-pushed
the
fix-vss-key-not-found
branch
from
b429363 to
0bbf333
Compare
EthanYuan
force-pushed
the
fix-vss-key-not-found
branch
from
0bbf333 to
8fd9ca9
Compare
Flouse
approved these changes
Mar 12, 2025
ShookLyngs
approved these changes
Mar 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request introduces a new error type
VssKeyNotFoundto handle cases where a VSS key is not found, along with the necessary logging and error handling updates across various files in themutiny-coreandmutiny-wasmmodules.