Raw trace of transaction on-demand #3013
Merged
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.
Motivation
We will start to ignore first traces from #3000 in case of Parity variant. Thus, we will not store them in the DB in order to shrink occupated space. In order to not break raw trace feature in Blockscout it is implemented to get transaction's raw traces on demand. Actually, the first trace will be fetched on-demand from the archive node once anyone opens the
/raw_trace
page of transactions for the first time and this first trace saved to the DB. And raw trace will be collected from all internal transactions from the DB and displayed on the page. If the first trace already exist in the DB, application will no request the node again in order to fetch it.Checklist for your Pull Request (PR)
CHANGELOG.md
with this PRmaster
in the Version column. Changes will be reflected in this table: https://docs.blockscout.com/for-developers/information-and-settings/env-variables.