System information

Geth
Version: 1.10.13-stable
Git Commit: 7a0c19f813e285516f4b525305fd73b625d2dec8
Architecture: amd64
Go Version: go1.17.3
Operating System: linux
GOPATH=
GOROOT=go

Expected behaviour

Close files that aren't in use / have a settable limit

Actual behaviour

Every database file it opens stays open for the duration of the sync

Steps to re

🧐 Motivation

I have came across the below function where implementers can to override to customize the functionality.
The thing is the validation within the base implementation. Basically as a developer, I would expect the function to act as getter returning the fee amount while keepin

Whiskers' regex looks for <..> as opposed to tokenizing the input, so it is not able to detect truncated/mistyped input.

For example it can't detect that <!b is not terminated in<?b> X <!b Y </b>.

With some heuristics it could be improved: match for <?, <! and </ and only allow identifiers which are terminated with >, otherwise it is invalid.

_Originally posted by @axic in h

• 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.

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

Component

Forge

Describe the feature you would like

Issue

Currently, when installing a specific version/branch of a dependency, this version is lost when running forge update.
Example:

forge install rari-capital/solmate@v7
forge update

=> checks out to master
I would expect the checked out branch to remain the same.

Example Scenario

I currently am depending on

It is currently not possible to specify the chain ID for a hardhat network invoked with npx hardhat node through any means other than the config file. This means it is impossible to specify the --chain-id argument in the command line, or execute a chain host pragmatically with hre.run('node', { chainId: 100 }).

Please add the chainId parameter to the node command so it is possible to