Thanks for finding this, now fixed by 2985caa9ee0029932680fc8f354a35492d18fe9a
This and similar bugs you've found are due to my adding asserts to code where my limited imagination did not think the situation could come up, but wanted to be sure of that, and not to blindly forge ahead getting a wrong answer. You have found a bunch where it was a syntax error that I my imagination didn't realize, and one (I think it was only one) where it was legitimate syntax that I overlooked. Now there are just a couple of these asserts left.
#Sat, 14 Nov 2015 11:06:02 -0800Karl Williamson <email@example.com> - Status changed from 'open' to 'pending release'
#Sun, 10 Jan 2016 06:26:15 -0800mauke- <firstname.lastname@example.org> - Status changed from 'pending release' to 'resolved'
#Sun, 10 Jan 2016 06:26:16 -0800mauke- <email@example.com> - Fixed In 5.22.1 added