Andrii
Andrii
@xlc @ermalkaleci
> what RPC node are you using? if is local one, what's the CPU usage? I used both: remote and local. If it comes to local, I monitored resource usage...
UPD: I was also experimenting with subway connected to both RC and AH and it did not help either
My colleague mentioned that he had a similar problem with subalfred and that [the fix](https://github.com/serban300/subalfred/commit/e2c4a5b1f6d2ee3b511334360c2359048b2a7607) resolved the problem. The problem was that some values were too big and were timing...
cc: @serban300
I am checking if that's a migration issue by running zombie-bite. It just got fixed today so I am still on my way...
If I remember correctly, Serban was using [this script](https://github.com/paritytech/ahm-dryrun/pull/17/files) and also added `timeout: 60000` (not newly added `rpc-timeout`) as part of the Relay and AH config.
> Now the all thing makes sense, it's your WsProvider connected to chopsticks which is timing out. Obviously because it will take chopsticks a long long time to go through...
> You need a polkadot-parachain node running. Small nits: You can easily **start the node** from `ahm-dryrun` repo by running: ``` just build-omni-node just run-chain ``` It will use 9944...
Hey @xlc I was able to start the migration with zombie-bite (a tool similar to chopsticks but it produces the blocks at regular 6s cadence, not on-demand as chopsticks does)....