What you're referencing was a separate bug in 1.12.0. Haven't seen the release notes for 1.12.1 that was just pushed up a few hours ago, but I'm guessing it's been addressed.
What you're referencing was a separate bug in 1.12.0. Haven't seen the release notes for 1.12.1 that was just pushed up a few hours ago, but I'm guessing it's been addressed.