If we config the cache options in the config file, then it will be overwritten.

I would like it to be, but some of our CI scripts use lerna exec tsc. Perhaps we can open a separate PR to update the scripts/npm commands to compile instead of tsc?

Originally posted by @spacesailor24 in ChainSafe/web3.js#3892 (comment)

In this error message:

Error: There was a timeout while attempting to connect to the network.
       Check to see that your provider is valid.
       If you have a slow internet connection, try configuring a longer timeout in your Truffle config. Use the networks[networ

🧐 Motivation
Create simple ERC20 and ERC777 presets with fixed supply.
The benefits are:

• Easy to deploy (including from Remix).
• No access control (for minting/pausing), and hence no governance required.
• Can be verified easily on public networks and then are verified for all.

📝 Details

Community members are creating their own simple ERC20 tokens, so it would be good if they

After ethereum/solidity#10737 we should be able to replace nearly all non-range-based for loops by range-based loops using appropriate ranges.

Suggested improvement on the chrome pop-up confirming a transaction:

Currently the pop-up states "Transaction #X" is confirmed. With X being the number of the transaction from that user's ethereum address. Even better if instead of the transaction number, other metadata could be used as the description for the transaction confirmation - such as the dapp or browser the transaction was occuring o

A parametrized option to set the blocksize would be useful to experiment with. As quorum is used in a private setting I think this option should be available

The cpp-ethereum homepage is not exactly helpful... http://cpp-ethereum.org/ which just takes you to here: http://www.ethdocs.org/en/latest/ethereum-clients/cpp-ethereum/ which only helps with building and installing.. and the only useful link is the "Running" which is only this: "Running eth without any argument will synchronise your node to the public blockchain. It is also possible to create or

Add custom clj-kondo hooks for macroses to ensure that lint rules are followed inside them.

Macros to be handled:

• fx/defn - similarly to defn with check on metadata for ::events
• fx/merge - seems like it could be lint'ed as thread macro, plus warn on limitations
• defview
• letsubs - lint as let + check on types for

It's nice if testing doesn't produce unnecessary artifacts after running with success but keeps relevant info on fail for further inspection.

Pytest should have a nice way of creating fixtures that can post-process a test based on whether it failed or not https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures

If a test fails, then keep the