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

Reopening: Hardhat couldn't infer error reason - random revert behaviour #4518

Closed
bibimohamed opened this issue Oct 23, 2023 · 3 comments
Closed
Assignees
Labels
status:needs-more-info There's not enough information to start working on this issue

Comments

@bibimohamed
Copy link

Version of Hardhat

2.17.2

What happened?

Exact same issue as this: #1904.

Minimal reproduction steps

#1904

Search terms

No response

@fvictorio
Copy link
Member

Hi @bibimohamed, from skimming the issue you linked, there doesn't seem to be good reproduction steps there. Can you provide a minimal reproducible example please?

@fvictorio fvictorio added status:needs-more-info There's not enough information to start working on this issue and removed status:triaging labels Oct 30, 2023
@hudeintres
Copy link

I am also running into this issue. I believe all you need to do is

  1. clone Aave's repo
  2. run the tests mulitple times using npm run test
  3. it will fail erratically with the issue linked.

As reported by others, it's extremely difficult to reproduce and isolate. I've tried adding many logs and have isolated the problem to event emssions.

@fvictorio fvictorio added status:triaging and removed status:needs-more-info There's not enough information to start working on this issue labels Nov 20, 2023
@fvictorio
Copy link
Member

@hudeintres is the test that fails always the same? If so, could you maybe create a branch that only runs that test, so that it's faster to run multiple times and reproduce?

@ChristopherDedominici ChristopherDedominici added status:needs-more-info There's not enough information to start working on this issue and removed status:triaging labels Nov 24, 2023
@fvictorio fvictorio closed this as not planned Won't fix, can't repro, duplicate, stale Dec 8, 2023
@github-project-automation github-project-automation bot moved this from Backlog to Done in Hardhat Dec 8, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status:needs-more-info There's not enough information to start working on this issue
Projects
Archived in project
Development

No branches or pull requests

4 participants