This is extremely helpful; thank you, Noam. I'm not in a position to make any promises, but I will add my efforts to get issues such as these at least not forgotten. Lucio. On Fri, May 17, 2024 at 8:47 PM Noam Preil wrote: > I would _love_ a complete list of known issues. > > What I'm aware of: > > - IIRC ORCLOSE doesn't work properly (visible as acme leaving temporary > files around after exiting) > - At least one deadlock remaining > - Syncs are not atomic, so a crash can render the system unbootable if > e.g. termrc was being written to disk. I've seen this repeatedly. > - It's not just non-atomic; the resulting state is usually an empty > file. Conjecture: blocks are being allocated, the file points at the new > blocks, the old data has not been copied yet. > - Multiple bugs in the file system checker. Nothing that messes with > data integrity, thankfully! I have needed multiple passes though, as a > single run does not fully clean up the file system. (Noticed this one > when cleaning up after the go failures :P) > - Also seen a deadlock while running `check fix` in the console > while > loading the file system, I think, but I don't remember for sure. > > I've almost certainly run into more than this. I run into fossil bugs > probably once every two or three months and usually haven't bothered > noting them down because I don't lose data when they happen and they're > rare enough I haven't bothered investigating most of them yet. > -- Lucio De Re 2 Piet Retief St Kestell (Eastern Free State) 9860 South Africa Ph.: +27 58 653 1433 Cell: +27 83 251 5824 ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tad3dc0c93039a7d2-M1d60f39156fbc7c3af05537d Delivery options: https://9fans.topicbox.com/groups/9fans/subscription