That link claims the issue is fixed, yet it’s still happening in 4.22.3
if I change that to a single variable the error goes away
