-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Pydantic validation error when accessing trace #2289
Comments
Hmm, this looks like a bug on our end. It seems like it might be related to the work in getsentry/sentry#50846. We are currently having some migration issues with 23.7.0 (more info), but will release 23.7.1 on Monday, which will include the change linked above. Once we do, would you be willing to upgrade and post the (hopefully) newly available stack trace produced by this error? |
I am getting this issue as well on 23.6.1 (same http response)
Looking at the logs, looks like my issue may be different? Happy to open a new issue if needed edit: nvm, found #2266 and fixed this with |
I am getting this issue as well on 23.6.1 (same http response)
|
@damon-kwok this seems like a different issue (Snuba vs Hybrid Cloud). Would you mind opening a separate bug so that we can route to the correct location? |
Self-Hosted Version
23.6.1
CPU Architecture
x86_64
Docker Version
24.0.4
Docker Compose Version
1.29.2
Steps to Reproduce
{"detail":"Internal error. Your query failed to run."}
We are running a stock install of sentry where the config only has custom slack configuration and mail configuration.
Expected Result
The trace page, so we can correlate data accross all services
Actual Result
logs output of the web page:
Schreenshot as shared above.
If you need more information, please feel free to reach out.
Event ID
No response
The text was updated successfully, but these errors were encountered: