Error: Could not set `null` as the transaction hash (deploying with `{overwrite: false}` )
See original GitHub issueAny ideas why this is happening in Truffle 4.1.0?
⚡ truffle test
Using network 'development'.
Error: Could not set `null` as the transaction hash for COT
COT inherits from StandardToken and doesn’t do much else.
Environment
- Operating System: OSX
- Ethereum client:
- Truffle version (
truffle version
): Truffle v4.1.0 (core: 4.1.0) Solidity v0.4.19 (solc-js) - node version (
node --version
): v8.4.0 - npm version (
npm --version
): 5.7.1
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Transaction problem with Web3 BEP20 in Node JS
After sending via the contract with web3 I only get a TX hash as a response and no receipt or anything like that....
Read more >wighawag/hardhat-deploy - GitHub
the deploy field override the paths.deploy option and let you define a set of folder containing the deploy scripts to be executed for...
Read more >web3.eth — web3.js 1.0.0 documentation - Read the Docs
Returns the receipt of a transaction by transaction hash. Note. The receipt is not available for pending transactions and returns null . Parameters ......
Read more >SqlPackage Publish - SQL Server - Microsoft Learn
Specifies if SqlPackage should overwrite existing files. Specifying false causes SqlPackage to abort action if an existing file is encountered. ...
Read more >Documentation - Ethers.js
If a topic-set is null , a log topic in that position is not filtered at all ... transactionHash - the hash of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@elie222 @JackPickering Apologies, it looks we introduced this bug in
4.0.7
. Have opened a PR attruffle-contract
(ref above) which will hopefully resolve this. Should be included in a patch release scheduled for early next week.@JackPickering Thanks, re-opening. Will look into this and see what’s going wrong . . .