Issue is still relevant for 3.6.x and this bug is actually has a workaround. Any chance to land it by 1.9.3?
Issue is still relevant for 3.6.x and this bug is actually has a workaround. Any chance to land it by 1.9.3?