Open engn33r opened 1 year ago
The keyboard interrupt likely didn't work because its checked once on every new block. If no new blocks are produced, that's likely the cause for that.
I haven't been able to reproduce this issue so far. Is anvli producing any output (is it accepting transactions)? Could also be that tenderly is incompatible, but I highly doubt it as its not using any non standard RPC calls for reading state.
I added a warning to the latest pr that will show every 60 seconds if no new blocks appear, it should clear up some confusion
I pulled the latest sothis 0.3.2 to test this again:
Describe the bug
Cannot use keyboard to interrupt sothis process. Instead, I have to manually kill the process.
Separate issues: cannot kill anvil process with keyboard interrupt, anvil blocks not increasing after the sothis track mode instance is started.
To Reproduce
Steps to reproduce the behavior:
anvil --fork-url https://eth-mainnet.alchemyapi.io/v2/xxxx --fork-block-number 17499990 --cups 2000
sothis --source_rpc https://mainnet.gateway.tenderly.co/xxxx --replay_rpc http://127.0.0.1:8545 --terminal_block 17500100
sothis --mode track --source_rpc http://127.0.0.1:8545 --contract_address 0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640 --storage_slot 0 --filename uniswap-slot0.json --path ./
I did not have this issue with track mode on a live node (current block), I have only observed the issue using a local node.
Expected behavior
Can use keyboard interrupt to kill process. Anvil block numbers should increase.
Screenshots
N/A
Setup (please complete the following information):
Additional context