Closed xhebox closed 5 months ago
Attention: 1 lines
in your changes are missing coverage. Please review.
Comparison is base (
c72f4e0
) 55.76% compared to head (76a0297
) 55.76%.:exclamation: Current head 76a0297 differs from pull request most recent head 891f79e. Consider uploading reports for the commit 891f79e to get more accurate results
Files | Patch % | Lines |
---|---|---|
components/playground/instance/tiproxy.go | 0.00% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
/lgtm
/approve
@xhebox: Your PR was out of date, I have automatically updated it for you.
/lgtm
Timeline:
2024-01-31 03:27:07.902101216 +0000 UTC m=+1536069.466398922
: :ballot_box_with_check: agreed by kaaaaaaang.2024-01-31 07:16:39.33685722 +0000 UTC m=+1549840.901154920
: :heavy_multiplication_x::repeat: reset by ti-chi-bot[bot].2024-01-31 07:59:24.857260746 +0000 UTC m=+1552406.421558450
: :ballot_box_with_check: agreed by kaaaaaaang./approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: kaaaaaaang
The full list of commands accepted by this bot can be found here.
The pull request process is described here
What problem does this PR solve?
If user sets TLS for PD endpoints, then tiproxy or etcd/client/v3 is not able to use TLS since
http://...
is passed to etcd client. Check https://github.com/etcd-io/etcd/blob/main/client/v3/internal/endpoint/endpoint.go#L90-L118. However, when onlyhost:port
is passed, the TLS config will be used.Check List
Tests
Code changes
Side effects
Related changes
Release notes: