Alexander
24086cc744
BlueDoc covering 6 critical resilience fixes with TDD flow: - 2.9: RwLock → parking_lot (poison-free locks) - 2.2: Panic hook with tracing integration - 3.7+2.7: systemd ExecStopPost + stale mount cleanup - 2.10: sd_notify READY/STOPPING - 2.1: Signal handling via spawn_mount2 + tokio signals Each with: stubs → RED tests → implementation → GREEN verify. ~5 days estimated, exact files and code patterns specified.
Organising a music library can be a hassle. With the wealth of online stores all providing music tagged in various formats, it can be a nightmare to unify them all. This is where beetFs comes in. Derived from beets, beetFs presents a FUSE filesystem that is based on your tags. Modifying the tags within the beetFs mountpoint will not change the data on the hard disk, merely update the beet database. When an application requests a music file from within the beetFs mountpoint, beetFs provides tag information from its own database, instead of from the original file, but music data from the on-disk location. This enables completely transparent modification of tags within an audio file with no change to the underlying on-disk data.