It seems like the tests can intermittently fail based on which order
they run, since some tests set the max logging level and `test_logging`
depends on info-level logs being recorded. Updated `test_logging` to
manually set it's max level. Hopefully this fixes the issue for good.
Updating the code now that fenix lives in firefox-android. This
actually simplifies things quite a bit.
Renamed the parameter from `ff-android` to `firefox-android`. I don't
think we need to abbreviate it now that it's the only branch-build parameter.
We've been getting intermittent failures for the this one. I'm pretty
sure it's because cargo runs the tests in multiple threads, but the
tests assume they are running in a single threaded environment.
Added a new crate called `rust-log-forwarder` that forwards logs to
consumers. This does basically the same thing as `rc-log`, but it uses
UniFFI. Once our consumer apps swich over to `rust-log-forwarder`, we
can remove the `rc-log` component.
This is what UniFfi expects and will start enforcing soon. When I was
testing app-services with the current code, I got errors because the
`UniFfiTag` struct was not in the crate root.
Made a bunch of things `pub` that weren't before. This seems logical,
since we're exporting those things in our UniFfi API. It also was the
simplest way to make the import work.
* fix various nimbus gradle plugin issues
* fix newline at end of file and adjust pathing for applicationServicesDir
* adjust nimbus fml cli to only include the R class in imports if it will be used
* fix clippy errors and update changelog
* Update components/support/nimbus-fml/src/backends/kotlin/gen_structs/bundled.rs
Co-authored-by: jhugman <jhugman@users.noreply.github.com>
* adjust for pr feedback
* fix formatting
---------
Co-authored-by: jhugman <jhugman@users.noreply.github.com>
* Consolidate the various types used for a "collection name" - now we
use `Cow` rather than the various `&'static str`, `&str` and `String`
used previously.
* This made it easier to clean up the `LocalCollState` state machine
to have the `Ready` state directly provide the `CollState` due to
a mismatch between `'static str` and `String` reprs of collections.
* No longer store the outgoing timestamp in an OutgoingChangeset - it was
never actually used and just creates unnecessary complexity.
* OutgoingChangsets now always supply the BSOs as they are created,
meaning less `mut` objects.
* Bonus fix to unbreak the `places-utils` example.
This discusses updating our release process so that we get code merged
into our consumers more frequently and to prepare us for a monorepo
world.
See the ADR for details.
* fix various nimbus gradle plugin issues
* update changelog
* fix newline at end of file and adjust pathing for applicationServicesDir
* set default cache dir to be root build directory
---------
Co-authored-by: jhugman <jhugman@users.noreply.github.com>
Updating to 4.5.3 and start using the official builds from zetetic.net.
This is needed for #5354. I was able to verify this one with their GPG
key so I think it should be trusted.
- Switched to using workspace dependencies, this will make future
updates much simpler
- Updated code to work with the new UniFFI crate structure
- Updated the error-support integration tests to work with the workspace
dependencies, following this advice: https://stackoverflow.com/a/71461114.
* [demo] handle_error as a proc macro
* Adds more tests
* Rework handle_error proc macro to take no arguments
* ignore rustdoc since it doesn't have expore to error_support
* Removes function signature validation
Ryan VanderMeulen
dependabot[bot]
jhugman
MatthewTighe
Sammy Khamis
Ben Dean-Kawamura
Mark Hammond
lougeniaC64
Tarik Eshaq
Julien Cristau
Julien Cristau
Charlie