Skip to content

Do not assume state list order in download_state #188

Description

@HDauven

Summary

download_state uses the last line of the published state list as the latest state.

The state list is not guaranteed to be sorted by block height. During the recent mainnet recovery, the list contained higher states before lower states, causing the default download_state flow to select a state that was not actually the latest published state.

Possible solution design or implementation

When no state number is provided, parse the state list numerically and select the highest available state instead of using tail -n 1.

The script should also print which state was selected before asking for confirmation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:conf&buildtasks related to our configuration or build system (Makefile, Docker, scripts, commands)fix:bugSomething isn't working

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions