Transactions failing due to supposedly missing objects which actually exist

[awelc]

trafficstars

This was reported on Discord and also discussed internally. It seems like this may be a problem with two transactions trying to access the same shared object at the same time - one will succeed but the other one will see an out-of-date object version and fail.

From what I understand, we are working on a fix that would make this workflow more reliable.

We may also make the error message a bit more detailed to better explain what the problem is if/when it happens in the future.

Assigning @patrickkuo to follow up, but please feel free to reassign.

[lxfind]

Is there anything more concrete? This issue won't be actionable, unless we at least have some logs/object ids that we could look into.

[awelc]

Is there anything more concrete? This issue won't be actionable, unless we at least have some logs/object ids that we could look into.

As I mentioned in the issue description, this was reported on Discord, so the only thing we currently have is this report:

Having an error on my dapp:

Uncaught (in promise): Error: Transaction failed with the following error. Error executing transaction with request type: Error: RPC Error: Failed to execute certificate on a quorum of validators, cause by : ["Internal error - Error checking transaction input objects: [ObjectNotFound { object_id: 0x344a80ef6445c774959be1b1182132175723282e }]",

But the object does exist as you can see in the explorer. Any thoughts?

[awelc]

@lxfind, it does not look like this is happening still, and you also mentioned that some fixes have been put in for this. Could you please list PRs for these fixes here and close this issue?