I reported the following issue upstream, where it was marked as resolved. Since it persists, this shall track it locally.