Skip to content
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

thread_id is typed as a string but Sentry actually sends ints #769

Closed
bfpepper87sentry opened this issue Feb 5, 2024 · 2 comments
Closed

Comments

@bfpepper87sentry
Copy link

Problem Statement

/~https://github.com/getsentry/sentry-go/blob/master/interfaces.go#L244

^This field, thread_id, is typed as a string but Sentry actually sends ints. This is blocking us from deserialising any event from Sentry.

This is the only issue with the modelling I've found.

Background:
We have the Android Sentry SDK set up in our app. We've got a Go webhook consuming alert events. These events cannot be deserialised currently because of this bug. Not sure if this problem is somehow specific to event_alerts coming from a JVM/Android project or not.

The original issue was raised here.

#767

Solution Brainstorm

No response

Product Area

Issues

@getsantry
Copy link

getsantry bot commented Feb 5, 2024

Assigning to @getsentry/support for routing ⏲️

@Fwang36 Fwang36 transferred this issue from getsentry/sentry Feb 6, 2024
@getsantry getsantry bot moved this from Waiting for: Support to Waiting for: Product Owner in GitHub Issues with 👀 2 Feb 6, 2024
@cleptric
Copy link
Member

cleptric commented Feb 6, 2024

Already tracked here #767

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants