-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Deadlock when calling the code from an asp.net 4.8 web forms code behind #543
Comments
Hi there and welcome to this repository! A maintainer will be with you shortly, but first and foremost I would like to thank you for taking the time to report this issue. Quality is of the highest priority for us, and we would never release anything with known defects. We aim to do our best but unfortunately you are here because you encountered something we didn't expect. Lets see if we can figure out what went wrong and provide a remedy for it. |
Hi @ronenfe and thanks for reporting this. A couple of questions helping me reproduce this:
|
Yes, this code works if I copy the signing code out of the nuget and put it inside my project and make all calls sync except the call for the original httpclient which I use for it .ConfigureAwait(false).GetAwaiter().GetResult() because it also doesn't have a sync send for .net 4.x Maybe adding another method for sync signing in the nuget will work. I did a pull request on the other nuget for aws singing which I was part of writing it, but the owner doesn't approve it because he thinks it's unsafe , maybe you want to implement it the same way. tsibelman/aws-signer-v4-dot-net#37 (comment) |
I've found the bug and will start working on fixing it in the upcoming days. Thanks for reporting it! |
This issue has now been fixed in v3.0.1. Thank you for reporting this issue! |
Confirmed to work, thanks for the fast fix. |
Thank you, what solved it for us was adding .configureawait(false) to the async calls in the nuget. You can see there the pull request.
…On Mar 25, 2022, 9:55 AM +0300, Mattias Kindborg @FantasticFiasco ***@***.***>, wrote:
I've found the bug and will start working on fixing it in the upcoming days. Thanks for reporting it!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Describe the bug
Deadlock when calling the code from an asp.net 4.8 web forms code behind which is a synchronous code.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Method should not hang
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: