Due to bug #321307 I've been restarting choqok a lot these days and I've noticed that when I restart I will often have some additional unread tweets show up down in the depths of my timeline. These are not new tweets since the crash (or tweets whose read status wasn't saved properly due to the crash); often they're several hours old. Some but not all of them are retweets. I've only seen this when choqok restarts; I've never seen a normal timeline refresh while it's running cause such old tweets to appear. I don't know if this is due to something on Twitter's side or something on choqok's side. I'm mentioning it because part of bug #321307 for me vaguely smells like some sort of data race and this might be another symptom of it. I'm using the latest git choqok on x86_64 Fedora 18 via a hand-built RPM. Reproducible: Sometimes
Some tweets are missing in the timeline after being processed (maybe a list effect). Sometimes when updating the TL some tweets appear then the number of unread tweets decrease and some of those tweets dissappear, never to be shown again.
(In reply to comment #1) > Some tweets are missing in the timeline after being processed (maybe a list > effect). > Sometimes when updating the TL some tweets appear then the number of unread > tweets decrease and some of those tweets dissappear, never to be shown again. Do you have any configured filter!? Check here: Tools -> Configure Filters
No filter except show simple response about me checked (sorry I'm translating from French so it might not be the exact message). I'm using lists + timeline and some dissappearing messages seemed to be response to listed messages. The 'conversation' I'm sure of was a message listed in 2 lists and the response to this message from a friend has dissapeared (after blinking during the Update timelines).
Could this be happening when I'm subscribed to someone on multiple lists ?
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
I'm afraid that I no longer use Choqok so I can't test this bug to see if it's still present.
I moved away from Choqok too as this was a kind of blocker to me.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
As with when this was asked in 2018, I no longer use Choqok so I can't say whether this bug is still present.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
same from me, I moved away from choqok :(
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!