Sometimes it's useful to think of an incompletely-specified date as a range. "March 4" refers to a whole day: from March 4 at 12:00:00 AM to March 5 at 12:00:00 AM. "March 4th 2:00 pm" refers to a whole minute: from March 4th at 2:00:00 PM to March 4th at 2:01:00 PM."

To put it another way, there's a big difference between telling someone, "Do this on March 4th" and "Do this on March 4th at 12:

Righ now we have a Java sample app, we should show the usage of the app in a Kotlin example also.

I noted the lack of a set function (as here). I built a sort of set function in a project of mine. At the moment it works only on array, what do you think if I make a porting of my function on your project?
What are your general guidelines to make a pull request? Do you have any suggest?
Best Regards
Domenico Rizzo

What was wrong?

The previous implementation of ExtendedDebugLogger cached whether the DEBUG2 level was enabled.

https://github.com/ethereum/py-evm/blob/5c080532168f38023bfebcd4ec60bb68c70fd29d/eth/tools/logging.py#L9-L13

How can it be fixed?

Use the same pattern for the eth-utils version of the logger.

graphviz-java offers several implementations of Graphviz. The problem is that those implementations are quite "fragile", i.e. if the first one defined is determined to be "available" by graphviz-java, it will be used even if it causes errors down the line on a specific machine.

An example here is an old CLI version of Graphviz unable to create a specific format, or a Nashhorn version unable