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

[close #345] build: fix client-java dependency #344

Merged
merged 1 commit into from
May 30, 2023

Conversation

pingyu
Copy link
Collaborator

@pingyu pingyu commented May 30, 2023

What problem does this PR solve?

Issue Number: close #345

Problem Description: build: bulk load build failed

What is changed and how does it work?

Code changes

  • No code

Check List for Tests

This PR has been tested by at least one of the following methods:

  • Unit test
  • Integration test

Side effects

  • No side effects

Related changes

  • No related changes

To reviewers

Please follow these principles to check this pull requests:

  • Concentration. One pull request should only do one thing. No matter how small it is, the change does exactly one thing and gets it right. Don't mix other changes into it.
  • Tests. A pull request should be test covered, whether the tests are unit tests, integration tests, or end-to-end tests. Tests should be sufficient, correct and don't slow down the CI pipeline largely.
  • Functionality. The pull request should implement what the author intends to do and fit well in the existing code base, resolve a real problem for TiDB/TiKV users. To get the author's intention and the pull request design, you could follow the discussions in the corresponding GitHub issue or internal.tidb.io topic.
  • Style. Code in the pull request should follow common programming style. (For Go, we have style checkers in CI). However, sometimes the existing code is inconsistent with the style guide, you should maintain consistency with the existing code or file a new issue to fix the existing code style first.
  • Documentation. If a pull request changes how users build, test, interact with, or release code, you must check whether it also updates the related documentation such as READMEs and any generated reference docs. Similarly, if a pull request deletes or deprecates code, you must check whether or not the corresponding documentation should also be deleted.
  • Performance. If you find the pull request may affect performance, you could ask the author to provide a benchmark result.

(The above text mainly refers to TiDB Development Guide. It's also highly recommended to read about Writing code review comments)

Signed-off-by: Ping Yu <yuping@pingcap.com>
@pingyu pingyu changed the title build: fix client-java dependency [close #345] build: fix client-java dependency May 30, 2023
@codecov
Copy link

codecov bot commented May 30, 2023

Codecov Report

Merging #344 (a210c73) into main (73d4378) will decrease coverage by 0.1701%.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@               Coverage Diff                @@
##               main       #344        +/-   ##
================================================
- Coverage   61.0648%   60.8948%   -0.1701%     
================================================
  Files           240        240                
  Lines         20285      20317        +32     
================================================
- Hits          12387      12372        -15     
- Misses         6778       6824        +46     
- Partials       1120       1121         +1     
Flag Coverage Δ *Carryforward flag
br 60.5320% <ø> (ø) Carriedforward from 73d4378
cdc 61.0627% <ø> (-0.2493%) ⬇️

*This pull request uses carry forward flags. Click here to find out more.

see 16 files with indirect coverage changes

@pingyu pingyu merged commit 1ac96c5 into tikv:main May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

build: bulk load build failed
3 participants