Tim Culverhouse e7a51f5524 backends: send MessageInfoError on header fetching error ... When an error is encountered fetching a header, the backends respond with a type.Error worker message. On receipt of this message, the UI deletes all pending headers. The headers are all requested again as they remain on the screen, resulting in an infinite request loop - and an infinite logging loop. The user only ever sees the spinner unless they check the logs. A previous commit intended to fix this, however it introduced a regression where any message that was part of the fetch request would also be marked as erroneous. This commit is reverted with commit 2aad2fea7d36 ("msgstore: revert 9fdc7acf5b48"). Send an erroneous message info message from the backend when an error is encountered for a specific UID. Fixes: 01f80721e2 ("msgstore: post MessageInfo on erroneous fetch") Signed-off-by: Tim Culverhouse <tim@timculverhouse.com> Acked-by: Robin Jarry <robin@jarry.cc>		2022-09-25 11:54:27 +02:00
..
messages.go	cache: fetch flags from UI	2022-09-20 21:10:35 +02:00
sort.go	Add sorting functionality	2019-09-20 14:56:02 -04:00
thread.go	mark: (un)mark message threads	2022-08-22 09:30:37 +02:00
thread_test.go	lint: apply new formatting rules	2022-08-01 10:44:52 +02:00
worker.go	backends: send MessageInfoError on header fetching error	2022-09-25 11:54:27 +02:00