-
Notifications
You must be signed in to change notification settings - Fork 65
Fix validation failing when there's a hh3 cache hit #715
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
base: development
Are you sure you want to change the base?
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## development #715 +/- ##
===============================================
+ Coverage 52.61% 52.93% +0.32%
===============================================
Files 231 231
Lines 5592 5728 +136
Branches 878 918 +40
===============================================
+ Hits 2942 3032 +90
- Misses 2392 2427 +35
- Partials 258 269 +11 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I think this is only part of the problem, because the logs seem to indicate that something else is going off. Look at this. New project, viem sample project. I open the first Solidity file. I get this log: I close the file, clear the log, Some part of the language server is treating |
|
@alcuadrado good catch, just pushed a commit to fix it |
If you compile a hardhat3 project, cache entries will be set for the contracts that were compiled successfully. When attempting validation for a file,
getCompilationJobsis used, which returns an empty array if there are no jobs to compile (because there was a cache hit). Two possible options would be to either skip validation when there are no jobs to compile, or to passforce: true. I chose the latter one since I think it's consistent with our model of compiling on every file change.