Unable to push hardhat contracts about tenderly-cli HOT 20 CLOSED

Hey, thanks for reaching out.

I've ran the command with the --debug flag and it looks like we're having problems reading some contract source files. The error I get is node_modules/solc_0.7/proxy/Proxy.sol while the actual path is node_modules/hardhat-deploy/solc_0.7/proxy/Proxy.sol.

It seems that all the source paths generated by hardhat deploy reference the files without the hardhat-deploy prefix, and that breaks our path resolution. I have no workaround at this time, but I will keep looking into this and let you know!

from tenderly-cli.

Hey that does help will test it out thank you!

from tenderly-cli.

Hey, I am unable to push as well ! We're using hardhat only and we get the same error:
unable to upload contracts: unable to get provider contracts: failed listing build files: open deployments: The system cannot find the file specified.
Couldn't read Hardhat build files at: deployments

Is there a workaround ? Let me know please. It's important.

from tenderly-cli.

Hey @deussatori, are you using yarn link/workspaces by any chance?

from tenderly-cli.

Hey, no.
I did try with a (1) contract as basic as possible a (2) hardhat config as basic as possible - still no luck.
I believe it's looking into the wrong folder. When I renamed "artifacts" to "deployments" I get this error:

"encountered unexcepted error: runtime error: invalid memory address or nil pointer dereference
Encountered an unexpected error. This can happen if you are running an older version of the Tenderly CLI."
I am using "tenderly_1.0.1_Windows_amd64"
So I believe this is it either.

from tenderly-cli.

Can you run tenderly <command> --output json --debug

If you want to keep the output private, you can go to Tenderly, start the chat in the bottom right and paste it there 😃

from tenderly-cli.

I also appear to be unable to deploy hardhat contracts. I'm using hardhat-deploy. My deployments are in the deployments folder. The output I get is...

Setting up your project...
Analyzing Hardhat configuration...
Pushing Smart Contracts for project: goldfinch/goldfinch-protocol
No migrated contracts detected in build directory: /Users/blakewest/code/goldfinch/goldfinch-protocol/deployments. This can happen when no contracts have been migrated yet.
Some of the project pushes were not successful. Please see the list above

I ran it with the debug flags, and put it into this gist. Hopefully that helps! Would love to use this feature with my project.

from tenderly-cli.

The same is happening to me 5 months after

from tenderly-cli.

Also running into this issue...

> tenderly contracts push --networks 42 --debug                                               (py39) 
Setting up your project...
Trying OpenZeppelin config path: networks.js
couldn't read new OpenzeppelinConfig config file
Trying buidler config path: buidler.config.js
couldn't read new Buidler config file
Trying hardhat config path: hardhat.config.js
unable to fetch config
 Couldn't read Hardhat config file
Trying hardhat ts config path: hardhat.config.ts
Making request
Got response with body
Analyzing Hardhat configuration...
Trying Hardhat config path: /home/samlaf/dev/ethereum/hardhat/hardhat.config.js
Trying Hardhat config path: /home/samlaf/dev/ethereum/hardhat/hardhat.config.ts
Pushing Smart Contracts for project: hardhat-test
We have detected the following Smart Contracts:
• Greeter
•  (not deployed to any network, will be used as a library contract)
• Greeter (not deployed to any network, will be used as a library contract)
•  (not deployed to any network, will be used as a library contract)
[          ] Making request
[===       ] Got response with body
Push for hardhat-test failed with error: unexpected number of pushed contracts. Got: 0 expected: 4
Some of the contracts haven't been pushed. This can happen when the contract isn't deployed to a supported network or some other error might have occurred. Below is the list with all the contracts that weren't pushed successfully:
• Greeter on network 42 with address 0xB796bB43543A62d7d79C14aB6eA36A65716bc74B
unable to upload contracts: some project uploads failed
Some of the project pushes were not successful. Please see the list above

Just trying to push the simple Greeter contract that comes from initializing a fresh hardhat typescript project.

from tenderly-cli.

Wait are the error only because I don't have a paid account?

If that is the case... there should be a much more explicit error message.

from tenderly-cli.

Hey @samlaf, the error isn't there because it's not a paid account.

Usually this error means that the deployed bytecode doesn't match the source + compiler options that the CLI pulls from your filesystem.

If you contact us over the in-app chat we can look into the exact error in our logs. 😃

from tenderly-cli.

Thanks @BogdanHabic, I moved on from this issue, but will make sure to do contact you next time I need to debug a transaction using tenderly. :)

from tenderly-cli.

from tenderly-cli.

Hey @Donaldson7, what do you mean that you can't resimulate transactions to the right address? All addresses are unlocked by default in the Simulator and Forks.

from tenderly-cli.

I also have error about not-existant deploymets folder. I don't understand I don't have such folder in my hardhat project why tenederly is asking for one? Neither in truffle .

from tenderly-cli.

As anyone managed to solve this issue ? I'm trying to push a contract from Hardhat but facing this:
Couldn't read Hardhat build files at: deployments

from tenderly-cli.

Hey, have you checked out this? It should help with the issue you guys are facing.

Tenderly works with artifacts generated by either hadthat-deploy or hardhat-tenderly plugins, so you need one of those in order for the required directories to be generated.

from tenderly-cli.

Thanks it helped me solve the issue 👍

from tenderly-cli.

Hey @BogdanHabic I am also facing this error when I try to push a local transaction off of my local node (running in forked mode). It finds the hardhat config, and I believe that after it tried to read contract artifacts it throws the:

encountered unexcepted error: runtime error: invalid memory address or nil pointer dereference

Happy to debug with you if you are willing

from tenderly-cli.

@sparrowDom We're moving away from supporting local transactions, and moving towards our own local development solution: DevNets (read more here).

This is the gist (generated by GitBook Lens):

DevNets are managed, zero-setup environments for smart contract development. They provide an isolated and flexible network where you can deploy, test, and debug your smart contracts using tools like the Debugger, Gas Profiler, and Call Trace. DevNets also allow you to access Mainnet data, simulate transactions, and customize the blockchain environment. They offer benefits such as zero-setup, isolation, flexibility, unlimited faucet, and reusable templates.

I hope this helps!

from tenderly-cli.