Canto | Details

Wow, so three weeks since I've touched git and the world of Canto hasn't imploded. Hooray. Last month shattered some records with respect to site traffic / downloads / bandwidth / popcon installs and votes / AUR votes (basically across the board), but bug reports are still sparing. In fact yesterday was the first actual bug that required a commit to fix.

You can see a write up w/ workaround (for those that use the n/p keybinds in the reader and don't want to wait for release) here.

Bug in long-running instances

One report notes that for Canto instances that have been running for a long while (a couple of days, in a screen session), the client stops updated and starts dominating the CPU.

I've managed to track this down to a call to the multiprocessing module that decides to choke to death deep in the C code because the length of something it's attempting to write is > INT_MAX which seems... highly unlikely... I don't think the cPickle output of a feed is going to reach into the gigabytes of size....

Regardless, I'm still attempting to fix it, even if it turns out that I have to submit patches to Python itself.

Debian Maintainership

Some bad news. The long-time Canto maintainer, Daniel Baumann had to drop the package as one of his main packages, along with a number of others (like ncurses itself). Currently, Canto's maintainer is listed as Debian Q-A. If anyone would like to take over, the position is open =).

Thanks to Daniel for being such a great maintainer.

Have fun! Submit bugs!