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

Gnodev to give useful info about failing replays #2867

Open
moul opened this issue Sep 27, 2024 · 0 comments
Open

Gnodev to give useful info about failing replays #2867

moul opened this issue Sep 27, 2024 · 0 comments

Comments

@moul
Copy link
Member

moul commented Sep 27, 2024

Gnodev can sometimes replay transactions and sometimes cannot. We should optimize this information for readability when used locally by developers.

Another important need for this feature is to enhance the failing report for portal loops. This will allow us and any other loop to update their gnoland deps (binary, examples/ folder, etc) while maintaining a clear list of issues related to failed transactions.

Developers will then have the option to ignore the warnings or address them.

In our specific case as portal loop maintainers, we want to create a simple process where a PR can be merged even if it breaks the loop (a.k.a, no CI). However, we also need meaningful logs to assist us in "patching" the history.

The use cases I have in mind are:

Related with #2866
See #2862 (comment)

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

No branches or pull requests

1 participant