On Wed, Apr 1, 2026 at 4:08 PM Gary Guo <[email protected]> wrote: > > Okay, I see what the comments mean now. Perhaps squash this to the previous > commit?
This one was mostly to ensure the workaround was not needed anymore, i.e. it is more "optional" than the other. In fact, we may want to just not have neither of the patches, i.e. we could just remove the workaround given the timelines of the branches -- please see my reply on the previous one on this. Cheers, Miguel
