As per my comment on another thread, I’ve had several instances of comments appearing only after I have commented on a thread. In the example above I read through the entire thread, knew some info and posted it. Then when scrolling back up I notice @dmt has already provided that information. This has occurred several times, and enough that I now know it’s not me.
Does discourse not display every single comment on a thread in some circumstances, and if so how do I make sure it displays them all? I’ve not had this issue on other discourse forums.
There was 12 hours between the posts though, so it wasn’t a case of the other post being created as I was composing mine. Regardless, I’ll try hard refreshing the page after opening a new post and see if it makes a difference.
Maybe it a case of split or merged topics and moved post? Posts were on the forum but in another topic. A moderator moves/merges something that was posted earlier. You post, that forces a refresh of the page and you see the merge?
Which topic was it, maybe some mod can check the logs and proof that theory.
The issue is on line 21 of /etc/grub.d/60_memtest86+ using --target=hints_string. (Also /etc/grub.d/60_memtest86+-efi)
If you run grub-probe --target=hints_string [memtest86-image] it will give you the same error.
I thought it was logged as an issue in the memtest86+ repo but I can’t find it. I’ll log it.
EDIT: Apologies I see @dmt has already posted this info. Can anyone tell me why I didn’t see this comment until after I had posted? I make sure to scroll through and read everything before commenting and this has happened a few times now where comments don’t display until after I’ve commented also.
Edit2: I created a new thread for this: Not all comments on a thread displayed until after I comment
Hitting F5 is often needed here too. Sometimes edits to a thread don’t show properly until I do, in particular when having merged, say, 4 or 5 consecutive posts, where the page then only displays part of the action until I reload it.
Browser caching. You must keep in mind that the so-called real-time nature of Discourse isn’t actually real-time.
It is dynamic content, and it will refresh its state when you post a reply, but your browser may have different ideas on how urgently it needs to refresh the page for you. Posting a reply yourself typically triggers a cache refresh for yourself, but not necessarily for someone else.
Many browsers have memory usage optimizations these days — I know for one that chromium does, but I suspect firefox does too — and this is actually what throws a spanner in the works on account of the (semi-)real-time experience.
