sgueissa
commented
4 months ago I tried again by creating a lao on dev-be1-a with the same servers as this morning (problem of connection between servers)
We can see that I'm connected to only 1 server.
Then I created a roll-call and got red toast. By looking at the console, the client sent 4 queries (one for each server)
Then the frontend received 3 error messages from the servers not connected to dev-be1-a (dev-be1-b, dev-be2-a/b) and the good result from the server that we initialy connected to.
So my guess is that the problem come first from the problem of synchronization between servers but at the same time from frontend displaying all the errors received when sending to multiple servers at the same time with at least one successful query.
Description (Actual behavior)
Many error toasts are shown on fe1 when creating an event, opening an event, casting a vote, posting a chirp etc. The action works despite the error toasts.
e.g. https://jam.dev/c/1e46e435-eb14-4ef1-96b8-fa6e2319dcd8, https://jam.dev/c/1e46e435-eb14-4ef1-96b8-fa6e2319dcd8 at 4:18
Expected behavior
The error toasts should not be shown.
How to reproduce
Do any of the actions listed above.
Version & Environment
Front-ends:
Back-ends:
Environment (as applicable):
Workaround
The system works despite the errors
Impact
User confusion
Possible root cause
Mishandling of messages by the frontend or incorrect errors sent by the server