Update: This is actually really a bug. It is likely a nodejs bug that started to occur since nodejs 16.
We've implemented a workaround which we are testing now.