Skip to content

pruner: --archival=false enables archival mode #5281

Description

@Bruce039

Version: main (3b16e0d)

--archival=false turns archival mode on. ParseFlags in nodebuilder/pruner/flags.go only checks cmd.Flag(archivalFlag).Changed and never reads the value, so any explicit use of the flag enables it.

  • celestia bridge start --archival=false disables header pruning and runs the node as archival (on a node that was pruned before, start fails with ErrDisallowRevertToArchival).
  • celestia light start --archival=false exits with "Archival mode is only supported for Bridge nodes".

Explicit --flag=false is common in templated deployments (helm/compose).

Expected: --archival=false behaves like not passing the flag.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions