Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

History of failed transactions buried #6950

Closed
wbt opened this issue Aug 2, 2019 · 1 comment
Closed

History of failed transactions buried #6950

wbt opened this issue Aug 2, 2019 · 1 comment

Comments

@wbt
Copy link
Contributor

wbt commented Aug 2, 2019

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):
image

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.

@tmashuang
Copy link
Contributor

tmashuang commented Nov 10, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants