Closed RichardWallis closed 2 years ago
More than happy to locally test a patch for this...
@RichardWallis sorry for the long delay on this. It appears that we missed fixing this the first time when processing the 336/337/338 $b (we fixed it only for processing of $a). Strange that it didn't come up for you before! Please feel free to reopen if this does not fix it for you.
This fix has been merged to the default branch and will be part of v1.7.1, probably released next week.
From previous issue:
Although the fix appeared in some pre-v1.7.0 versions it didn't make it into the shipped version of v1.7.0
So, having upgraded I am back to my error state. :-(