Caching: current status
-
It might have been related, I am happy to say that it is if it means its all fixed now. So far I have not seen a problem with the unread list, its in perfect order, anyone noticed a problem? @J-Hilk you usually hit it easily, have you noticed anything?
Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
-
It's looking indeed. Fingers crossed !
-
It might have been related, I am happy to say that it is if it means its all fixed now. So far I have not seen a problem with the unread list, its in perfect order, anyone noticed a problem? @J-Hilk you usually hit it easily, have you noticed anything?
-
Update.
Been monitoring it for a couple of hours now, apparently no caching issue!
🤞👍
Seems good!
-
Woo hoo! I am calling it fixed then :)
Thanks to everyone for putting up with it for so long! Things should be a lot more stable and so on going forward now.
Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
-
Woo hoo! I am calling it fixed then :)
Thanks to everyone for putting up with it for so long! Things should be a lot more stable and so on going forward now.
@AndyS
Woo hoo indeed! So far I believe I see correct reply counts from overview page, correct vote counts, and I haven't seen the "let's go to default serif font" that sometimes affects pages. It remains to be seen whether the most unwelcome effect --- losing edits you make to your posts --- has gone for good too. However, overall looks positive!Which means, I'll have to buy you that beer... :)
Thanks for all your work!
-
Considering how long it took I think we can safely say the beer is negated, but if we are ever in the same room I would happily accept and likewise be willing to buy one too :)
Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
-
Considering how long it took I think we can safely say the beer is negated, but if we are ever in the same room I would happily accept and likewise be willing to buy one too :)
-
Considering how long it took I think we can safely say the beer is negated, but if we are ever in the same room I would happily accept and likewise be willing to buy one too :)
Seems to be solved for me, at least in the broad strokes.
nitpick: I had an upvote that didn't take immediately (i.e. after click), however it did update properly after a page reload.Read and abide by the Qt Code of Conduct
-
Seems to be solved for me, at least in the broad strokes.
nitpick: I had an upvote that didn't take immediately (i.e. after click), however it did update properly after a page reload.@kshegunov said in Caching: current status:
Seems to be solved for me, at least in the broad strokes.
nitpick: I had an upvote that didn't take immediately (i.e. after click), however it did update properly after a page reload.That's interesting, it might be a bug in NodeBB, or even a local cache issue. But I am hoping it was a fluke and not a sign that the problem still exists in some form.
Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
-
@kshegunov said in Caching: current status:
Seems to be solved for me, at least in the broad strokes.
nitpick: I had an upvote that didn't take immediately (i.e. after click), however it did update properly after a page reload.That's interesting, it might be a bug in NodeBB, or even a local cache issue. But I am hoping it was a fluke and not a sign that the problem still exists in some form.
@AndyS said in Caching: current status:
That's interesting, it might be a bug in NodeBB, or even a local cache issue. But I am hoping it was a fluke and not a sign that the problem still exists in some form.
In any case, it was so minor that I wouldn't put much though into it anyway. Thanks for the work on this (and in general) and happy holidays!
-
@kshegunov said in Caching: current status:
Seems to be solved for me, at least in the broad strokes.
nitpick: I had an upvote that didn't take immediately (i.e. after click), however it did update properly after a page reload.That's interesting, it might be a bug in NodeBB, or even a local cache issue. But I am hoping it was a fluke and not a sign that the problem still exists in some form.
