"All accounts" shows that chan has new messages, but in the chan itself nothing is shown as new #884

New Issue

2016-07-15T22:18:42+02:00

yurivict commented

2016-07-15 22:18:42 +02:00

(Migrated from github.com)

Icon counter also shows new messages.

This is the the current rev. 8e066ea

Icon counter also shows new messages. This is the the current rev. 8e066ea

beyondmeh commented

2016-07-15 22:39:30 +02:00

(Migrated from github.com)

Can confirm this happens, even when every message has been read and trashed and there's no messages shown in the inbox.

yurivict commented

2016-07-16 17:47:34 +02:00

(Migrated from github.com)

The opposite also happens: the chan shows it has new messages but "All accounts" and icon indicator doesn't. Overall this problem became worse in 8e066ea compared to 0.6.0.

The opposite also happens: the chan shows it has new messages but "All accounts" and icon indicator doesn't. Overall this problem became worse in 8e066ea compared to 0.6.0.

PeterSurda commented

2016-07-16 22:20:13 +02:00

(Migrated from github.com)

Ok I'll look at it.

g1itch commented

2018-02-06 20:58:27 +01:00

(Migrated from github.com)

@yurivict, @keithieopia, can you please check the latest v0.6? I hope #1117 fixed it.

yurivict commented

2018-02-06 22:22:57 +01:00

(Migrated from github.com)

Sorry, I can't check now due to ETOOBUSY.

beyondmeh commented

2018-02-07 02:26:58 +01:00

(Migrated from github.com)

@g1itch I just did a fresh git clone to get 4a3f8f4 / your #1117 pull request. Thank you for taking time time to address this issue despite it's age.

IIRC, this issue on my end seemed to be intermittent but would happen at least once in 24 hours. At the time, I wasn't running 8e066ea so it wasn't as frequent as yurivict reported.

Let's give my new instance a max of 2 days running. I'm confident the issue would show up again in that time if it hasn't been successfully fixed. That said, your commit seems like pretty solid work. I see no reason why it wouldn't be fixed.

Please @ me here if I don't report back, so GitHub sends me a nag email.

@g1itch I just did a fresh `git clone` to get 4a3f8f4 / your #1117 pull request. Thank you for taking time time to address this issue despite it's age. IIRC, this issue on my end seemed to be intermittent but would happen at least once in 24 hours. At the time, I wasn't running 8e066ea so it wasn't as frequent as *yurivict* reported. Let's give my new instance a max of 2 days running. I'm confident the issue would show up again in that time if it hasn't been successfully fixed. That said, your commit seems like pretty solid work. I see no reason why it wouldn't be fixed. Please @ me here if I don't report back, so GitHub sends me a nag email.

beyondmeh commented

2018-02-07 23:44:57 +01:00

(Migrated from github.com)

I've had the client running for many hours and have gone through several rounds of new and deleted messages. It seems that the issue has been fixed thanks to thanks to @g1itch's work.

@PeterSurda, I feel this issue can be safely closed if @yurivict is still too busy to check.

I've had the client running for many hours and have gone through several rounds of new and deleted messages. It seems that the issue has been fixed thanks to thanks to @g1itch's work. @PeterSurda, I feel this issue can be safely closed if @yurivict is still too busy to check.

This repo is archived. You cannot comment on issues.