Possible cost calculation issue

[whoabuddy]

We deploy a "tardis" contract that uses at-block to pull historical information from CityCoins contracts. It's a very basic contract and used in conjunction with a vote contract as seen here:

• Tardis V2 on Explorer / GitHub
• Vote V1 on Explorer / GitHub

For an upcoming vote, we've deployed a new tardis / GitHub and it is failing because it exceeds the read length (107905 / 100000):

Unchecked(CostBalanceExceeded(ExecutionCost { write_length: 0, write_count: 0, read_length: 107905, read_count: 17, runtime: 125602 }, ExecutionCost { write_length: 0, write_count: 0, read_length: 100000, read_count: 30, runtime: 1000000000 }))

When testing a similar, local version of the contract, the output of clarinet test --costs shows this value as much lower:

├──────────────────────────────────────────┼──────────┼──────────────────────────┼──────────────────────┼─────────────────────────┼─────────────────────┼──────────────────────┼──────────────┤
│                                          │ # Calls  │ Runtime (units)          │ Read Count           │ Read Length (bytes)     │ Write Count         │ Write Length (bytes) │ Tx per Block │
├──────────────────────────────────────────┼──────────┼──────────────────────────┼──────────────────────┼─────────────────────────┼─────────────────────┼──────────────────────┼──────────────┤
│ get-stacker-stats                        │        3 │  min:  114042  (0.002%)  │  min:  18  (0.120%)  │  min:  91411  (0.091%)  │  min:  0  (0.000%)  │   min:  0  (0.000%)  │          833 │
│                                          │          │  max:  114042  (0.002%)  │  max:  18  (0.120%)  │  max:  91411  (0.091%)  │  max:  0  (0.000%)  │   max:  0  (0.000%)  │          833 │
│                                          │          │  avg:  114042  (0.002%)  │  avg:  18  (0.120%)  │  avg:  91411  (0.091%)  │  avg:  0  (0.000%)  │   avg:  0  (0.000%)  │          833 │
├──────────────────────────────────────────┼──────────┼──────────────────────────┼──────────────────────┼─────────────────────────┼─────────────────────┼──────────────────────┼──────────────┤

The core contract that the tardis contract queries for information did increase slightly in size, and I think I have a workaround, but it would've been nice if the cost testing showed this could be a potential issue.

See citycoins/contracts#208 for more detail.

[lgalabru]

Should be addressed with the latest VM integration #544