-
Notifications
You must be signed in to change notification settings - Fork 224
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
Bug 1661539 - Add Glean to a iOS megazord build #3554
Conversation
e8ff49d
to
a50345c
Compare
Codecov Report
@@ Coverage Diff @@
## main #3554 +/- ##
==========================================
+ Coverage 69.47% 76.67% +7.20%
==========================================
Files 230 230
Lines 30879 30879
==========================================
+ Hits 21453 23677 +2224
+ Misses 9426 7202 -2224
Continue to review full report at Codecov.
|
* internally it defers to the same string implementation. | ||
* Because Glean is added as a submodule it's easier to change this occurence than it it to change the one of Glean. | ||
*/ | ||
/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm curious what the underlying conflict was here - was it swift complaining about trying to add two extension methods with the same name on the String
class?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we have the same extension to String
with the same named parameter.
I actually propose to rename it on our side (s/Rust/Glean/
) to avoid the conflict, but as I also want to submodule based on the release commit this has to be defered to the next release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks reasonable enough to me, thanks @badboy for taking this on!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great! Let's get this in a release and try it out.
@badboy do you have any other tweaks you wanted to try here, or should we merge this as-is and cut a new release?
From conversation with @garvankeeley, let's also merge #3556 before making a new release with this. |
Also could you please try re-running the dependency-list-generator script? It looks like something has gotten out of date. |
This adds the tag v32.3.0
1d864dc
to
0c1dece
Compare
I rebased on Force-pushing again to see what CI thinks. |
The pull request has been modified, dismissing previous reviews.
I've ran the exact same commands CI runs but it doesn't fail locally. |
I see similar when trying this locally :-( I'm going to go ahead and merge this and if it's still failing, I'll be better situated to fix it up locally. |
Ref #3565 for further investigation of the dependency issue. |
mozilla-mobile/firefox-ios#7303 is landed on iOS, locally I am building and running and it works well. |
This is a first try in adding Glean as a submodule to incorporate it into a iOS megazord build.
If this lands firefox iOS will also require updates (similar to the PoC in mozilla-mobile/firefox-ios@main-dev...badboy:megazord-appservices-glean)
So far this was reasonably easy and I only need 2 small Swift changes to make it work (both of which can be later mitigated on the Glean side again).
I managed to build Firefox iOS locally from this branch.
I'm not sure if having the
git submodule update
in thebuild-all-ios.sh
script is actually enough, but I think that one is run on all iOS platforms, so it's good enough?cc @travis79, @Dexterp37, @mdboom for Glean.
Pull Request checklist
automation/all_tests.sh
runs to completion and produces no failures[ci full]
to the PR title.