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

fix backport of #14310 #14316

Merged
merged 1 commit into from
Aug 25, 2022
Merged

fix backport of #14310 #14316

merged 1 commit into from
Aug 25, 2022

Conversation

lgfa29
Copy link
Contributor

@lgfa29 lgfa29 commented Aug 24, 2022

must was not imported in the file yet in release/1.3.x and Config.Copy() was added in #14139, which was not backported.

I wasn't sure how to deal with Copy(), I thought of just copying the function over to release/1.3.x but it seemed unnecessary for the test.

CI errors.

Copy link
Member

@tgross tgross left a comment

Choose a reason for hiding this comment

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

LGTM.

Kind of unfortunate that the backport assistant doesn't wait for green tests, but we'd be waiting all day if it did. 😀

@lgfa29
Copy link
Contributor Author

lgfa29 commented Aug 25, 2022

Kind of unfortunate that the backport assistant doesn't wait for green tests, but we'd be waiting all day if it did. 😀

Yeah, I was thinking about it the other day. Slow runs + flaky tests would probably mean a lot more of CI babysitting 😅

@lgfa29 lgfa29 merged commit 582e868 into release/1.3.x Aug 25, 2022
@lgfa29 lgfa29 deleted the fix-backport-14310 branch August 25, 2022 13:51
@lgfa29 lgfa29 added backport/1.2.x backport to 1.1.x release line and removed backport/1.2.x backport to 1.1.x release line labels Aug 25, 2022
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants