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

Remove the explicit dependency on netty-tcnative-boringssl-static #583

Conversation

VinayLondhe14
Copy link
Member

As can be seen here and here, we can get the correctly matched netty and netty-tcnative versions from the netty-bom itself

@VinayLondhe14
Copy link
Member Author

/gcbrun

@codecov
Copy link

codecov bot commented Apr 1, 2022

Codecov Report

Merging #583 (908d04b) into master (6031228) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #583   +/-   ##
=======================================
  Coverage   12.67%   12.67%           
=======================================
  Files         104      104           
  Lines        4473     4473           
  Branches      511      511           
=======================================
  Hits          567      567           
  Misses       3856     3856           
  Partials       50       50           
Flag Coverage Δ
integrationtest 12.85% <ø> (ø)
unittest 12.67% <ø> (ø)

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


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 64ded94...908d04b. Read the comment docs.

@VinayLondhe14 VinayLondhe14 merged commit 42c03c2 into GoogleCloudDataproc:master Apr 1, 2022
@VinayLondhe14 VinayLondhe14 deleted the remove_tcnative_boringssl branch April 1, 2022 20:22
@VinayLondhe14 VinayLondhe14 self-assigned this Sep 15, 2022
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.

2 participants