Gordon Ball Sun, 07 Apr 2019 08:02:12 -0700
I can confirm this bug is still present in 0.8.10, but I don't have a clear sense of how to fix it; awaiting an upstream fix.
