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

Deletion of unused UseBackgroundThreadsForIO #846

Conversation

Pliner
Copy link
Contributor

@Pliner Pliner commented May 24, 2020

Proposed Changes

Delettion of unused property UseBackgroundThreadsForIO.

Types of Changes

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause an observable behavior change in existing systems)
  • Documentation improvements (corrections, new content, etc)
  • Cosmetic change (whitespace, formatting, etc)

Checklist

  • I have read the CONTRIBUTING.md document
  • I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
  • All tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in related repositories

@Pliner Pliner force-pushed the drop-unused-use-background-threads-for-io branch from c3680f8 to be24c05 Compare May 24, 2020 18:41
@Pliner Pliner marked this pull request as ready for review May 24, 2020 19:01
@Pliner Pliner changed the title Delete unused UseBackgroundThreadsForIO Deletion of unused UseBackgroundThreadsForIO May 25, 2020
@michaelklishin
Copy link
Member

@bording @lukebakken @stebet just to be sure: if we include this into 6.1.0, does this count as a "minor breaking API change"?

@michaelklishin
Copy link
Member

@Pliner good catch, thanks.

@michaelklishin michaelklishin merged commit dc2ba04 into rabbitmq:master May 25, 2020
@bording
Copy link
Collaborator

bording commented May 25, 2020

@bording @lukebakken @stebet just to be sure: if we include this into 6.1.0, does this count as a "minor breaking API change"?

Yes, this is a breaking change. It should not be backported to 6.x

@stebet
Copy link
Contributor

stebet commented May 25, 2020

It's a no-op but yes, breaking as removing it'll trigger a compilation error. I'd say for 6.x mark it with a [Deprecated] attribute.

@michaelklishin
Copy link
Member

Actually this was not backported to 6.x, #847 was, but I've mixed up a tab and left a comment here.

@michaelklishin michaelklishin added this to the 7.0.0 milestone May 25, 2020
@Pliner Pliner deleted the drop-unused-use-background-threads-for-io branch May 25, 2020 18:33
@lukebakken lukebakken modified the milestones: 8.0.0, 7.0.0 Mar 8, 2022
adamsitnik added a commit to adamsitnik/AspNetCore.Diagnostics.HealthChecks that referenced this pull request Nov 23, 2023
adamsitnik added a commit to Xabaril/AspNetCore.Diagnostics.HealthChecks that referenced this pull request Dec 4, 2023
* update all dependencies that don't require TFM update to latest versions

* build fix: fix xUnit1030 in the whole solution: don't use .GetAwaiter in Test projects

* build fix: stop using UseBackgroundThreadsForIO, which got deprecated and removed (it was unused), see rabbitmq/rabbitmq-dotnet-client#846 for more details

* build fix: xUnit1031: Test methods should not use blocking task operations, as they can cause deadlocks.

* update all dependencies that required TFM bump to .NET 8

* build fix: stop using .Add, use .Append instead

* run approval tests for 8, not 7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants