Update `aiohttp` to version 3.8.5 and `requests` to version 2.31.0,
and vendor their respective dependencies. Add all the new dependencies
to the various required site virtualenv requirements files.
Differential Revision: https://phabricator.services.mozilla.com/D188904
What we are doing in this bug is adding the ability to get motionmark ramp scores for just firefox
Motionmark has issues with other browsers, which is why we are starting with just firefox for now
Differential Revision: https://phabricator.services.mozilla.com/D188120
This contains a micro-optimization that fixes the performance
regression.
Also miri fixes and such, and a drain_filter implementation.
Differential Revision: https://phabricator.services.mozilla.com/D188756
To increase the integration between color and calc it is nescessary to
vendor the current cssparser-color library into Gecko where all the calc
functionality lives.
Differential Revision: https://phabricator.services.mozilla.com/D188216
As of bug 1719535, libm is vendored, so we don't need to pull it out of
packed_simd anymore, and that was the last remaining difference between
upstream and our fork.
Differential Revision: https://phabricator.services.mozilla.com/D187413
This commit vendors the latest changes to the Suggest and Remote
Settings Rust components.
1. From the `application-services` source tree, I ran
`./tools/update-moz-central-vendoring.py ../m-c` to update the
revisions in the m-c source tree.
2. I added the Remote Settings component UDL file to
`toolkit/components/uniffi-bindgen-gecko-js/mach_commands.py`, and
updated `toolkit/components/uniffi-bindgen-gecko-js/config.toml` to
call the `RemoteSettings` constructor on the main thread. The
Suggest component uses the `RemoteSettingsConfig` type in its
public API, so we must generate bindings for the Remote Settings
component.
3. From the m-c source tree, I ran `./mach uniffi generate` to update
the generated UniFFI bindings.
Differential Revision: https://phabricator.services.mozilla.com/D187559
Support the Pipewire videotransform meta via the already existing shared
infrastructure. This is needed for mobile devices which often have a 90
degree rotated camera - which is likely the reason there is already
support in the shared code paths.
Upstream commit: dc4c019c62abefc09e4903abea44bc36f3427452
Differential Revision: https://phabricator.services.mozilla.com/D183652
This cherry-picks the `spa_meta_videotransform` needed for upcoming
webrtc patches, avoiding a full sync for easier porting.
Upstream commit: 01b2552b71e7475b4c9f893c43e07e8f1044a50b
Differential Revision: https://phabricator.services.mozilla.com/D183651
This can be helpful in various situations, such as debugging with an
unrestricted Pipewire socket or for downstream projects like
B2G/Capyloon. Additionally it will help once we move from the camera
portal to the more generic device portal.
This is intended to get upstreamed but would be nice to carry downstream
already.
Original patch by Fabrice Desré <fabrice@desre.org>
Upstream commit: a717c7ada811411e31bd7308168b4dbee5b956fa
Differential Revision: https://phabricator.services.mozilla.com/D183650
This is part 1 of 3 and vendors the [suggest component](https://github.com/mozilla/application-services/tree/main/components/suggest) from
application-services into m-c. `suggest` depends on `remote_settings`, so it was
also vendored. Part 2 will generate JS bindings with uniffi.
This is my first time doing this so I'll explain how I generated this patch in
case I did something wrong:
1. I manually added `suggest` to the following files:
* Top-level `Cargo.toml`
* `toolkit/library/rust/shared/Cargo.toml`
* `toolkit/library/rust/shared/lib.rs` -- I followed the example of `tabs`,
not sure if `suggest::uniffi_reexport_scaffolding!()` is necessary
2. I ran `./mach vendor rust`
That's it, there were no errors or problems.
Differential Revision: https://phabricator.services.mozilla.com/D187323
The changes from 1830945 were landed upstream in v116's release branch as
commit 04ee24493d as a cherry-pick of dcf600d7a5. dcf600d7a5's no-op file
will be created automatically when running build_no_op_commits.sh at the
proper time so a tracking file for it is not needed yet.
Differential Revision: https://phabricator.services.mozilla.com/D187489
This avoids numerical stability problems when computing the
miter pointer intersection when the lines are nearly parallel.
Differential Revision: https://phabricator.services.mozilla.com/D187057
Karl Tomlinson
Connor Sheehan
Gabriele Svelto
andrej
Nicolas Silva
John Schanck
Mike Hommey
Emilio Cobos Álvarez
Andrew Halberstadt
Yury Delendik
Jan-Erik Rediger
Sandor Molnar
Tiaan Louw
Ryan VanderMeulen
Erich Gubler
Updatebot
Ben Hearsum
Lina Butler
Robert Mader
Logan Rosen
Zhao Jiazhong
Drew Willcoxon
Michael Froman
Jeff Muizelaar
stransky
Sebastian Hengst
Willy R. Vasquez
Henri Sivonen