this is a known, presumably harmless bug we're not sure on the cause of which was first encountered three days ago. i'll copy and paste what i said there since it still applies exactly from what we can tell:
as far as we can tell it doesn’t create reports, so don’t worry about that part. we’re obviously not sure what’s causing this but i’ve passed it on to our grand list of things to keep an eye on so hopefully it’ll get looked at next week.
should be able to get a look at it this week. may also be a lemmy bug, in which case we'll then report it