Hyeong Geun Oh

@GimluCom Yes. I tried it. The error message just changes from 10 to 1. like this. ``` {"time":"2024-01-29T18:40:24.803Z","severity":"error","message":"Empty id in response: %{error: %{code: -32014, message: "too many RPC calls in...

@sl1depengwyn These are my environment variables. ``` ETHEREUM_JSONRPC_VARIANT=geth ETHEREUM_JSONRPC_HTTP_URL=https://1rpc.io/op DATABASE_URL=postgresql://blockscout:[email protected]:7432/blockscout ETHEREUM_JSONRPC_TRACE_URL=https://mainnet.optimism.io ETHEREUM_JSONRPC_WS_URL=wss://optimism.llamarpc.com SECRET_KEY_BASE=56NtB48ear7+wMSaBajCsdkZCk19A9Nc7GiyspBP2vh7t5zlCsF5QDv76chXeN DISABLE_WEBAPP=true API_V1_READ_METHODS_DISABLED=true API_V1_WRITE_METHODS_DISABLED=true DISABLE_EXCHANGE_RATES=true TXS_STATS_ENABLED=false SHOW_TXS_CHART=false RE_CAPTCHA_DISABLED=true API_V2_ENABLED=true ETHEREUM_JSONRPC_GETH_TRACE_BY_BLOCK=true INDEXER_DISABLE_PENDING_TRANSACTIONS_FETCHER=true INDEXER_DISABLE_BLOCK_REWARD_FETCHER=true INDEXER_INTERNAL_TRANSACTIONS_BATCH_SIZE=1 INDEXER_COIN_BALANCES_BATCH_SIZE=10 INDEXER_RECEIPTS_BATCH_SIZE=10 CHAIN_ID=10 # optimism...

@sl1depengwyn @GimluCom I'm sorry. I guess my explanation wasn't enough. First of all, the above settings are just settings to create an error. Originally, my node had a batch limit...

So, I think the indexer need parameter like `INDEXER_GETH_DEBUG_TRACE_TRANSACTION_BATCH_SIZE`. related #8565, #7330

#7330, right? Thanks for the example. I'll try it. I hope this issue will be officially merged soon!

I ran recent version from ghcr with --debug option. There are no logs related to 'malloc', but there are logs related to 'free()'. ``` 03:45:32.695 5149 DEBUG catalog.c:710 Opening SQLite...

@benw-pusher Can I know when user authentication will be supported? Was there an internal roadmap or meeting?

I investigated the issue in more detail. You can get the blocks that are trying to be reindexed using the query below. ```SQL SELECT DISTINCT block_number FROM logs WHERE first_topic...

There are logs that you mentioned, but it's not the case I'm talking about. (The topic and data are different) I think the indexer recognizes this log as a correct...

@sl1depengwyn @vbaranov