ERROR: The operation was canceled. -> Unable to read data from the transport connection: Operation canceled.

Hello,

When I run dotnet symbol to download debug symbols for .NET Core SDK 2.1.10 it throw the following error:

...
Writing: /usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.10/System.Diagnostics.FileVersionInfo.pdb
Cached: /root/.dotnet/symbolcache/system.componentmodel.annotations.pdb/5b25c24677e342c39b52d7d0bb347779FFFFFFFF/system.componentmodel.annotations.pdb
Writing: /usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.10/System.ComponentModel.Annotations.pdb
Cached: /root/.dotnet/symbolcache/system.private.corelib.pdb/d86a24c58e91402d8f6d21028185ef75FFFFFFFF/system.private.corelib.pdb
Writing: /usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.10/System.Private.CoreLib.pdb
ERROR: The operation was canceled. -> Unable to read data from the transport connection: Operation canceled.

Looks like dotnet symbol is trying to download large file and can’t do it because exceed read timeout. Could you please check it?

Steps to reproduce:

1. Create Dockerfile:

   FROM mcr.microsoft.com/dotnet/core/sdk:2.1.603@sha256:8eda326c4c0bd038f3cc5aeb5c8af8374b88f1b90eb444ed91bab42f2e17840f
   
   RUN dotnet tool install -g dotnet-symbol
   
   ENV PATH=$PATH:/root/.dotnet/tools
   
   RUN dotnet symbol --diagnostics --symbols --output /usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.10 '/usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.10/*'
   

2. Run docker build to build this docker file:

   docker build . -f Dockerfile
   

It should show error described above.

Thank you.

[am11]

It is not a coincidence that multiple people are reporting these timeout issues as an unexpected behavior (https://github.com/dotnet/diagnostics/issues/602, https://github.com/dotnet/diagnostics/issues/412). This internet connection downloads 10 GB in less than 200 seconds while streaming Netflix videos, so downloading 70 MB file (for singlefilehost symbols) should take about 1.1 second, while it waits for four minutes and timesout. It looks like the symbol servers are not setup with CDN, so folks outside the US will hit the slow connection (but I don’t know why it is THIS slow?)

I think --timeout command-line argument in various tools that interact with symbol server would be an OK short-term pragmatic solution (please add it or just a --no-timeout?; timeout option is currently missing in all tools in the latest versions); but the real solution would be to setup CDN for symbol server, or move the blobs under a better storage plan such as; geo-zone redundant storage.

@mikem8361, should we report it as a new issue or could this be reopened for tracking purposes? Diagnostic tools are unusable for some of us.

[am11]

could you submit a new issue to add a --timeout option to dotnet-symbol? Thanks.

https://github.com/dotnet/symstore/issues/246.