Ethereum

I had a unclean shutdown less than a day ago and got this warning afterwards:

WARN [03-26|10:10:29.944] Unclean shutdown detected booted=2021-03-17T13:16:42+0000 age=1w1d20h

As it would be better to have the "age=" part closer to the shutdown @holiman suggested to update the marker like every 5 minutes

There is the test/libsolidity/SolidityEndToEndTest.cpp file, which contains a lot of semantic tests. It is a large monolithic single C++ file, which takes a long time to compile and is hard to maintain.

We want to move as many test cases out to individual files under test/libsolidity/semanticTests. They should be grouped logically, by following the grouping in SolidityEndToEnd.

Have a

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

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

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