-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Backport #61798 to .NET 6 #73007
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @dotnet/ncl Issue Details#61798 is breaking concurrent use of the .NET Azure SDKs for us starting in .NET 6 (see Azure/azure-sdk-for-net#27018, for example). Can this fix be backported to .NET 6?
|
Judging by the stack trace you posted in Azure/azure-sdk-for-net#27018 (comment), you appear to be hitting #65379. Can you please try the workaround mentioned in the issue? |
Duplicate of #65379. (Of course, feel free to continue discussion around this issue there) |
@MihaZupan thanks for the info on the other error. However, I'm also seeing the index-out-of-bounds error (see Azure/azure-sdk-for-net#27018 (comment)) so I'd still appreciate that fix being backported. |
#65379 is the cause for that |
@MihaZupan ah ok I misunderstood. So #61799 covers both stacktraces and #68115 is completely unrelated?:
AND
Is that correct? |
#61798 tracks the issue that before 7.0, reading from a header collection concurrently was not thread-safe, blowing up in many different ways (like the two exceptions you observed). We treat concurrent use like that as improper usage. But there are cases where TL;DR; #65379 covers both of the exceptions you observed. |
@MihaZupan thanks. It is still my understanding that these problems are unique to (or at least much more prevalent in) .NET 6; we're hitting them through the Azure SDK and we did not see them prior to the .NET 6 upgrade. Do you think any of the relevant changes will be backported to 6? |
#61798 is breaking concurrent use of the .NET Azure SDKs for us starting in .NET 6 (see Azure/azure-sdk-for-net#27018, for example). Can this fix be backported to .NET 6?
The text was updated successfully, but these errors were encountered: