fix: attach error reporting directly to logs; sourceLocation#4855
Merged
Hidden character warning
The head ref may contain hidden characters: "more-\ud83e\udeb5"
Conversation
another-rex
approved these changes
Feb 20, 2026
tymzd
pushed a commit
to tymzd/osv.dev
that referenced
this pull request
Apr 13, 2026
…4855) Add a `@type` field to the error logs in Google cloud to send them to error reporting directly, instead of making a separate API call (see https://docs.cloud.google.com/error-reporting/docs/formatting-error-messages#log-text). This is what python was already doing. Also, changed the `sourceLocation` field to the more complete key so it gets put into the top-level log instead of within the jsonPayload.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add a
@typefield to the error logs in Google cloud to send them to error reporting directly, instead of making a separate API call (see https://docs.cloud.google.com/error-reporting/docs/formatting-error-messages#log-text). This is what python was already doing.Also, changed the
sourceLocationfield to the more complete key so it gets put into the top-level log instead of within the jsonPayload.