Some threads still showing as unread after reading about cyclescape

[nikolai-b]

Ha, I didn't mean to suggest you really thought it was magic, just that sometimes these problems crop up and magically fix themselves. I've no idea why this is happening but I've update the background worker and re-deployed 🤞 that fixes it.

[nikolai-b]

Closing as I think this was related to a deployment.

[mvl22]

Thanks for reporting. Could you give a specific thread number, so we have an example to look at?

[soundplusfury]

So of course, I report it and then as if by magic (not magic - tech stuff from somewhere) it's fine again. As you were.

[nikolai-b]

Sadly not by magic. @mvl22 in our error reporting we were getting NameError: uninitialized constant ThreadRecorder::ThreadView and (ActiveJob::DeserializationError: Error while trying to deserialize arguments: uninitialized constant Message) for some reason in the background jobs (resque). I restarted resque on the server and it seems to be fixed but I'm not sure what was happening.

[soundplusfury]

(I know it isn't magic. I was being daft.) But to report thread 892 is doing the same thing in Firefox now.

[soundplusfury]

Also thread 5261. It will clear after about three refreshes, I think, so it's not quite so bad, but still odd.

[soundplusfury]

Add thread 5115 too. This one's being pretty stubborn. I'll stop there.