-
Notifications
You must be signed in to change notification settings - Fork 149
fix: sync service otel and CI #5390
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
Open
404Wolf
wants to merge
2
commits into
main
Choose a base branch
from
wolf/fix-sync-service-prod
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+41
−8
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win
Make
normalizeErrorsafe for everyunknownvalue.JSON.stringify(error)can returnundefinedwithout throwing. Line 122 then falls through toString(error)instead of returning the intended"Unserializable thrown object"fallback. A custommessagegetter or string conversion can also throw. This can makeSpanImpl.errorthrow while it is handling the original error.Keep message access and final coercion inside guarded fallbacks.
Proposed fix
private static normalizeError(error: unknown): Error | string { - if (error instanceof Error || typeof error === "string") return error; - - if ( - typeof error === "object" && - error !== null && - "message" in error && - typeof error.message === "string" - ) { - return new Error(error.message); - } - - if (typeof error === "object" && error !== null) { - try { - const message = JSON.stringify(error); - if (message !== undefined) return new Error(message); - } catch { - return new Error("Unserializable thrown object"); + try { + if (error instanceof Error || typeof error === "string") return error; + if (typeof error === "object" && error !== null) { + const message = "message" in error ? error.message : undefined; + if (typeof message === "string") return new Error(message); + try { + const serialized = JSON.stringify(error); + return new Error(serialized ?? "Unserializable thrown object"); + } catch { + return new Error("Unserializable thrown object"); + } } + return new Error(String(error)); + } catch { + return new Error("Unserializable thrown value"); } - - return new Error(String(error)); }🤖 Prompt for AI Agents
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.
testing reply
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.
@whutchinson98, reply received.You are interacting with an AI system.
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.
again
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.
@whutchinson98, reply received.You are interacting with an AI system.