Oleg Nikonychev

Results 9 issues of Oleg Nikonychev

``` There are incompatible versions in the resolved dependencies: eth-typing=2.0.0 (from web3==5.29.0->dydx-v3-python==1.5.1->-r /var/folders/c6/2md_1txd6l38vv3ly2_kz4t80000gn/T/pipenv5lnq22earequirements/pipenv-fobg0z3s-constraints.txt (line 2)) eth-typing=3.0.0 (from eth-keys==0.4.0->dydx-v3-python==1.5.1->-r /var/folders/c6/2md_1txd6l38vv3ly2_kz4t80000gn/T/pipenv5lnq22earequirements/pipenv-fobg0z3s-constraints.txt (line 2)) ```

After yesterday's upgrade to `5.2.0` I noticed that messages enqueue (through Celery) to SQS moves messages directly to "In flight", worker doesn't even see them. I found my queue full...

Here and there in liquidator and heart-monitor some unexpected py-sdk messages are appearinng: ``` 12:06:41|DEBUG|_handle_txs| Failed parsing events log: failed to execute message; message index: 0: 0unibi is smaller than...

type: bug

How to reproduce: I intentionally created 100+ delegations. Now querying delegations returns ``` nibid q staking delegations-to nibivaloper1zaavvzxez0elundtn32qnk9lkm8kmcszuwx9jz --node tcp://34.130.24.87:26657 --chain-id nibiru-localnet-0 ``` ``` - balance: amount: "10" denom: unibi...

See the block results below and notice that the same transaction has 2 events `ethereum_tx` and two different `txIndex` values `0` and `1`. The correct value is `0`. - Related...

S-triage

Produces traces for the `debug_traceBlockByNumber` query when tx is a creation of a funtoken from coin. Used by indexers to track erc20 funtoken contracts. ```bash curl --location 'http://127.0.0.1:8545' \ --header...

Issue spotted when HeartMonitor captured ERC20 tx log for a contract which is not tracked. Issue happened in block 19176785: https://rpc.nibiru.fi/block_results?height=19176785 Tx Hash: `0xc3a57553cebe226092b2d246c46afb81bfea5025416260b49daa2250c57cd571` ### EventEthereumTx event: It's a call...

S-triage

- related to https://github.com/NibiruChain/nibiru/issues/2321

⚠️ do not merge