Reto Brunner 1687e558d3 notmuch/maildir: remove double emit of the dirinfo ... There was some bug which could be worked around by double emitting an event. However that proofed to be brittle: We send the first message here from the worker goroutine: a5553438/item/worker/maildir/worker.g= o#L306 Then Tick() is waked in the main goroutine and calls ProcessMessage: a5553438/item/widgets/account.go (L100) ProcessMessage in the main goroutine reads types.Message state with msg.getId() and msg.InResponseTo(): a5553438/item/worker/types/worker.go#= L74-76 Meanwhile in the worker goroutine we call PostMessage for a second time with a pointer that points to the *same* previous message that ProcessMessage is reading: a5553438/item/worker/maildir/worker.g= o#L306 The second PostMessage call makes writes to message while ProcessMessage in the main goroutine is possibly reading: a5553438/item/worker/types/worker.go#= L59 This led to a data race in the event loop Reported-By: Wagner Riffel <w@104d.net>		2021-04-28 07:54:16 +02:00
..
lib	notmuch: remove gc close hooks	2020-12-02 09:06:34 +01:00
eventhandlers.go	Add missing notmuch build tags	2020-02-26 21:46:31 +01:00
events.go	Add missing notmuch build tags	2020-02-26 21:46:31 +01:00
message.go	notmuch: don't read the full file into memory	2021-02-08 08:40:07 +01:00
worker.go	notmuch/maildir: remove double emit of the dirinfo	2021-04-28 07:54:16 +02:00