Not quite the right spot … but that specific bug has a different thread and looks like devs are on it.
