-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am constantly recieving old backlog #245
Comments
If you didn't enable |
I didn't set |
I can reproduce this here, as well. I've now enabled DisableAutoView and will see how that behaves / feels like. |
I've also got bitten by this and did some further debugging. This is definitely a mattermost issue, they don't update the channel even though we send this event (and we don't receive an error). To fix this you can just drop a message in the channel that's replaying it and delete the message again. |
Per 42wim#245, we can't trust that Mattermost has updated the last viewed for channel. Instead, we save this locally and use that for replaying of logs. Useful for when experiencing flaky network causing matterircd to reconnect.
* Fixed logging in with personal access token * Save last viewed at state and use for replaying logs Per #245, we can't trust that Mattermost has updated the last viewed for channel. Instead, we save this locally and use that for replaying of logs. Useful for when experiencing flaky network causing matterircd to reconnect. * Fixed using defer in range loops * Also make the map
Since update of mattermost to last version (5.9.0) I am recieving old backlog in my irc client. Even when I stop running of matterircd and spawn the process again and then connect with my irc client to matterircd I am recieving backlog in channels that I have already read multiple times.
Example:
Matterircd version: 0.19.2
The text was updated successfully, but these errors were encountered: