Skip to content
This repository has been archived by the owner on Mar 24, 2023. It is now read-only.

refactor: handling godwoken error #512

Merged
merged 6 commits into from
Sep 9, 2022

Conversation

keroro520
Copy link
Contributor

@keroro520 keroro520 commented Aug 31, 2022

Main contribution:


Others:

@keroro520 keroro520 self-assigned this Sep 2, 2022
packages/api-server/src/cache/data.ts Outdated Show resolved Hide resolved
packages/api-server/src/methods/error.ts Outdated Show resolved Hide resolved
packages/api-server/src/methods/gw-error.ts Outdated Show resolved Hide resolved
packages/api-server/src/methods/modules/eth.ts Outdated Show resolved Hide resolved
@keroro520
Copy link
Contributor Author

Updated:

  • @RetricSu All of your review suggestions have been applied at the new commit a7abecd . Thanks

@classicalliu
Copy link
Contributor

Can hardhat parse error message after error.data.message removed ?

@keroro520
Copy link
Contributor Author

Can hardhat parse error message after error.data.message removed ?

If HardHat fails after error.data.message removed, it would cause godwoken-tests fail. Am I right?

Godwoken-tests has several cases that trigger revert-error: https://github.com/nervosnetwork/godwoken-tests/pull/179/files
So my answer is YES.

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

Successfully merging this pull request may close these issues.

[v1.3] hardhat cannot parse eth_call failed information
4 participants