Yep, same issue reported here:
Unfortunately the fix missed the release train for 8.3.8 but should be in 8.3.9.