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
Currently, only cpu and memory limits are enforced during testing because those two limits are tracked in the host. Limits like the entry and byte limits are enforced in core, so contract tests using the sdk are not affected by these limits. The issue with this is that a contract developer will not realize those limits are an issue until after they deploy their contract to testnet, potentially resulting in wasted time developing a contract that doesn't work.
We should allow the sdk testutils to set and enforce limits just like the ones in core (read_entries, write_entries, read_bytes, write_bytes, and contract_events_size_bytes).
The text was updated successfully, but these errors were encountered:
What problem does your feature solve?
Currently, only cpu and memory limits are enforced during testing because those two limits are tracked in the host. Limits like the entry and byte limits are enforced in core, so contract tests using the sdk are not affected by these limits. The issue with this is that a contract developer will not realize those limits are an issue until after they deploy their contract to testnet, potentially resulting in wasted time developing a contract that doesn't work.
We should allow the sdk testutils to set and enforce limits just like the ones in core (read_entries, write_entries, read_bytes, write_bytes, and contract_events_size_bytes).
The text was updated successfully, but these errors were encountered: