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.

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

Merged
merged 4 commits into from
Feb 9, 2022
Merged

Conversation

danielmarbach
Copy link
Contributor

@danielmarbach danielmarbach commented Feb 9, 2022

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 in CancellationToken.None. This should be safe since CanBeCanceled will return false and thus the correct internal source is created

All SDK Contribution checklist:

This checklist is used to make sure that common guidelines for a pull request are followed.

  • Please open PR in Draft mode if it is:
    • Work in progress or not intended to be merged.
    • Encountering multiple pipeline failures and working on fixes.
  • If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
  • I have read the contribution guidelines.
  • The pull request does not introduce breaking changes.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

SDK Generation Guidelines

  • The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
  • The *.csproj and AssemblyInfo.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] or Azure.ResourceManager.[RP]

  • Include updated management metadata.
  • Update AzureRP.props to add/remove version info to maintain up to date API versions.

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:

    • Do not modify any code in generated folders.
    • Do not selectively include/remove generated files in the PR.
    • Do use generate.ps1/cmd to generate this PR instead of calling autorest 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:

      `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`
    

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.

@ghost ghost added Service Bus customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Feb 9, 2022
@ghost
Copy link

ghost commented Feb 9, 2022

Thank you for your contribution @danielmarbach! We will review the pull request and get back to you soon.

@ghost ghost added the Community Contribution Community members are working on the issue label Feb 9, 2022
@check-enforcer
Copy link

check-enforcer bot commented Feb 9, 2022

This pull request is protected by Check Enforcer.
For more information about how to run a pipeline against this pull request, see this.

@JoshLove-msft
Copy link
Member

/azp run net - servicebus - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@JoshLove-msft
Copy link
Member

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

@danielmarbach
Copy link
Contributor Author

Ok will push an update

…ake sure the continuation is actually using ExecuteSynchronously
@danielmarbach
Copy link
Contributor Author

Done

@danielmarbach
Copy link
Contributor Author

@JoshLove-msft pushed as you requested. Now the title of the PR is no longer correct. Should I reword to say Processor improvements?

@JoshLove-msft
Copy link
Member

@JoshLove-msft pushed as you requested. Now the title of the PR is no longer correct. Should I reword to say Processor improvements?

Sure!

@JoshLove-msft
Copy link
Member

/azp run net - servicebus - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@danielmarbach danielmarbach changed the title Use the right overload for the ContinueWith in the receiver manager make sure the continuation is actually using ExecuteSynchronously Processor improvements Feb 9, 2022
@JoshLove-msft JoshLove-msft enabled auto-merge (squash) February 9, 2022 21:57
@JoshLove-msft JoshLove-msft merged commit d03e3f5 into Azure:main Feb 9, 2022
@danielmarbach danielmarbach deleted the fix-continuation branch February 9, 2022 22:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Community Contribution Community members are working on the issue customer-reported Issues that are reported by GitHub users external to the Azure organization. Service Bus
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants