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
See reproduction steps on this issue to start. When originally observed, the error was not an [intentionally induced] Out Of Gas error but rather [an unintentional] intrinsic gas too low; this might matter.
Once the history becomes available to view, scroll down to see more. Lots of transactions are confirmed, and as you scroll back through the history, you get to past dates, and it seems like everything more recent than these past dates (above it in the history) succeeded. However, that's not true. If you keep scrolling down (not using the vertical scroll bar which doesn't go far, but the scroll wheel), you can see a newer transaction near the bottom of the list, without a number in front of the date, which failed.
Example screenshot (Chrome on Windows):
Expected behavior
Transactions are in order by datetime with the most recent being the most easily visible at the top of the list, instead of having a recent failed transaction buried below a month or more of confirmed transactions.
The text was updated successfully, but these errors were encountered:
This seems to have been fixed in #8564. I reproduced with a on-chain failed tx to a contract and it seems to organize by date/time and nonce. I'll mention #9053 for when the overall design of on-chain failures and provider failures gets sorted out.
See reproduction steps on this issue to start. When originally observed, the error was not an [intentionally induced] Out Of Gas error but rather [an unintentional]
intrinsic gas too low
; this might matter.Once the history becomes available to view, scroll down to see more. Lots of transactions are confirmed, and as you scroll back through the history, you get to past dates, and it seems like everything more recent than these past dates (above it in the history) succeeded. However, that's not true. If you keep scrolling down (not using the vertical scroll bar which doesn't go far, but the scroll wheel), you can see a newer transaction near the bottom of the list, without a number in front of the date, which failed.
Example screenshot (Chrome on Windows):
Expected behavior
Transactions are in order by datetime with the most recent being the most easily visible at the top of the list, instead of having a recent failed transaction buried below a month or more of confirmed transactions.
The text was updated successfully, but these errors were encountered: