Skip to content
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

client: support specifying target member #7909

Merged
merged 3 commits into from
Apr 2, 2024

Conversation

rleungx
Copy link
Member

@rleungx rleungx commented Mar 13, 2024

What problem does this PR solve?

Issue Number: Ref #7905

What is changed and how does it work?

Check List

Tests

  • Unit test

Release note

None.

Copy link
Contributor

ti-chi-bot bot commented Mar 13, 2024

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • CabinfeverB
  • JmPotato

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot bot added the release-note-none Denotes a PR that doesn't merit a release note. label Mar 13, 2024
@ti-chi-bot ti-chi-bot bot requested review from HunDunDM and JmPotato March 13, 2024 06:30
@ti-chi-bot ti-chi-bot bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 13, 2024
@rleungx rleungx force-pushed the follower-handle branch 2 times, most recently from f25c245 to 0a084b3 Compare March 13, 2024 08:06
@rleungx rleungx requested review from CabinfeverB and HuSharp and removed request for HunDunDM March 13, 2024 08:07
Copy link

codecov bot commented Mar 13, 2024

Codecov Report

Merging #7909 (2eb0571) into master (f559940) will increase coverage by 0.00%.
The diff coverage is 55.00%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #7909   +/-   ##
=======================================
  Coverage   73.65%   73.66%           
=======================================
  Files         436      436           
  Lines       48503    48516   +13     
=======================================
+ Hits        35727    35737   +10     
+ Misses       9735     9727    -8     
- Partials     3041     3052   +11     
Flag Coverage Δ
unittests 73.66% <55.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

c := newClientWithMockServiceDiscovery("test-with-target-url", []string{"http://127.0.0.1:2379", "http://127.0.0.2:2379", "http://127.0.0.3:2379"})
defer c.Close()

_, err := c.WithTargetURL("http://127.0.0.4:2379").GetStatus(ctx)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we check the right follower target as well?

@@ -111,6 +111,8 @@ type Client interface {
WithRespHandler(func(resp *http.Response, res any) error) Client
// WithBackoffer sets and returns a new client with the given backoffer.
WithBackoffer(*retry.Backoffer) Client
// WithTargetURL sets and returns a new client with the given target URL.
WithTargetURL(string) Client
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to make it a request-level option rather than a client one?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have the request level option now.

@@ -56,6 +56,7 @@ func (m *mockPDServiceDiscovery) GetAllServiceClients() []ServiceClient {
return m.clients
}

func (m *mockPDServiceDiscovery) GetURL() string { return "" }
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no need add this method

@ti-chi-bot ti-chi-bot bot added the status/LGT1 Indicates that a PR has LGTM 1. label Mar 15, 2024
@rleungx rleungx requested review from JmPotato, CabinfeverB and HuSharp and removed request for CabinfeverB April 2, 2024 03:10
@ti-chi-bot ti-chi-bot bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Apr 2, 2024
@JmPotato
Copy link
Member

JmPotato commented Apr 2, 2024

/merge

Copy link
Contributor

ti-chi-bot bot commented Apr 2, 2024

@JmPotato: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

Copy link
Contributor

ti-chi-bot bot commented Apr 2, 2024

This pull request has been accepted and is ready to merge.

Commit hash: a16233c

@ti-chi-bot ti-chi-bot bot added the status/can-merge Indicates a PR has been approved by a committer. label Apr 2, 2024
Copy link
Contributor

ti-chi-bot bot commented Apr 2, 2024

@rleungx: Your PR was out of date, I have automatically updated it for you.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@ti-chi-bot ti-chi-bot bot merged commit 6fe44d7 into tikv:master Apr 2, 2024
23 of 26 checks passed
@rleungx rleungx deleted the follower-handle branch April 2, 2024 04:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants