You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Waiting for network timeouts can be a major bummer. It would be great if we could:
Add overloads that take System.Threading.CancellationTokens.
Add support for configurable timeouts (shorter than network timeout by default?).
Async support would be icing on the cake.
Some comments from Lee:
In addition to cancellation support, we also need to have a timeout for SymbolLocator. I’m not sure if it should be an individual timeout (for slow individual servers) or a global timeout when calling FindBinary/FindPdb (such that after N seconds the operation is cancelled) or both. Keep in mind that calling virtually any function in ClrMD may go out to the symbol server to download files if we are missing metadata that we need to perform an operation.
Also it’d be really nice if ClrMD could support some modern features like async/await…especially for symbol servers.
The text was updated successfully, but these errors were encountered:
I have implemented async/await additions to ClrMD, along with adding a timeout to SymbolLocator. Unfortunately HttpWebRequest does not accept cancellation tokens, so I'm not sure there's an easy way to use one here.
unless the server responds with a 200 OK. Modified the
``GetPhysicalFileFromServerAsync`` method to use HttpClient instead of
HttpRequest to leverage it's better async support (see microsoft#4).
Hello! This issue is being closed due to its age. The codebase has moved significantly since this was filed. Please feel free to open a new issue for ClrMD about this issue if it still reproduces on ClrMD 1.0. (Also, I apologize for having not looked at or resolved this earlier and for resolving it now. In order for me to be able to make some progress on the growing issue count in ClrMD I need to clear the backlog down to a manageable set of issues, but do feel free to file a new one if this is still a problem.)
Waiting for network timeouts can be a major bummer. It would be great if we could:
Some comments from Lee:
The text was updated successfully, but these errors were encountered: