Hi! Thanks for looking into this. Can you elaborate why you filed this on 26.4.8 and not latest 26.4.10?
Builds are passing. Thus tests indicate that there is no issue. What is the broken thing exactly and since tests are passing, how will we verify that the broken thing is fixed or still broken?
