vbaranov on vb-token-instance-images-mime-types
Fix gettext (compare)
[Victor Baranov, POA Network] > i see the log, first_block= 11262155 , last_block= 11262146, so the range is only 9 blocks.
Yes, the default batch size for catchup fetcher is 10 blocks. If more blocks are absent then it will be processed in different batches.
and i don’t know why first_block > last_block. is it normal?
that is fine. Blocks will be processed in this range.
Are these params for Geth? Looks good to me. You can check yourself too https://docs.blockscout.com/for-developers/information-and-settings/client-settings-parity-geth-ganache
[Victor Baranov, POA Network] Hi, in order to make this API endpoint working, Blockscout instance owner should set CHAIN_SPEC_PATH env variable which is
Chain specification path (absolute file system path or URL) to import block emission reward ranges and genesis account balances from. Geth- and OpenEthereum-style specs are supported.
After setting it, the internal process will parse spec file and fetch block reward value into the table. After that, blockreward endpoint should work fine.
The reference to the list of supported ENV vars:
[Victor Baranov, POA Network] > the first of all they can not parse my genesis json file
Blockscout supports import from genesis json file for Geth and OpenEthereum archive nodes only. Possibly, format of your JSON file is slightly different. Please open an issue in a Github.
During the syncing I have looked at the node which requests got and i have discovered that the explorer requesting many blocks with almost random block number again and again
Blockscout requests the same data again if the previous try failed. It will continue until the response is successful. Especially at the time of the first syncing, it is recommended to strengthen the node because, indeed, Blockscout performs many requests in order to index chain for the first time.
[Victor Baranov, POA Network] Hi, it is possible to run indexer separately from the web application. However, there is no benefit to run multiple instances of indexers because they will don’t know each other and will process the same data intersecting. Luckily, every fetcher in the indexer has its own batch size and concurrency. So, you can manage parallelism of each fetcher inside a single indexer instance.
Hey thanks for this response. Can you give me a pointer in the code / config where I can make these changes in the safest way possible?
when i start blockscout in docker with
make startit shows error
WARNING: We noticed you're using the useBuiltIns option without declaring a core-js version. Currently, we assume version 2.x when no version is passed. Since this default version will likely change in future versions of Babel, we recommend explicitly setting the core-js version you are using via the corejs option. You should also be sure that the version you pass to the corejs option matches the version specified in your package.json 's dependencies section. If it doesn't, you need to run one of the following commands: npm install --save core-js@2 npm install --save core-js@3 yarn add core-js@2 yarn add core-js@3
./apps/indexer/lib/indexer. For instance, batch size and concurrency of internal transactions fetcher is managed at these lines https://github.com/poanetwork/blockscout/blob/master/apps/indexer/lib/indexer/fetcher/internal_transaction.ex#L23-L24. Similarly, is for other fetchers.