-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Expose and use async APIs for transaction commit/rollback #20694
Comments
@ajcvickers shouldn't this be in a 5.0 milestone? It seemed to have gone in for preview5... |
@roji Usually the person that commits the fix is responsible of ensuring that the issue is in the correct milestone and has the "closed-fixed" label |
Sure, am just wondering why this didn't pop up for triage up to now... |
We don't triage closed issues |
We had a few issues with closed-fixed without a milestone - fixed two of mine, pinged @ajcvickers for others. Unfortunately Github doesn't seem to support searching for issues without a certain label (closed-duplicate and all the others), so it's difficult to find everything that doesn't have a closed label but no milestone... |
GH does not properly filter things but here is the query you are looking for Plus, don't think there is any need to go further than first page as we did not assign closed-* labels before. First page end itself is reaching 2018. |
Thanks @smitpatel! |
Continuing on #9015, #15917
The text was updated successfully, but these errors were encountered: