-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix rr worker e.code is undefined issue #1638
Conversation
WalkthroughWalkthrough:The changes to Changes:
Assessment against linked issues:
Poem:
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- core/src/worker/request-response.ts (2 hunks)
Additional comments not posted (5)
core/src/worker/request-response.ts (5)
22-22
: The addition ofOraklError
import is correctly placed and necessary for the new error handling logic.
88-88
: Typecasting the error toError | OraklError
is a robust approach to handle different types of errors. This ensures that type-specific properties are accessed safely.
89-89
: Logging the error immediately after catching it is a good practice as it ensures that all errors are recorded, aiding in debugging and monitoring.
94-96
: The conditional handling ofOraklError
usinginstanceof
to safely accesserror.code
is an excellent fix for the issue described. This prevents the application crash by ensuringerror.code
is accessed only when it is defined.
100-100
: Rethrowing the error after handling it allows the error to propagate, ensuring that higher-level error handlers can also react to it. This is a good practice in error management.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
Description
e.code
is undefined inworker/request-response.ts
when thee
is of typeError
, in which casee.code.toString()
will cause the app crash. This PR checks theinstanceof
the error and accesses the error code if the error type isOrakleError
Closes #996
Type of change
Please delete options that are not relevant.
Checklist before requesting a review
Deployment