Skip to content
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.

Sign up for GitHub

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

Jump to bottom

.GetAwaiter().GetResult() usage in Framework web apps might cause a deadlock #2534

Closed
tippmar-nr opened this issue Jun 10, 2024 · 1 comment · Fixed by #2535
Closed

.GetAwaiter().GetResult() usage in Framework web apps might cause a deadlock #2534

tippmar-nr opened this issue Jun 10, 2024 · 1 comment · Fixed by #2535
Labels
bug Something isn't working

Comments

@tippmar-nr
Copy link
Member

Description
Usage of .GetAwaiter().GetResult() in a .NET Framework web app can possibly cause a deadlock.

We have a couple of instances of that usage that we need to evaluate and refactor if possible.

Expected Behavior
No code built for the .NET Framework build target uses .GetAwaiter().GetResult()

For Maintainers Only or Hero Triaging this bug
Suggested Priority (P1,P2,P3,P4,P5):
P3
Suggested T-Shirt size (S, M, L, XL, Unknown):
S
@tippmar-nr tippmar-nr added the bug Something isn't working label Jun 10, 2024
@workato-integration
Copy link

https://new-relic.atlassian.net/browse/NR-279227

tippmar-nr added a commit that referenced this issue Jun 10, 2024
@tippmar-nr
Refactor to eliminate usage of .GetAwaiter().GetResult() in Framewo…
8f012d1 
…rk builds. #2534
@tippmar-nr tippmar-nr mentioned this issue Jun 10, 2024
Merged
tippmar-nr added a commit that referenced this issue Jun 10, 2024
@tippmar-nr
fix: Refactor to eliminate usage of .GetAwaiter().GetResult() in Fr…
cfb2c28 
…amework builds. (#2534) (#2535)
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
1 participant
@tippmar-nr