This issue is now fixed in v2.287.1 which will be released at some point next week.
Thank you @mdouglass for reporting the issue.
This issue is now fixed in v2.287.1 which will be released at some point next week.
Thank you @mdouglass for reporting the issue.