Dan Nessett wrote:
After testing, it appears moving to 1.16.5 solves the
problem. Should I
file a bug against 1.16.2 and mention it is fixed in 1.16.5? This might
help those who run 1.16.x, x < 5 if, if they run into the same problem
Such bug wouldn't get any action. Bugs in 1.16.x are fixed in a new
release 1.16.y (y > x). This is already fixed, Nothing we can do to
solve people in old versions.