This repository has been archived by the owner on Jan 13, 2025. It is now read-only.
Fixes the calculation of the compute_meter_consumption #21944
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.
Problem
The calculation of the
compute_meter_consumption
acrossprocess_instruction()
andprocess_message()
was broken in #21671. Thepre
value was measured beforeInvokeContext::push()
, then the compute meter was reset to a higher value and later thepost
value could be above thepre
value, resulting in a negative consumption (overflow).This was not caught by the tests as the bug only happens before the feature
tx_wide_compute_cap
is activated and it is always activated in the tests.Summary of Changes
Moves from
process_message()
toprocess_instruction()
so that it does not include modification of thecompute_meter
inInvokeContext::push()
.Fixes #