fidzu : thunderbird

Github Link

The following changes have been pushed to bugzilla.mozilla.org:

• Bug 2087000 - Sometimes phab "last modified" timestamp updates without actual changes to the revision
• Bug 2081860 - Migrate Bug REST resource to native Mojo API: bug objects (get, search, create, update, possible_duplicates, history)
• Bug 2070239 - Add DB-backed tests for flag-event bugmail recipient selection (prev-status tie-break, flag-type cc_list)
• Bug 2082543 - Clean up after the REST-to-Mojo migration: shared helpers in Bugzilla::API::V1::Util

Discuss these changes in the BMO Matrix Room

1 post - 1 participant

Read full topic

03 Nov 2026 10:05pm GMT

Bugs resolved in Moz-Phab 2.24.0:

• bug 2078583 moz-phab reorg --force can fail part way and leave the Phabricator stack tangled
• bug 2082342 Move lando warnings knowable at submit time to moz-phab
• bug 2086803 Resolve each command's flags and config into a frozen options object
• bug 2087605 moz-phab will break with upcoming jj release 0.47
• bug 2087877 Remove args from the VCS layer
• bug 2088194 Update hard-coded Lando-dev urls to point to Fastly WAF fronted domains

Discuss these changes in #engineering-workflow on Slack or #Conduit Matrix.

1 post - 1 participant

Read full topic

03 Nov 2026 2:49pm GMT

The rustup team has published a new point release of rustup, 1.29.3.

Rustup is the recommended tool to install Rust, a programming language that empowers everyone to build reliable and efficient software.

What's new in rustup 1.29.3

This new patch release has fixed some minor regressions over the previous one:

• Fixed "Illegal instruction" error on certain x86_64 CPUs without SSE4.1. pr#5162

• Fixed "lock() not supported" error on Solaris. pr#5167

Further details are available in the changelog!

How to update

If you have a previous version of rustup installed, getting the new one is as easy as stopping any programs which may be using rustup (e.g. closing your IDE) and running:

$ rustup self update

Rustup will also automatically update itself at the end of a normal toolchain update:

$ rustup update

For this particular release, if you have encountered any issues during self-update, you may try to update rustup manually by following the steps below:

1. Download the corresponding rustup-init binary for your platform.
2. Make double sure that no other rustup processes are running.
3. Replace your existing rustup binary with the downloaded rustup-init renamed to rustup.
   • As a reminder, this binary is often located at $HOME/.cargo/bin/rustup, or $CARGO_HOME/bin/rustup if you have overridden the $CARGO_HOME environment variable.

If you don't have it already, you can get rustup from the appropriate page on our website.

Rustup's documentation is also available in the rustup book.

Caveats

Rustup releases can come with problems not caused by rustup itself but just due to having a new release.

In particular, anti-malware scanners might block rustup or stop it from creating or copying files, especially when installing rust-docs which contains many small files.

Issues like this should be automatically resolved in a few weeks when the anti-malware scanners are updated to be aware of the new rustup release.

Thanks

Thanks again to all the contributors who made this rustup release possible!

03 Nov 2026 12:00am GMT