I've actually not had it stay off for this long before; typically after two refreshes they all pop back, so i'm a little more optimistic this time. i'm sure they'll come back, based on history, but still...
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Cannot mark as read one of my watched threads [MERGED]
- Thread starter UliBaer
- Start date
- Sort by reaction score
We think we have identified a fix. Things should be working properly for now, though a permanent solution will take a bit more work.
Feedback appreciated on whether things are indeed working properly for people.
Feedback appreciated on whether things are indeed working properly for people.
That's interesting. I've had a couple threads manifest this issue over the past weekend. Different strokes for different folks.
Had 10+ un-read threads (at this machine).
Marked all as read as of now (mix between clicking "Mark as read" and actually reading them).
Now, let's see.
Marked all as read as of now (mix between clicking "Mark as read" and actually reading them).
Now, let's see.
I was able to mark all my threads read. This appears to be fixed. Excellent work. Will report back if anything unexpected happens.
This is positive news. Can you give us some details on what's happening?
Looking good for me at the moment. Hopefully you have squashed that bug for good!
Thank You, it appears to be fixed, though I'll reserve final judgement for a couple weeks
Would be good if you could share some details of that fix.
I marked everything read this morning and so far, it's working as expected. Thanks!
It's been working properly for me on all the previously problematic threads, and has been since you posted the notice of the fix.
Thanks.
It's a database syncing issue. We've temporarily fixed it by dropping a server, so a permanent fix to bring it back online will likely require rebuilding some things.
Thanks for the clarification! That is most certainly not something that we armchair debuggers would have ever figured out. 🤣
Thanks for the update, appreciated.
So, when that server comes back online, with or without the fix, can you let us know so we can test the reoccurrence of this issue or not?
I'll try to remember, but if the issue does come back, you'll know. As should I, since I had a dozen affected threads myself.
The thing I'm curious about is why "Mark Read" at the Forum level made the issue disappear. Well, not really disappear, but it did actually reset the "read" markers for all the threads in that forum, something that "Mark Read" at the Thread level failed to do. In other words, what's different about Forum-level and Thread-level "Mark Read" that would lead to the different behavior?