I noticed a problem with bacon after upgrading to Rust 1.85.0.
If I run bacon (built with previous stable version) on a crate it seemingly hangs before rendering bacon's tui. I can't exit it by pressing q, but SIGINT (Ctrl+C) works.
It can sort-of get it unstuck if I run cargo build in a different terminal. (I have a target-dir configured in ~/.cargo/config.toml, so each crate build needs to coordinate file locks). If I start two bacons in different terminal windows, it hangs for a while, but then suddenly both of them become unstuck? Once it has reached the point of rendering the tui it seems to work fine.
While writing the text above I rebuilt bacon using Rust 1.85.0 and the problem seems to have gone away. The bacon tui comes up instantly as it usually does.
Unsolving this because the problem isn't really gone.
I don't know why this keeps happening, but it looks like the first time, after a reboot,bacon is run it will hang. Sometimes one can wait it out, and it'll eventually unblock and run. Once it gets to that point, it appears to keep running without issue. So after a reboot, it needs to be "warmed up" in some manner.
However, it seems to work this way on a per-crate basis -- even though I have a common target-dirset up in ~/.cargo/config.toml.
I also tried to run bacon on a ramfs drive, and there it works immediately without delay. Maybe there's are some locking issue with APFS volumes on macOS 15.3? I have yet to upgrade to 15.3.1 (will do that later tonight), but will report back if it improves the situation.