Closed Defined2014 closed 8 hours ago
Hi @Defined2014. 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 74.9283%. Comparing base (
4442d49
) to head (71a3663
). Report is 22 commits behind head on master.
🚨 Try these New Features:
/retest
@Defined2014: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mjonss, tangenta
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/retest
@Defined2014: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
/retest
@Defined2014: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
/retest
@Defined2014: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
In response to a cherrypick label: new pull request created to branch release-8.5
: #57622.
What problem does this PR solve?
Issue Number: close #57588
Problem Summary:
Didn't set
isUpdate = true
before, so it will use the last value in datum as_tidb_rowid
which caused primary key duplicate.If we don't do this during add columns,
len(r) == len(cols)
always equal to true, so it's safe.What changed and how does it work?
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.