Peter Wagenet

Were you able to get tests running? If so, can you write some for this?

@chadhietala I believe it's been present since at least 3.4.6 as we discovered it in our app which is stuck on 3.4 for unrelated reasons.

@locks I just rebased. Looks like CI still fails.

Rebased again just now.

@tgvrssanthosh were you able to look into this?

@tgvrssanthosh Just checking in on this. It continues to be unsafe. @bmish should we turn off the auto-fix until we can investigate further?

@tgvrssanthosh Here's a demo of the issue: https://limber.glimdown.com/edit?c=AYjmCsGcAIBsEsBuBTaAHATsx9kHcAoeAWzQHsMAXaAYTNLIDtlHqAzDe6AcgAFQExYsgwB6AMb1yzVtwDcRBlWgBBDBgCGATwAKnAB5boHLn2TEARiNEb120ZjKH5i8soDe0UMmoBfY5zEPLzmVmIAFsiwaCIuBMj6btQAJshsGgCusNTisBqQMAASUbBkAOoUsMnQCZQsyTB0DDLU7gTQ0LaaRgC8qna6BloAdOJYGnUAFJ6SrCyUAFzQANoAjAA0AEzrAMwAutC%2BAJQK7dAAPHWkeXUAfGcdAOI%2B0AAMS%2B7u3tSU4fCQwy62mgACJXiDfL5zhYMPcOk8Xmx4BhIJQAPIWcDIcSLaCfb7QX7-QEDUFIlHozHYygQ3xnc6iK5oG7Ie50kDAAhAA&format=glimdown @bmish it's not EmberData specific. It's specific to anything using `Ember.Array` that is not an actual native array.

I know this is way late, but is it possible for you to write tests for this?

@falcn Huh, that's quite strange. It works fine for me on a USB-C > DP cable. Must be something different when not going over a USB-C AltMode.

@falcn I'd guess that the hub may be the issue in this case.