Explicitly calling chain.mine(1) does not work after disabling auto mining.

[derekpierre]

Environment information

• OS: macOS

• Python Version: 3.12

• ape: 0.6.27

• Contents of your ape-config.yaml (NOTE: do not post anything private like RPC urls or secrets!):
  https://github.com/nucypher/ATxM/blob/main/tests/ape-config.yaml

What went wrong?

Related to #1968 .

After disabling auto-mining (see #1968), it seems that the subsequent use of chain.mine(1) (using the chain fixture) does not work, and instead I have to specifically call w3.provider.ethereum_tester.mine_block() for the mine to actually occur.

Ideally using the chain fixture should be sufficient to force the mining of blocks.

[linear]

APE-1713 Explicitly calling `chain.mine(1)` does not work after disabling auto mining.

[antazoey]

are you using the eth-tester provider that comes with Ape?
I haven't been able to reproduce this one, even after implementing the auto mine functionality.

[derekpierre]

are you using the eth-tester provider that comes with Ape?

Pretty sure we are. We don't have an explicit dependency on eth-tester.

[derekpierre]

That being said we use an older version of eth-ape - eth-ape==0.6.27. Is that issue possibly fixed in a newer version?

We haven't updated to a newer version of eth-ape because of #1933

[antazoey]

We haven't updated to a newer version of eth-ape because of #1933

workaround for #1933 #1933 (comment)
btw, this isn't a bug on 0.8 (which isn't released yet but is in the works)

[antazoey]

still unable to reproduce this.

[antazoey]

please re-open , i dont think this is a problem!