We declared this fixed in the changelog of 0.23.5 today. I'm not sure if that's the preferred way to hand workarounds or we should keep this open since it's not yet fixed.
I'm leaning toward keeping this open and wait for the full fix. The 0.23.5 changelog has several such points of confusion that need retrospective clarification anyway.
We declared this fixed in the changelog of 0.23.5 today. I'm not sure if that's the preferred way to hand workarounds or we should keep this open since it's not yet fixed.
I'm leaning toward keeping this open and wait for the full fix. The 0.23.5 changelog has several such points of confusion that need retrospective clarification anyway.