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

use pool production tip to compute performance #1168

Merged
merged 5 commits into from
Dec 12, 2019
Merged

use pool production tip to compute performance #1168

merged 5 commits into from
Dec 12, 2019

Commits on Dec 12, 2019

  1. use pool production tip to compute performance 

    instead of the node tip. The production worker might not have caught up with
the network yet and therefore, yield statistics that are slightly off
    @KtorZ
    KtorZ committed Dec 12, 2019
    Configuration menu
    Copy the full SHA
    f68691a View commit details
    Browse the repository at this point in the history

  2. use production tip for computing progress + make computeProgress a pu… 

    …re function
    @KtorZ
    KtorZ committed Dec 12, 2019
    Configuration menu
    Copy the full SHA
    2ee8945 View commit details
    Browse the repository at this point in the history

  3. add unit test to verify progress calculation when failing to list pools

    @KtorZ
    KtorZ committed Dec 12, 2019
    Configuration menu
    Copy the full SHA
    4f11b8b View commit details
    Browse the repository at this point in the history

  4. fix prodTip calculation (maximumBy is partial)

    @KtorZ
    KtorZ committed Dec 12, 2019
    Configuration menu
    Copy the full SHA
    a600b5d View commit details
    Browse the repository at this point in the history

  5. fix newStakePoolLayer calls after addition of the cache directory

    @KtorZ
    KtorZ committed Dec 12, 2019
    Configuration menu
    Copy the full SHA
    31123c5 View commit details
    Browse the repository at this point in the history