Yet another topic that should not have been closed

As @Saoiray stated before, that thread is still open:

The Github issue is active as of today and it looks like there’s a literal fix for the exact issue you’re having already being implemented:

Unless there’s something we’re all missing I’m going to go ahead and close this thread as well.