Christian Klemm

We are having the same issue. I don't have insights on how symbolicator works internally but I find it a bit strange that it attempts to download external code instead...

No, we are not self-hosting. I've already created a support ticket for this issue and got redirected here. It seems that no source files are uploaded in the first place...

This seems to not be working correctly then. We're still seeing the Azure DevOps unauthenticated HTMl being used as source for our C# files.

None that I could send you publicly. Any chance I can send over one privately?

I've send you both, a pdb file and an error for this exact pdb.

Any updates on this? This makes MSAL in Blazor basically useless.

Which version is supposed to fix this issue? We're running 5.14.1 but we still get a lot of WASM warnings. ``` 13:11:23 [WRN] /root/.dotnet/packs/Microsoft.NET.Runtime.WebAssembly.Sdk/9.0.9/Sdk/WasmApp.Common.targets(793,5): warning WASM0001: Could not get pinvoke,...

We're not using Redis. This is our configuration: ```yaml relay: mode: managed upstream: https://xxxxxxxxxxxxxxx.ingest.de.sentry.io host: 0.0.0.0 port: 3000 logging: level: info limits: max_thread_count: 2 sentry: enabled: true dsn: https://[email protected]/xxxxxxxxxxxxx ```

Here the logs for the last 24 h. This error is being reported after the container received a SIGTERM and tries to gracefully shut down. For some reason it stops...

Bump