[Citadel Development] Re: I'm in ur VM, running FreeBSD

2023-08-29 Thread IGnatius T Foobar
Yet another status update! With some sleep under my belt and a thankfully slow day at work I've been able to poke around a little more. Uncensored crashed a couple of times last night but I think it was because of a null pointer bug I somehow introduced. Turning off the indexer

[Citadel Development] Re: I'm in ur VM, running FreeBSD

2023-08-29 Thread IGnatius T Foobar
Yeesh. It's nearly 2:00am and I still haven't figured out the deadlock problem. But I can make it appear pretty reliably by doing these things together: 1. loadtest, with 3 threads 2. while true ; do ./sendcommand tdap ; sleep 1 ; done I also have a room on the test system that

[Citadel Development] Re: I'm in ur VM, running FreeBSD

2023-08-28 Thread IGnatius T Foobar
Yecch. The new code has a deadlock problem. The DB is rock solid though. On it.

[Citadel Development] Re: I'm in ur VM, running FreeBSD

2023-08-28 Thread IGnatius T Foobar
Oh, and in case I didn't make it abundantly clear: the remaining backend decoupling work is complete, and work on more modern backends can begin soon. LMDB? MariaDB? SeattleCloud Hosted DB? You name it, we'll be able to do it.

[Citadel Development] Re: I'm in ur VM, running FreeBSD

2023-08-28 Thread IGnatius T Foobar
Ok, I've got my FreeBSD system installed and have begun making changes to fix any problems that came up. I am also now running Uncensored on 'git master' (commit 6960933711b8353ad5cddcc17994db670911a1dc) as of right now. When it comes to dealing with database corruption, in the words of

[Citadel Development] Re: I'm in ur VM, running FreeBSD

2023-08-28 Thread IGnatius T Foobar
Ok, I've got my FreeBSD VM set up and will give the Citadel build a shot today. \