in reply to Missing 'in reply to...' And 'in thread....'

The same thing happened to me with Re: Dark Mode for AM? a week ago -- I posted it, it turned up blank without an "in reply to". I added back in my content, then considered it for reparenting... Then I noticed that kcott's Re^2: Larger profile pic than 80KB? (posted right after mine) was also empty without "in reply to", and I was thinking about considering that second post as well... but a few minutes later (I thought before a janitor would have had time to reparent mine), mine did have "in reply to" correctly, and when I rechecked kcott's, it was fixed as well, so I concluded that it was just something slow/stuck on the server that eventually finished. I /msg'd the janitors to ignore my consideration. I later noticed my posts janitation history said erzuuli had changed the consideration status -- and I don't know whether that was from the reparenting or from my /msg after it had already found its parent.

When I saw the same symptoms in hippo's post a few days ago (and because it had been long enough from the post that if it was just a slow server, it would have resolved itself), I /msg'd the gods to let them know there might be an intermittent bug, because it doesn't seem to be just a one-time server fluke, like I assumed with my and kcott's posts last week.

Replies are listed 'Best First'.
Re^2: Missing 'in reply to...' And 'in thread....'
by kcott (Archbishop) on Oct 28, 2023 at 20:12 UTC

    I've noticed that slowness quite a few times; most recently with my last post, "Re^3: Listing out the characters included in a character class [v5.38]", which I just posted some minutes ago. It's quite long and took a few previews to fix minor typos: these all occurred in a resonable time. When I hit create, I had to wait minutes for anything to happen. That sort of thing has occurred on quite a few occasions over the last week or so.

    Also, when going back just now to get the node_id for linking, I see the timestamp is completely wrong. It shows "Oct 28, 2023 at 15:42 AEDT". The timezone, AEDT, is correct; but it's just after 7am on 29th Oct here. I don't know if that's related or helps with troubleshooting.

    — Ken