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.
Description
Expected behavior:
When setting up a ceremony for a circuit with >1M constraints, the CLI automatically chooses VM verification and promps the user to select and instance type.
Actual behavior:
When setting up a ceremony for a circuit with >1M constraints, the CLI automatically chooses CF verification
The reason this occurs was because we assume
cfOrVM
is aboolean
when it's actually a string in the case thatenforceVm
istrue
. Since the string is truthy, the CLI sets it to CF verification instead of VM verification.Checklist: