truffle

Feature

Similar to #4461, it would be nice if people could truffle exec typescript without needing to run a compilation step.

Steps to Reproduce

Write a script for truffle exec in TypeScript

Desired Behavior

Truffle would use ts-node to execute said script

Current Behavior

Users must first compile said script, and truffle exec the compilation output.

Ruby 3.0.2 allows a string for Process.euid=, and will (I assume) do a user lookup in that case:

# OS X
Process.euid = "test" # => can't find user for test (ArgumentError)
Process.euid = "dberger" # => "dberger"

But using Truffleruby 22.0.0.2:

Process.euid = "test" # => undefined method `to_int' for "test":String
Process.euid = "dberger" # => undefined method `to

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.

Bug Description

A bug in the verfy.js prevents verifying Proxy smartcontrat. When I tried verifying a proxy smartcontract, It started verifying the implementation contract and failed with the message: "Invalid constructor arguments provided. Please verify that they are in ABI-encoded format". After debugging the process, I found that retrieved constructor argument parameters are different f

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.