Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add upgrade module #3979

Closed
wants to merge 10 commits into from
Closed

Add upgrade module #3979

wants to merge 10 commits into from

Commits on Apr 4, 2019

  1. Add upgrade module

    @aaronc
    aaronc committed Apr 4, 2019
    Configuration menu
    Copy the full SHA
    a9ae75f View commit details
    Browse the repository at this point in the history

  2. Added pending changelog entry

    @aaronc
    aaronc committed Apr 4, 2019
    Configuration menu
    Copy the full SHA
    89ef052 View commit details
    Browse the repository at this point in the history

  3. Add cache behavior to upgrade Keeper, bring package test coverage to … 

    …100%
    @aaronc
    aaronc committed Apr 4, 2019
    Configuration menu
    Copy the full SHA
    29c5962 View commit details
    Browse the repository at this point in the history

  4. Convert Keeper to an interface and return underlying struct as pointer 

    Because a cache is being kept on the keeper itself currently, it must
get passed around as a pointer so that the cache remains consistent.
    @aaronc
    aaronc committed Apr 4, 2019
    Configuration menu
    Copy the full SHA
    cbcec49 View commit details
    Browse the repository at this point in the history

Commits on Apr 17, 2019

  1. Add willUpgrader and onUpgrader, and remove doShutdowner from upgrade… 

    … keeper

Upon testing, halting the chain by methods other than a panic (such as os.Exit) actually causes issues between nodes because the other nodes instead of processing their own doShutdowners to trigger upgrades actually just hang trying to connect after enough nodes exit. The onUpgrader allows nodes to trigger some process before the panic, and willUpgrader allows nodes to prepare for upgrades before they actually need to be applied. Still needs more testing
    @aaronc
    aaronc committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    7f9dc6c View commit details
    Browse the repository at this point in the history

  2. Fix upgrade keeper tests

    @aaronc
    aaronc committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    b429635 View commit details
    Browse the repository at this point in the history

  3. Add the ability to retrieve the height of an applied upgrade and clea… 

    …nup CLI
    @aaronc
    aaronc committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    dce1806 View commit details
    Browse the repository at this point in the history

  4. Fix lint error

    @aaronc
    aaronc committed Apr 17, 2019
    Configuration menu
    Copy the full SHA
    d368a70 View commit details
    Browse the repository at this point in the history

Commits on Apr 18, 2019

  1. Rename upgrade query height -> query applied-height

    @aaronc
    aaronc committed Apr 18, 2019
    Configuration menu
    Copy the full SHA
    13fdf0c View commit details
    Browse the repository at this point in the history

  2. Update upgrade module docs

    @aaronc
    aaronc committed Apr 18, 2019
    Configuration menu
    Copy the full SHA
    38b28f8 View commit details
    Browse the repository at this point in the history