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
We have a setup fixture that take a parameter numberOfAccounts which it use as the number of accounts to deploy. However, if connected to a sandbox, it won't actually deploy the the number of specified accounts, instead it will always deploy a hardcoded number of accounts. So for tests that expect >3 (current hardcoded accounts) accounts, the setup will pass and tests will then fail when the account is to be used.
Fixes#2801. (Also fixes#3214)
Experimentation with slow updates in Noir.
- Adds a slow update structure
- Sparse tree to support membership and non-memberships
- Wraps this structure in a contract to make interaction easier
- Adds an oracle to make it practical to pass the >200 params.
- Implement token contract with blacklist and access control in the slow
tree.
We have a
setup
fixture that take a parameternumberOfAccounts
which it use as the number of accounts to deploy. However, if connected to a sandbox, it won't actually deploy the the number of specified accounts, instead it will always deploy a hardcoded number of accounts. So for tests that expect >3 (current hardcoded accounts) accounts, the setup will pass and tests will then fail when the account is to be used.Example of this is in #2732.
The text was updated successfully, but these errors were encountered: