-
-
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
symbolicator request failed, "Failed to deserialize the JSON body into the target type: unknown variant portablepdb
"
#1860
Comments
PortablePDB is a format for .NET... so that's really odd. Could you try upgrading to the 8.x cocoa SDK and see if that stops the errors from happening? |
Since upgrading from 22.10 to 22.11 we encounter this exact same issue. My guess would then be this is not related to the SDK being used |
Looking at the latest Changing that version to |
Ok, that's great to hear! This should get fixed in the release tomorrow then, we will be bumping symbolicator in the 22.12 release. Kind of unfortunate the error message is so unclear :/ |
I believe this has nothing to do with the cocoa SDK, but rather the This source configuration is being sent to (and decoded by) symbolicator just in case you wanted to fetch such files from the microsoft symbol server. It is a bit surprising though that the published github release is being used by selfhosted deployments, rather than an uptodate docker image. We have no real release schedule for tagged github releases of symbolicator, and the releases that we do, do not match any self-hosted sentry releases. I believe that is the main problem here. |
As part of the self-hosted release infrastructure, which runs once a month when we do a self-hosted release, we push the latest gcr docker image to dockerhub which is what we use in self-hosted.
Ah I see, so it seems that Sentry <-> Symbolicator were incompatible? I suppose it would be good to add a test for a symbol-related workload to the self-hosted CI (we're looking to expand our tests this quarter). Thank you for pointing that out! |
yes exactly.
That seems like a good idea, yes. To cover this particular usecase, you would need a test that uses all the builtin symbol servers. A Windows minidump perhaps. We should have one already in the main Sentry tests, though those tests are always testing the very latest symbolicator master. |
This is fixed in 22.12.0. Please open a new issue if you still encounter problems going forward! |
Self-Hosted Version
22.11.0
CPU Architecture
x86_64
Docker Version
20.10.21
Docker Compose Version
2.12.2
Steps to Reproduce
Upgraded from 22.5.0 to 22.11.0. Uploaded new events from iOS sentry-cocoa 7.9.0.
Expected Result
No errors on the instance's
internal
project?Actual Result
I see an issue similar to #1818 (comment), many many times for "portablepdb" symbols. This was not happening prior to upgrading.
Raw event json:
Event ID
No response
The text was updated successfully, but these errors were encountered: