According to the upstream bug report, this is fixed in version 0.12.4 however I am unsure of the exact commit that resolved it. Although I haven't encountered this issue yet, i'm going to mark it as triaged as upstream, have essentially confirmed it with the version we ship.
According to the upstream bug report, this is fixed in version 0.12.4 however I am unsure of the exact commit that resolved it. Although I haven't encountered this issue yet, i'm going to mark it as triaged as upstream, have essentially confirmed it with the version we ship.