truffle

Issue

Vyper handles unmapped instructions differently from Solidity. In Solidity, unmapped instructions are given a file index of -1. When attempting to show the source for such an instruction, we instead just show 1: // No source code found..

However, in Vyper, such instructions are not given a file index of -1, but are given a start and length of 0. So when we show the source for t

We should add explicit runtime errors that stop CLI execution when an obvious version mismatch is detected. No one (me neither) checks peer dependency-related errors from a package manager.

TC should bail if:

• ether target has detected too low ethers version detected
• tc core package is too low to support given target package

Each target package should be able to define custom conditions

When a lot of data has been added, it might be annoying to find the data you want to refund/report. It would be good to have an easy way to search for the events.

Search params can be put into the customFilter function that is passed to handleAddedData.

Hi, Patrick

Can you please only leave the .env.example file and delete the .env one?
Us newbies might end up leaving our mneumonic exposed, because .gitignore does not ignore files that are already there on github.

Thanks for all the top-notch teaching.

It would be nice if truffle-flattener added the package version of the imported library in the comments of the output file.

For example:

// File: zeppelin-solidity/contracts/ownership/Ownable.sol Package: zeppelin-solidity@v1.7.0

Current if I have 30 solidity contracts, I need to key in one by one

Currently
truffle run verify ContractA --network rinkeby
truffle run verify ContractB --network rinkeby
truffle run verify ContractC --network rinkeby

Is that any I could run something like that, then it will eventually verify all my contracts?
truffle run verify all --network rinkeby

thanks buddies

When bailing out with an error, print where in source error occurred. We already set source section in ast visitor but do not print it in error cases.

Decide if early or lazy loading is better for graalphp.

• pro for eager: we may implement phpdoc semantics into parsing (types)
• however, new versions of php support type hints and dont have to rely on comments
• i think for now we lazy loa

See TODOs in ClipboardExtendedPlugin.java.