This past month has been mainly focused on fixing bugs reported by others since we officially released version 2.0.0 at the beginning of the month. Fortunately, due to extensive testing prior to our release of 2.0.0, the reported issues have been fairly mild.
However, FreeDV Reporter did go down during Activity Day weekend (likely due to having a larger than usual number of users logged in). Since this was hosted on a virtual machine, I increased the amount of RAM allocated to it to help prevent this problem from occurring again. There was also a Linux-specific bug in the built-in FreeDV Reporter client that was partly caused by the SocketIO server libraries in used. Basically, it was considering users “connected” much earlier than it should have, and because of this it was processing multiple events simultaneously on different threads (one for each of the events the FreeDV application sends to the server to synchronize itself). This simultaneous handling of messages triggered race conditions during display of updates, causing overall weird behavior and random assertion failure popups. Fortunately some minor code changes on the server side eliminated most of the problem, with much of the rest of the problem going away once 2.0.1 is released and users upgrade to it.
For this coming month, I’m hoping to wrap up 2.0.1 and potentially work on some other RADE V2 tasks (time permitting, of course). I’m also set to give a few Zoom talks about FreeDV over the next few months to go along with the one I recently gave for the Front Range 6 meter group.
More information can be found in the commit history below:
(Note that all commit logs above were generated with the following command line:)
git log --author="member@email" --after "Month 1, 2025" --before "Month 31, 2025 23:59:59" --all