policy: Do not fuzz mapState receiver #36200
Merged
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.
Ever since we dropped the separate allow/deny maps the fuzz test has been failing on trying to fuzz the mapState receiver. With the new flatter mapState definition this no longer works, and the value of trying to fuzz the empty map is in itself questionable, so drop it. This allows the fuzz test to proceed with insertions of fuzzed keys and values.