-
Notifications
You must be signed in to change notification settings - Fork 371
CloudBlob.UploadText/UploadTextAsync loads for ever. #864
Comments
Hi @EmmaZhu , Could you please help me on this issue ? I'm completely blocked here. Attention Required !! |
There is nothing in the code you show that would obviously lead to the behavior you're seeing, particularly since you say it works and continues to work for the first person to call it in your production deployment. That's not a behavior I'd expect in any class of bug the SDK could exhibit -- async deadlocks would not care about the caller, for example. I suspect the issue is at a higher level than this method. Can you please describe what environment you're in? Is this ASP.NET, or a console app, or something else? Do you have a stack trace? Fiddler logs? |
Hi @kfarmer-msft , Thanks for the response, the environment is .Net Web API (REST Service). 'I suspect the issue is at a higher level than this method.'
Thanks, |
Hey @kfarmer-msft , I have got you a Fiddler Archive for that particular request that i make. Even this request hangs and crashes. Please help me fix this ASAP, I'm blocked |
Sorry, but there's nothing in that archive that shows any activity beyond the existance of an encrypted connection. You say the process crashes in your production environment. Have you attempted to debug into the production process? Have you any stack traces? Exception messages that might be getting swallowed? Without this, I'm not going to be able to help you track down where the issue actually is. Your code snippet isn't really anything that is going to help narrow things down here -- it's no different from any test method we already have. What is going to be different is how it's called (eg, how you use it via DMLib), and different environments can do different things that neither you nor I nor DMLib would necessarily think about: that's the sort of thing that leads to being unable to reproduce it locally. |
Issues is with ?
Dot Net SDK used
Which platform are you using? (ex: .NET Core 2.1)
What problem was encountered?
How can we reproduce the problem in the simplest way?
Have you found a mitigation/solution?
My Code Snippet
The text was updated successfully, but these errors were encountered: