You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cost estimations for contract-call invocations in 2.05 and 2.00 must be reset -- the costs of contract-calls will all change because of the new cost functions, methods of calculating input, etc.
This should be relatively easy to implement -- the cost estimator should just add an epoch identifier to the key used as a cost identifier:
For testing this, I believe it's sufficient to unit test. Basically, add a new test or set of tests in the src/cost_estimates/tests/cost_estimators.rs module that:
supply measurements with the evaluated_epoch = 2.0
fetch estimates using 2.05, asserting that no estimate is available
fetch estimates using 2.00, asserting that an estimate is available
supply different measurements with the evaluated_epoch = 2.05
fetch estimates using 2.05, asserting that the estimate is available, and is different than the 2.00 estimate
fetch estimate using 2.00, asserting that its still the same as it was in step 3
Cost estimations for contract-call invocations in 2.05 and 2.00 must be reset -- the costs of contract-calls will all change because of the new cost functions, methods of calculating input, etc.
This should be relatively easy to implement -- the cost estimator should just add an epoch identifier to the key used as a cost identifier:
This will separate the estimates of functions evaluated in 2.05 from those evaluated in 2.00.
The text was updated successfully, but these errors were encountered: