This version includes the new
`SuggestStoreBuilder#remoteSettingsBucketName()` API.
This commit also makes the chrome JS-exposed `SuggestStoreBuilder`
methods synchronous.
Differential Revision: https://phabricator.services.mozilla.com/D201774
Now that WGPU has upgraded its dependency on `libloading`, we can
finally remove our fake `libloading` 0.7 crate! 🙌
I found this audit and review easiest to do by generating a diff. that
ignores whitespace-only differences. In my case, I did the following:
```
git diff --ignore-space-at-eol --ignore-space-change --ignore-all-space --ignore-blank-lines
```
Differential Revision: https://phabricator.services.mozilla.com/D209290
This crate is only used by the crash reporter and geckodriver, and
geckodriver is only used in testing (if I understand correctly).
In the future we will upstream changes to the zip crate which more
gracefully handles the case which they are trying to cover.
Differential Revision: https://phabricator.services.mozilla.com/D209752
This crate is only used by the crash reporter and geckodriver, and
geckodriver is only used in testing (if I understand correctly).
In the future we will upstream changes to the zip crate which more
gracefully handles the case which they are trying to cover.
Differential Revision: https://phabricator.services.mozilla.com/D209752
Update:
- UniFFI to 0.27.1
- Glean to 59.0.0
- App-services to a recent version
This removes the need for the goblin build hack, although we still have
duplicate versions of goblin since UniFFI is ahead of the moz-central
version. I think that should be easy to resolve as a follow-up.
Updating uniffi-bindget-gecko-js based on upstream changes:
- Clone objects before lowering them
(https://github.com/mozilla/uniffi-rs/pull/1880)
- Use u64 for the RustBuffer length and capacity field
(https://github.com/mozilla/uniffi-rs/pull/1978)
I didn't implement the new callback interface VTable code. Instead I
simply disabled the one fixture that tests it. I'd rather implement
https://bugzilla.mozilla.org/show_bug.cgi?id=1888668 first, since that
will simplify the process a bunch. The only real-world use-case for
callbacks that I know of is Mark's logging changes, but that will
require implementing trait interfaces anyways so I'd rather wait than
write a bunch of C++ code that we then throw away.
Differential Revision: https://phabricator.services.mozilla.com/D206130
Update:
- UniFFI to 0.27.1
- Glean to 59.0.0
- App-services to a recent version
This removes the need for the goblin build hack, although we still have
duplicate versions of goblin since UniFFI is ahead of the moz-central
version. I think that should be easy to resolve as a follow-up.
Updating uniffi-bindget-gecko-js based on upstream changes:
- Clone objects before lowering them
(https://github.com/mozilla/uniffi-rs/pull/1880)
- Use u64 for the RustBuffer length and capacity field
(https://github.com/mozilla/uniffi-rs/pull/1978)
I didn't implement the new callback interface VTable code. Instead I
simply disabled the one fixture that tests it. I'd rather implement
https://bugzilla.mozilla.org/show_bug.cgi?id=1888668 first, since that
will simplify the process a bunch. The only real-world use-case for
callbacks that I know of is Mark's logging changes, but that will
require implementing trait interfaces anyways so I'd rather wait than
write a bunch of C++ code that we then throw away.
Differential Revision: https://phabricator.services.mozilla.com/D206130
Update:
- UniFFI to 0.27.1
- Glean to 59.0.0
- App-services to a recent version
This removes the need for the goblin build hack, although we still have
duplicate versions of goblin since UniFFI is ahead of the moz-central
version. I think that should be easy to resolve as a follow-up.
Updating uniffi-bindget-gecko-js based on upstream changes:
- Clone objects before lowering them
(https://github.com/mozilla/uniffi-rs/pull/1880)
- Use u64 for the RustBuffer length and capacity field
(https://github.com/mozilla/uniffi-rs/pull/1978)
I didn't implement the new callback interface VTable code. Instead I
simply disabled the one fixture that tests it. I'd rather implement
https://bugzilla.mozilla.org/show_bug.cgi?id=1888668 first, since that
will simplify the process a bunch. The only real-world use-case for
callbacks that I know of is Mark's logging changes, but that will
require implementing trait interfaces anyways so I'd rather wait than
write a bunch of C++ code that we then throw away.
Differential Revision: https://phabricator.services.mozilla.com/D206130
Henri Sivonen
Tamas Szentpeteri
Alex Franchuk
Lina Butler
Ben Dean-Kawamura
Iulian Moraru
John Schanck
Norisz Fay
Mark Hammond
Erich Gubler
Kershaw Chang
Nan Jiang
acseh
Mike Hommey
Emilio Cobos Álvarez
Cristian Tuns
Sandor Molnar
Nipun Shukla
Jonathan Kew
Narcis Beleuzu