neiljp
commented
1 year ago @jonjensen Thanks for another report :+1:
Are you receiving a lot of popups, or is this over an extended time? As the popup states, these issues are normally not a problem, as you've likely seen if using ZT afterwards. In any case, unless you have state stored in eg. the single draft, it's safe to simply close and restart ZT - it'll fetch state from the server each time, by default a lot less than the web client.
In terms of why this is happening...
This sequence of calls (same each time?) should only be happening when you read a message - on any client, since ZT receives an event to say that it's happened.
I suspect the issue here is that a message is being marked read in a stream that ZT isn't aware you're subscribed to, at least with its current data model.
My prime suspect is if you've subscribed to a stream in another client, while ZT was open, and read messages in that stream outside of ZT, ZT tries to process the associated read-message events and is getting confused.
Many established ZT users likely don't run into these issues, since their subscribed streams are less likely to change over time.
In any case, there are events ZT can handle for adding and removing subscriptions, and we have a WIP PR for this.
jonjensen
Sorry to be a pest, but I've had two cases of another error happen today. This time zulip-term doesn't crash, but it shows a TUI modal on the screen:
When I press escape it goes away and the program keeps working seemingly fine.
The contents of that log file:
Both times this happened to me I wasn't actively using that terminal window, but I may have typed something odd passing it as I changed virtual desktops in Awesome window manager.
The terminal I'm using is Alacritty.