So it seems to be a bug if 3.22.18 that was fixed in 3.22.19. From their git log, I see nothing obviously obvious though.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.