Closed you06 closed 2 weeks ago
Hi @you06. Thanks for your PR.
PRs from untrusted users cannot be marked as trusted with /ok-to-test
in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all
.
I understand the commands that are listed here.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 54.6901%. Comparing base (
2343c54
) to head (618cfbc
). Report is 3 commits behind head on master.
/retest
@you06: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
/merge
@you06: We have migrated to builtin LGTM
and approve
plugins for reviewing.
Please use /approve
when you want approve this pull request.
The changes announcement: LGTM plugin changes
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: AilinKid, ekexium, wshwsh12
The full list of commands accepted by this bot can be found here.
The pull request process is described here
In response to a cherrypick label: new pull request created to branch release-8.1
: #53015.
What problem does this PR solve?
Issue Number: close #53011 ref #50215
Problem Summary:
What changed and how does it work?
The client-go patch let the pipelined DML abort once the max ttl is exceeded, and avoid writing useless locks which slow down GC.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.