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

Make use of CompletionStage#handle instead of whenComplete. #3222

Closed
wants to merge 1 commit into from

Conversation

He-Pin
Copy link
Contributor

@He-Pin He-Pin commented Oct 8, 2022

#3221
For Main branch

@He-Pin He-Pin requested a review from a team as a code owner October 8, 2022 08:39
@pivotal-cla
Copy link

@He-Pin Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

1 similar comment
@pivotal-cla
Copy link

@He-Pin Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@He-Pin He-Pin closed this Oct 8, 2022
@He-Pin He-Pin reopened this Oct 8, 2022
@pivotal-cla
Copy link

@He-Pin Thank you for signing the Contributor License Agreement!

@simonbasle
Copy link
Member

simonbasle commented Oct 10, 2022

I will either merge this after or include this in the forward-merge of sister PR #3221

@simonbasle
Copy link
Member

@He-Pin no, I'll merge the other PR into 3.4.x, merge 3.4.x into main and use the code from this one to solve the resulting merge conflict.

@He-Pin
Copy link
Contributor Author

He-Pin commented Oct 10, 2022

I see, thanks for the detail.

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.

None yet

3 participants