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.

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

feat: miner cli: sectors list upgrade-bounds tool #10923

Merged
merged 1 commit into from
May 30, 2023

Conversation

magik6k
Copy link
Contributor

@magik6k magik6k commented May 26, 2023

Related Issues

(Mostly?) Addresses #10908

Proposed Changes

Additional Info

image

  • Output without --deal-terms just shows sectors bucketed by expiration
  • Output with --deal-terms shows how many sectors worth of deals with a given expiration could be accepted into available sectors

Checklist

Before you mark the PR ready for review, please make sure that:

  • Commits have a clear commit message.
  • PR title is in the form of of <PR type>: <area>: <change being made>
    • example: fix: mempool: Introduce a cache for valid signatures
    • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
    • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
  • New features have usage guidelines and / or documentation updates in
  • Tests exist for new functionality or change in behavior
  • CI is green

@magik6k magik6k requested a review from a team as a code owner May 26, 2023 10:25
@magik6k magik6k force-pushed the feat/sectors-upgradebounds-cli branch from 75a56ec to 85a2a9d Compare May 26, 2023 10:27
@magik6k magik6k force-pushed the feat/sectors-upgradebounds-cli branch from 85a2a9d to 14f9770 Compare May 26, 2023 10:29
},
&cli.BoolFlag{
Name: "deal-terms",
Usage: "bucket by how many deal-sectors can start at a given expiration",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure I fully understand this. We don't pass in an expiration here so what does this statement mean?
I initially took this to mean filter all deal sectors which can start past a certain time

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Basically when you're packing datacap deals into sectors, the sector expiration must fit two constraints:

  • Sector expiration must be larger than deal end - so that the sector is alive for the whole duration of the deal
  • Sector expiration must NOT be longer than 90 days after deal expiration - so that you don't get the datacap boost for too much longer than the deal is requesting to be stored for

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(the --deal-terms mode shows how many deals you can accept at a given deal end epoch)

@magik6k magik6k merged commit 6cc506f into master May 30, 2023
@magik6k magik6k deleted the feat/sectors-upgradebounds-cli branch May 30, 2023 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants