Guillaume Potier
Guillaume Potier
Trying to reproduce it and saving some snapshot on our DO spaces if I can.
@LesnyRumcajs I tried yesterday with snapshots `2719200_2023_03_27T02_00_00Z.car` and `2720400_2023_03_27T12_00_00Z.car` and was not able to reproduce. Will try with yours.
Maybe RPC service could be started only at some point (when Forest is able to serve all API calls)?
Interesting, speaking of supporting exchanges [this issue](https://github.com/ChainSafe/forest/issues/2726) still should be fixed or closed if we can't reproduced it.
Most likely the `send` command is not working as we expected. The test setup should be good, only incomplete regarding message behaviour. From Lotus doc: > If messages are not...
I've been trying to reproduce the issue ~~and it was pretty easy~~. Found out that between two subsequent messages where the first one was mined and the second is stuck...
I think that a bad message `Nonce` could cause the transaction to fail. In Forest node I can see: `WARN forest_message_pool::msg_chain: encountered message from actor t1ekkzekiozleakm4jauekqqc6uhn3dcwzcrrqrry with nonce 53 less...
I've found a new error while sending FIL: `Error: {"code":0,"message":"gas_limit cannot be greater than block gas limit"}` Something is going really wrong here. Will add display of value in error...
To sum up: - The `gas_limit` error was due to some mutation bug and I've fixed it in 5f090e1 - The `Nonce` issue was fixed in bba7724 (I was using...
@LesnyRumcajs did you try to run the script locally? Like sending to an address 40 times.