-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Processor improvements #26904
Processor improvements #26904
Conversation
Thank you for your contribution @danielmarbach! We will review the pull request and get back to you soon. |
This pull request is protected by Check Enforcer. |
/azp run net - servicebus - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
sdk/servicebus/Azure.Messaging.ServiceBus/src/Processor/ReceiverManager.cs
Show resolved
Hide resolved
I think we need the same fix in SessionReceiverManager - https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/src/Processor/SessionReceiverManager.cs#L352 |
Ok will push an update |
…ake sure the continuation is actually using ExecuteSynchronously
221bcfe
to
7966971
Compare
Done |
@JoshLove-msft pushed as you requested. Now the title of the PR is no longer correct. Should I reword to say Processor improvements? |
Sure! |
/azp run net - servicebus - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
Previously this code was passing the enum
TaskContinuationOptions.ExecuteSynchronously
to the state parameter on the Continuation method which doesn't have the desired effect ;)I wasn't entirely sure whether it should actually pass
_handlerCts.Token
but I assumed it is deliberate this way. Instead of using the array overload which allocates an array, I'm switching over to use the overload that has two parameters (NET 5 and higher would even have one with just one parameter, but I figured we don't want to#ifdef
) and pass inCancellationToken.None
. This should be safe sinceCanBeCanceled
will returnfalse
and thus the correct internal source is createdAll SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.
Draft
mode if it is:General Guidelines and Best Practices
Testing Guidelines
SDK Generation Guidelines
*.csproj
andAssemblyInfo.cs
files have been updated with the new version of the SDK. Please double check nuget.org current release version.Additional management plane SDK specific contribution checklist:
Note: Only applies to
Microsoft.Azure.Management.[RP]
orAzure.ResourceManager.[RP]
Management plane SDK Troubleshooting
If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add
new service
label and/or contact assigned reviewer.If the check fails at the
Verify Code Generation
step, please ensure:generate.ps1/cmd
to generate this PR instead of callingautorest
directly.Please pay attention to the @microsoft.csharp version output after running
generate.ps1
. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.Note: We have recently updated the PSH module called by
generate.ps1
to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.