It makes chasing back the context of an interaction difficult if not impossible.
What’s going on there? The system seems to get lost at times.
Maybe your interlocutor pushed the wrong button.
Be sure you respond to the post in question by hitting the top Reply, not the larger, general ‘Reply’ and then entering the ID of the poster you’re responding to in the text body.
Worked a long time in software development. This is a system flaw.
There have been times that I know I hit the correct REPLY but the system failed to record it. It’s inconsistent. The system should be made user friendly if not foolproof.
I did look at one of the five responses you had entered when I read your post above, and it started with ‘@’ and a username. From this, I deduced you had simply responded to the thread, and not the specific post. Was I mistaken in that? Because I’ve been here since the site opened, and I’ve never observed the behaviour you’re reporting.
I edited the post when I noticed and then added the user name it. The issue could be platform/browser dependent. Possibly a race condition.
I’m sure you mean ‘rare condition’ 
No race condition. It’s a computer thing. I can explain it to you if you like.
Do! I’ve never heard the terminology (and I’ve been a techwriter).
Posts failing to indicate which post it was in response to
Which posts?
A race condition is a bug that happens when two or more threads access a shared resource without proper serialization.
So say you have multiple processors running in the same address space. I have spent a couple decades in such an environment. You have a counter in memory. Two processors try to increment that simultaneously. The way to do that is read it, add one, and write it back. So they each read it (5 say) and both write the 6 back. Now the count is off since it should be 7. That can cause a fatal crash.
Proper protection in that case is probably to protect the counter with a spin lock so the first processor finishes its write before the second one can read the value. The race is to be the first to get the lock.
No, I don’t think the problem with the post reference is a race condition or other bug. It is probably the user error that you pointed out in your first reply. WeSee may have a point about it being too easy to use the wrong button.
1 Like
Actually the “race” would be for thread1 to complete the write before any competing thread can read it. The lock is placed to force any competing thread to wait on the read until the write has been completed thus preventing the “race”.
WeSee made no such point.
Have you noticed the behaviour again since?
One would think a mature system such as the Discourse platform would be adequately protected against such bugs.
When you have two or more processes running concurrently, you can have a race condition. There are more than a few different types of race conditions.
Techwriter? Let’s say that there is a tech repair manual that requires both text and illustrations that needs to be published ASAP. The text and illustrations are to be produced concurrently. The illustrations seem likely to take longer than the text. A decision is made to publish as soon as the text is ready with any missing illustrations to be sent later in an addendum. The “race” will be for illustrations to finish by the time the text is ready.
Webpages often utilize concurrent processing.
Got the following response from Google AI when I asked it about Chrome:
Yes, race conditions can absolutely result in elements being left out or completely missing from a webpage. This usually happens when the logic that creates or shows an element depends on another process that hasn’t finished yet.
I ran this past gemini.google.com which responded in part:
If the Reply button is “not operating properly,” it is likely a synchronization issue between the browser’s local cache and the Discourse server. In Discourse’s architecture, the most effective “fix” is usually a hard refresh (Ctrl+F5) to force the Ember.js engine to re-sync the UI state with the current server permissions and topic status.
Actually I primarily started this thread because of difficulty I have had in following the discussions of others in a given thread. Sussing out who was responding to whom.
In my experience, about 30-40% of software developers are marginally competent at best. Imagine that would be even higher with webpage developers. Especially when multiple platforms/browsers are supported.
However, I see that in this thread, at least, all your replies to date are correctly attributed, are they not?
It’s not necessarily an issue with the Reply button not operating properly.
The nature of race conditions is that they often only intermittently occur. So just because it seems to be behaving in this thread, is neither here nor there.
Plus it may only be an issue with Android/Chrome.