You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To mitigate #2261 we need to figure out the status of ST in case we get the "already in cache" error from Tenderdash.
To do so we need to check either ST in mempool (using dashpay/tenderdash#963) or in blockchain (/tx RPC call) or pass it to CheckTx (considering it's invalid) and return validation errors to the client. There might be a case when CheckTx will pass. It's a buggy condition meaning there is inconsistency between CheckTx and block processing logic or some issue in tenderdash. We should log such errors and return the internal error to the client.
The text was updated successfully, but these errors were encountered:
To mitigate #2261 we need to figure out the status of ST in case we get the "already in cache" error from Tenderdash.
To do so we need to check either ST in mempool (using dashpay/tenderdash#963) or in blockchain (/tx RPC call) or pass it to
CheckTx
(considering it's invalid) and return validation errors to the client. There might be a case whenCheckTx
will pass. It's a buggy condition meaning there is inconsistency betweenCheckTx
and block processing logic or some issue in tenderdash. We should log such errors and return the internal error to the client.The text was updated successfully, but these errors were encountered: