Updating Springrole blockscout with latest release #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* npm audit fix --only=dev
Update npm dependencies
…on-the-token-holders-page-near-your-address
…now-available-on-the-token-holders-page-near-your-address Async loading on the token holders page
Why: * To be able to index transactions, we need to add special handling for a bug in Ganache in which transaction inputs are returned as invalid `DATA` types. For details please see: ConsenSys-archive/ganache#997 * Issue link: #1068 This change addresses the need by: * Editing `EthereumJSONRPC.Transaction` to convert incorrectly formatted transaction `input`s of `0x0` to `0x`.
Handles Ganache transaction input bug
Why: * We were using the `EthereumJSONRPC.Geth` variant for Ganache but we recently learned that it doesn't support the `tracer` option for [debug_traceTransaction](https://github.com/ethereum/go-ethereum/wiki/Management-APIs#debug_tracetransaction). This `tracer` option is what we currently use to fetch internal transactions for Geth. This was the cause of errors as shown on issue 1152 (link below). * Issue link: #1152 This change addresses the need by: * Creating `EthereumJSONRPC.Ganache`. It ignores fetching beneficiaries, internal transactions, and pending transactions. * Editing ganache config to use the `EthereumJSONRPC.Ganache` variant instead of `EthereumJSONRPC.Geth`. * Updating inaccurate doc in `EthereumJSONRPC.Geth`. It previously said fetching internal transactions was not supported for Geth which is inaccurate.
This code should be removed with the code removed in this PR: https://github.com/poanetwork/blockscout/pull/1063/files
…ons-realtime Remove references from pending transactions feature
Fixes #1109 Use `NOT VALID` on constraint and don't put data updates in schema migration. Instead, migrate data using script based on @amandasposito's scripts.
… create_has_init Fixes #1112
Allow gradual data migration after schema and code is deployed
Gsf fix contract code display
Add release build
Improve docs in the application
Realtime block number will set `Logger.metadata(block_number: ...)` for each block number is fetches separately after getting the `newHead` websocket message.
The catchup block range `first_block_number..last_block_number` will set `Logger.metadata(first_block_number: first_block_number, last_block_number: last_block_number)` for errors in `BoundIntervalSupervisor` and tasks in `Catchup.Fetcher`.
Record the number of things being fetched in metadata instead of in text so that the count can be graphed.
Having count and error_count in the metadata would allow us to graph one vs the other to see how often we achieve partial retries vs full retries.
Being in metadata will allow it to be graphed by tools.
Allow separating shrunk vs unshrunk to monitor how often shrinking occurs.
Metadata instead of prose
Fix displayed address length when a primary name presents
Log timeout in PendingTransaction fetcher instead of crashing
`Indexer.Block.Uncle.Fetcher.retry/1` when there are errors did not
actually retry the calculated `retried_errors` and instead only logged
them. This didn't cause an unused variable warning because
`retried_errors` is used in the Logger metadata. The `Task` for the
`run/2` callback did not error because `Logger.error` returns `:ok`.
To fix this problem, `{:retry, retried_errors}` need to be returned
after the `Logger.error` call.
Fixes #1221 It happens too often to be worth treating as an error as we should only log things that are exceptional and need human attention as errors.
Don't log errors when uncles aren't found
Fixes #1215 The short-circuiting `[]` was not being used.
Fix picking wrong clause for fetch_token_balances_from_blockchain
Fixes #1223 For large chains like ETH Mainnet, it is fairly common for the catchup fetcher to take a long time to calculate the missing block numbers and start the named Sequence used by `push_front(block)`. Since this is normal and not exceptional, `InvalidConsensus.Worker` shouldn't log this and retry silently.
They have a similar style where Uncataloged could also receive :queue_unavailable.
Don't log when queue is unavailable in Indexer.Block.InvalidConsensus.Worker
…a-from-blockchain-call Save reward data from blockchain call
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
12 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updating Springrole blockscout with latest release