Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hot fix v20.0.2, increased preflight instruction fee padding to 3 million #1127

Merged
merged 4 commits into from
Dec 12, 2023

Conversation

sreuland
Copy link
Contributor

What

increased the instruction fee padding during preflight to 3 million to accommodate new v20 cost model and more complex contracts that use more compute.

Why

avoid preflight fees failure on contracts that used to work pre-v20

Known limitations

[TODO or N/A]

assert.InDelta(t, uint32(expectedTransactionData.Resources.ReadBytes), uint32(transactionData.Resources.ReadBytes), 10)
assert.InDelta(t, uint32(expectedTransactionData.Resources.WriteBytes), uint32(transactionData.Resources.WriteBytes), 300)
assert.InDelta(t, int64(expectedTransactionData.ResourceFee), int64(transactionData.ResourceFee), 3000)
assert.Greater(t, int64(transactionData.ResourceFee), int64(0))
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tamir, how did you obtain the fee 113910 for this example? after the increase on instr budget to 3M in this pr, the resulting fee here is outside this delta, is the resulting fee deterministic based on other factors, I took a defensive approach on test stability and just assert on minimal aspect of the fee must be > 0, same on line 1124.

@sreuland sreuland merged commit 514406e into stellar:release/v20.0.2 Dec 12, 2023
21 of 22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants