docs(fizz): add --experimental_no_graph and document experimental flags#351
Merged
Merged
Conversation
The --experimental_no_graph flag landed in #350 but wasn't wired through the fizz wrapper script — users invoking via ./fizz couldn't opt in to no_graph mode. Add the parse case, args-forwarding, and default-false initializer. Also document both experimental flags in the usage() output so they appear in --help. The wrapper had silently forwarded --experimental_processed_queue without listing it in usage; users discovered it only via the binary's --help. The new usage block calls them out as experimental-and-off-by-default with a one-line summary each, including the no_graph caveats (no liveness, no crash simulation, auto-enables processed_queue). Verified: ./fizz --help now lists both flags; ./fizz --experimental_no_graph <spec> runs in no_graph mode (visible from the auto-enable note and the "Peak (new)" line confirming the NEW queue path). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
jp-fizzbee
force-pushed
the
user/jp/fizz-wrapper-experimental-flags
branch
from
a5d2d09 to
ec1e1bb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The --experimental_no_graph flag landed in #350 but wasn't wired through the fizz wrapper script — users invoking via ./fizz couldn't opt in to no_graph mode. Add the parse case, args-forwarding, and default-false initializer.
Also document both experimental flags in the usage() output so they appear in --help. The wrapper had silently forwarded --experimental_processed_queue without listing it in usage; users discovered it only via the binary's --help. The new usage block calls them out as experimental-and-off-by-default with a one-line summary each, including the no_graph caveats (no liveness, no crash simulation, auto-enables processed_queue).
Verified: ./fizz --help now lists both flags; ./fizz --experimental_no_graph runs in no_graph mode (visible from the auto-enable note and the "Peak (new)" line confirming the NEW queue path).