b9a2e62602
Fixes #10340 Fixes a race condition when receiving a message in a channel that doesn't exist yet (for example in a delete 1-1 chat). What happens is that the status-go signal contains both the message and the chat. Both are handled by different services, so there was a race between the two of them. If the chat service handled the chat first, then the message was added correctly, but in the case of the message service handling it first, it would try to add the message to a chat that doesn't exist yet, so it wouldn't work. I also cleaned the ChatUpdateArgs by removing the messages arg that was not used anywhere and also was a bit counter-intuitive. Why did a Chat arg have messages? |
||
|---|---|---|
| .. | ||
| app | ||
| app_service | ||
| backend | ||
| dev | ||
| constants.nim | ||
| contributing.md | ||
| nim_status_client.nim | ||
| nim_windows_launcher.nim | ||