-
Notifications
You must be signed in to change notification settings - Fork 458
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
[BUG] local-node-info subject #2411
[BUG] local-node-info subject #2411
Comments
Hi @MalekLahbib, I have tried to run your solution locally, and it does not work for me :) I might have tried an incomplete version: could you please send me the full solution text using this formatting? |
@nprimo thanks for the formatting advice, I didn't give attention to it, from now I will, I updated my comment so now you have the full code. I launched a local eth node with "npx hardhat node", and when I open my html file it works. |
Hello @nprimo, I'm still waiting for a response to this issue. Best Regards |
Hi @MalekLahbib, I am currently working on this |
Hello @MalekLahbib, Thank you for submitting this issue.
|
local-node-info
I wrote a code that's working fine locally, but doesn't pass the test, I tried with "web3" package and "ethers" package, here's my code:
and here's the test response:
[1m�[43m�[30m
Puppeteer old Headless deprecation warning:�[0m�[33m
In the near feature
headless: true
will default to the new Headless modefor Chrome instead of the old Headless implementation. For more
information, please see https://developer.chrome.com/articles/new-headless/.
Consider opting in early by passing
headless: "new"
topuppeteer.launch()
If you encounter any bugs, please report them to https://github.com/puppeteer/puppeteer/issues/new/choose.�[0m
Local node info
1) Should have the correct chainID
2) Should have the correct number of blocks
0 passing (12s)
2 failing
Local node info
Should have the correct chainID:
Error: Timeout of 10000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/jail/test/local-node-info.test.js)
at listOnTimeout (node:internal/timers:569:17)
at processTimers (node:internal/timers:512:7)
Local node info
Should have the correct number of blocks:
AssertionError: expected NaN to equal +0
-NaN
+0
at Context. (test/local-node-info.test.js:54:45)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
The text was updated successfully, but these errors were encountered: