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
{{ message }}
This repository has been archived by the owner on Aug 22, 2018. It is now read-only.
Depending on the network conditions, a transaction may not get mined for a while and time out with the error:
Error: Transaction was not mined within 50 blocks, please make sure your transaction was properly send. Be aware that it might still be mined!
Since this is a soft error, it usually just means that the transaction will process successfully later. But this messes with the .getStats feature which uses the return receipt to track when a transaction was claimed or executed. We can add an 'Attempted' and/or 'Incomplete' column to the table to reflect that a transaction was sent but didn't complete successfully.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Depending on the network conditions, a transaction may not get mined for a while and time out with the error:
Since this is a soft error, it usually just means that the transaction will process successfully later. But this messes with the .getStats feature which uses the return receipt to track when a transaction was claimed or executed. We can add an 'Attempted' and/or 'Incomplete' column to the table to reflect that a transaction was sent but didn't complete successfully.
The text was updated successfully, but these errors were encountered: