refactor: improve error handling in pipeline #10
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.
What changed
Replaced several
unwrap()andexpect()calls inpipeline/src/main.rswith proper error handling using match expressions. The changes provide clearer error messages and prevent unexpected panics during normal operation.Why
The pipeline binary is a core component for enclave communication, and users shouldn't see panic backtraces when things like config file issues occur. Better to give them a clean error message and exit code 1.
Changes
Tested the changes and confirmed that error messages are now user-friendly while maintaining the same exit behavior.