fix: go-algorand 4.3.0 access list behaviour hotfixes #259
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Gate transaction-level resource population behind ResourcePopulation::Enabled and stabilize behavior on go-algorand 4.3.0+ (access lists).
Update resource_population tests to enable access-list mode, adjust deterministic expectations (e.g., medium box refs).
NOTE: 4.3.0 on go algorand repo https://github.com/algorand/go-algorand/releases/tag/v4.3.0-stable added new access list behaviour but the release does not seem to include updates to algod open api spec (the new access field in app call txns is present in code but not in the spec for some reason). This pr mainly aims to accomodate hotfixes to patch failing resource population tests due to new behaviour in algod images.