• I've opened a support ticket before filing this issue.

Issue

Tests are not isolated from each other. I reproduced it using the metacoin box tutorial, adding a new test at the end that checks again the balance. As per the "clean-room" the first account should have all 10000 tokens. It's not.

I have some contracts using a library structure data storage, compiled using an older version of Solidity, but which throw an error asking me to make a report here.

In the libraryType.sol contract I have something like this:

library PersonLib {
    struct Data {
        bool   isActive;
        bytes  hashOfData;
        string handle;
    }
    function handle(Data stor

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.

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.

Working with multiple block explorers, sometimes it would be great to just output the standard json, so it can be uploaded to verify manually.

My current work-around is to change the verify.js slightly, so it outputs the standard json (line 173)

...
 const postQueries = {
    apikey: options.apiKey,
    module: 'contract',
    action: 'verifysourcecode',
    contractaddress: artifa

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.