there is an upgrade with a partial fix on 2.6.3
but is not completely fixed, at least I still see the error.
1 Like
I updated to 2.6.3 but I see the error as well
Could you point to the issue on github if possible? Thanks
It will be fixed in 2.6.4:
4 Likes