-
Notifications
You must be signed in to change notification settings - Fork 71
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
feat(sdks/actor/runtime): include url for debugging actor in internal error metadata #1952
Conversation
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.
PR Summary
This PR enhances actor debugging capabilities by adding error metadata URLs that link directly to specific actor instances in the Rivet Hub.
- Added
InternalErrorMetadata
interface insdks/actor/runtime/src/errors.ts
to include debugging URLs - Modified error handling in
sdks/actor/runtime/src/actor.ts
to include actor-specific Hub URLs in error metadata - Updated
sdks/actor/runtime/src/event.ts
to pass actorMetadata and construct debugging URLs for WebSocket errors - Enhanced error logging with additional context (connectionId, rpcRequestId, rpcName)
3 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile
sdks/actor/runtime/src/actor.ts
Outdated
metadata = { | ||
url: `https://hub.rivet.gg/projects/${this._metadata.project.slug}/environments/${this._metadata.environment.slug}/actors?actorId=${this._metadata.actor.id}`, | ||
} satisfies errors.InternalErrorMetadata; |
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.
logic: URL construction assumes project.slug and environment.slug are always available. Should handle case where metadata fields are undefined.
9485632
to
d2eaad4
Compare
2ea6c4b
to
d2eaad4
Compare
c5aac86
to
d2eaad4
Compare
6cf3ff7
to
d2eaad4
Compare
Merge activity
|
… error metadata (#1952) <!-- Please make sure there is an issue that this PR is correlated to. --> ## Changes <!-- If there are frontend changes, please include screenshots. -->
Changes