Closed MyonKeminta closed 1 day ago
Hi @MyonKeminta. 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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cfzjywxk, hawkingrei, you06
The full list of commands accepted by this bot can be found here.
The pull request process is described here
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 73.4645%. Comparing base (
1c059a1
) to head (87f59a0
). Report is 8 commits behind head on master.
🚨 Try these New Features:
What problem does this PR solve?
Issue Number: close #57348
Problem Summary:
What changed and how does it work?
After #57050 , the safety check on stale read ts is made strict, making sure that the stale read ts never exceeds that PD has allocated.
However there seems still exists some test code that have some unsafe usage of stale read (such as reading at
now
). For these usages, the read ts has chance to exceed PD's max allocated ts, causing the ts validation failed.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.