Skip to content

[-> #739] Special handling for unsubscribe calls. #752

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

Merged
merged 2 commits into from
May 3, 2022

Conversation

jsdw
Copy link
Collaborator

@jsdw jsdw commented May 3, 2022

Also point at Tokio 1.16 since we use a method added then.

This avoids acquiring a permit for unsubscribe calls, so that they always make it past the subscription limit.

(I wonder whether they should also avoid any resource claiming, too?)

This is to be merged into #739 if we're happy with the approach!

Todo:

  • Add a test to check that unsubscribe methods make it past the limit.
  • Check/fix proc macro stuff?

@jsdw jsdw requested a review from a team as a code owner May 3, 2022 10:41
@jsdw jsdw changed the title Special handling for unsubscribe calls. [-> #729] Special handling for unsubscribe calls. May 3, 2022
@jsdw jsdw changed the title [-> #729] Special handling for unsubscribe calls. [-> #739] Special handling for unsubscribe calls. May 3, 2022
@jsdw jsdw merged commit 7ac1fd6 into na-fix-729 May 3, 2022
@jsdw jsdw deleted the jsdw-unsubs-are-unique branch May 3, 2022 10:55
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.

1 participant