I take that back: this is already fixed in v0.48.3argonaut, which you should be upgrading to anyway due to some critical bug fixes.
I take that back: this is already fixed in v0.48.3argonaut, which you should be upgrading to anyway due to some critical bug fixes.