Skip to content

chore: remove orphan --pxe flag from aztec start#22867

Merged
nventuro merged 1 commit into
merge-train/fairiesfrom
nico/f-612-aztec-start-pxe-flag-is-defined-but-has-no-handler-no-module
Apr 30, 2026
Merged

chore: remove orphan --pxe flag from aztec start#22867
nventuro merged 1 commit into
merge-train/fairiesfrom
nico/f-612-aztec-start-pxe-flag-is-defined-but-has-no-handler-no-module

Conversation

@nventuro
Copy link
Copy Markdown
Contributor

The --pxe flag has had no handler since #17228 dropped the PXE JSON-RPC server; passing it produced "No module specified to start" and exited 1. This just drops the flag.

The bare `--pxe` flag has had no handler since #17228 dropped the PXE
JSON-RPC server; passing it produced "No module specified to start"
and exited 1. Drop the flag entry and its stale references in the
prover-agent/broker mutual-exclusion guards. The `--pxe.*` namespaced
options stay registered (consumed by `--bot` to configure the bot's
embedded PXE).

Also drop `--pxe` from the spartan bot helm `startCmd` — Commander
silently accepted the unknown flag before, but would now reject it
and crash the bot pod.
@nventuro nventuro merged commit c8b0ac5 into merge-train/fairies Apr 30, 2026
21 of 25 checks passed
@nventuro nventuro deleted the nico/f-612-aztec-start-pxe-flag-is-defined-but-has-no-handler-no-module branch April 30, 2026 00:49
AztecBot pushed a commit that referenced this pull request Apr 30, 2026
The `--pxe` flag has had no handler since #17228 dropped the PXE
JSON-RPC server; passing it produced "No module specified to start" and
exited 1. This just drops the flag.
@AztecBot
Copy link
Copy Markdown
Collaborator

✅ Successfully backported to backport-to-v4-next-staging #22857.

ElusAegis pushed a commit to ElusAegis/aztec-packages that referenced this pull request Apr 30, 2026
BEGIN_COMMIT_OVERRIDE
feat: fix incorrect usage of domain sep in partial notes (AztecProtocol#22832)
docs: add map and state variable docs  (AztecProtocol#22824)
feat(pxe): support nested utility function calls (AztecProtocol#22822)
fix: malformed suggestion in OwnedStateVariable storage panic message
(AztecProtocol#22862)
feat: add --json flag to aztec profile gates (AztecProtocol#22860)
chore: prevent inlining public init check (AztecProtocol#22869)
chore: remove orphan `--pxe` flag from `aztec start` (AztecProtocol#22867)
END_COMMIT_OVERRIDE
critesjosh added a commit that referenced this pull request May 18, 2026
Covers operator-facing changes in v4.3.0:
- Bundled binaries renamed under aztec- prefix on PATH (#22902, #22709)
- --pxe flag removed from aztec start (#22867)
- aztec-up pins manifest Node version (#23201)
- aztec-up pins FOUNDRY_DIR (#22886)

Added to both source docs-operate/ and the v4.3.0 versioned snapshot,
and linked from the operator changelog sidebar in both places.
critesjosh added a commit that referenced this pull request May 18, 2026
…--help

The operator cli-reference.md is hand-maintained (the auto-generation
scripts under scripts/cli_reference_generation/ only target the three
developer-facing CLI refs). The doc had silently drifted from the actual
'aztec start --help' output between v4.2.x and v4.3.0:

- Bare --pxe flag removed (#22867) -- file still documented it
- New --local-network.testAccounts flag added -- file didn't document it
- ~460 lines of help-text drift across other flags/descriptions

Regenerated source + v4.3.0 snapshot from the v4.3.0-rc.1 CLI's actual
--help output. A follow-up PR should wire this regeneration into
scripts/cli_reference_generation/ so the operator CLI ref stays in sync
the same way the developer CLI refs do.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants