> it is not fixed in 0.9.1 if I did not overlooked something
Reviving this one, though I hope we can re-resolve it quickly. It seems the problem may still persist in 0.9.1? Or did I miss something and was this tested and resolved as well?
> it is not fixed in 0.9.1 if I did not overlooked something
Reviving this one, though I hope we can re-resolve it quickly. It seems the
problem may still persist in 0.9.1? Or did I miss something and was this tested
and resolved as well?