Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Conversation

xster
Copy link
Member

@xster xster commented Sep 29, 2021

@flutter-dashboard
Copy link

This pull request was opened from and to a release candidate branch. This should only be done as part of the official Flutter release process. If you are attempting to make a regular contribution to the Flutter project, please close this PR and follow the instructions at Tree Hygiene for detailed instructions on contributing to Flutter.

Reviewers: Use caution before merging pull requests to release branches. Ensure the proper procedure has been followed.

@flutter-dashboard
Copy link

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

@xster xster changed the title Cherry-pick #28846 into flutter-2.6-candidate.11 Cherry-pick #28846 and #28743 into flutter-2.6-candidate.11 Sep 29, 2021
@flutter-dashboard flutter-dashboard bot added the embedder Related to the embedder API label Sep 29, 2021
@@ -21,10 +21,10 @@
<key>CFBundleVersion</key>
<string>1.0</string>
<key>MinimumOSVersion</key>
<string>8.0</string>
Copy link
Member Author

Choose a reason for hiding this comment

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

@jmagman I imagine it's ok but just double checking, both #28783 and #28743 touched this line. Neither of which are in the cherry-pick base. Cherry picking this directly is ok?

Copy link
Member

Choose a reason for hiding this comment

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

Is 4460688 in this branch? Otherwise this doesn't need to be cherry-picked. I can't tell what the parent SHA is from the GitHub UI.

Copy link
Member

Choose a reason for hiding this comment

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

Ah, it's branched off 5b81c6d (that makes sense). Just cherry pick #28783 then, it's more focused and lower risk. Thanks @xster!

Copy link
Member Author

Choose a reason for hiding this comment

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

Ah, you're saying #28783 addresses b/200635527 too? Done

Copy link
Member

Choose a reason for hiding this comment

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

Exactly, sorry I wasn't clear! 😄

Copy link
Contributor

@christopherfujino christopherfujino left a comment

Choose a reason for hiding this comment

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

branch and source commits LGTM.

@jmagman
Copy link
Member

jmagman commented Sep 29, 2021

The jcenter failures were fixed by #28777, which only touches test files, if you want to cp that too. Or you can keep re-running until it deflakes.

@xster
Copy link
Member Author

xster commented Sep 30, 2021

Thanks for the tip Jenn!

@xster xster added the waiting for tree to go green This PR is approved and tested, but waiting for the tree to be green to land. label Sep 30, 2021
@fluttergithubbot
Copy link
Contributor

This pull request is not suitable for automatic merging in its current state.

  • The status or check suite Linux Web Framework tests has failed. Please fix the issues identified (or deflake) before re-applying this label.

@fluttergithubbot fluttergithubbot removed the waiting for tree to go green This PR is approved and tested, but waiting for the tree to be green to land. label Sep 30, 2021
Copy link
Member

@jmagman jmagman left a comment

Choose a reason for hiding this comment

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

This is still cherry picking #28743 instead of the more focused #28783, but I think that should be fine.

@xster xster force-pushed the flutter-2.6-candidate.11 branch from e65db1a to 705c2ad Compare September 30, 2021 21:29
Copy link
Member

@jmagman jmagman left a comment

Choose a reason for hiding this comment

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

Still LGTM

@@ -21,10 +21,10 @@
<key>CFBundleVersion</key>
<string>1.0</string>
<key>MinimumOSVersion</key>
<string>8.0</string>
Copy link
Member

Choose a reason for hiding this comment

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

Exactly, sorry I wasn't clear! 😄

@jmagman
Copy link
Member

jmagman commented Sep 30, 2021

The jcenter failures were fixed by #28777, which only touches test files, if you want to cp that too. Or you can keep re-running until it deflakes.

It's still failing, also may need #28738.

@google-cla
Copy link

google-cla bot commented Sep 30, 2021

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no and removed cla: yes labels Sep 30, 2021
@google-cla
Copy link

google-cla bot commented Sep 30, 2021

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

1 similar comment
@google-cla
Copy link

google-cla bot commented Sep 30, 2021

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@xster xster added cla: yes and removed cla: no labels Sep 30, 2021
@xster xster merged commit 8bd90a7 into flutter:flutter-2.6-candidate.11 Oct 4, 2021
@xster xster deleted the flutter-2.6-candidate.11 branch October 4, 2021 20:52
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants