Incorrect backend status after receiving seats about bet HOT 4 CLOSED

Just reproduced again. @sg777

Steps

Tested on Vultr nodes

1. Connect Player1 node
2. Connect Player2 node
3. Choose a SEAT for player1, all ok
4. Choose s SEAT for player2
5. Received warning: 0 for player2, see screenshot

Logs

dcv.txt
player1.txt
player2.txt

Screenshots

Player1

Player2

from bet.

This issue has been fixed in the latest commits.

from bet.

@piggydoughnut if this issue is resolved, and you confirmed it is, then please close it.

from bet.

You see in the player2 logs, tx is waiting to commit, since the tx is not committed the BE is sending the warning:0 saying that BE is not ready yet. It's not any error of the sort.

Below is the enum that declares the warning:

enum bet_warnings { 
backend_not_ready = 0, 
seat_already_taken, 
insufficient_funds, 
table_is_full 
};

Whenever you receive any of these warnings, please make sure to convey to the user accordingly.

from bet.