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

lotus-miner: expose Config in StorageMiner; add SealingPipelineState API endpoint #7513

Closed
wants to merge 1 commit into from

Conversation

nonsense
Copy link
Member

This PR is exposing the lotus-miner StorageMiner Config, as well as adding a SealingPipelineState API to be consumed by the markets node to determine if a miner is available to accept new deals.

The idea is to improve the deal acceptance filter to take into account the state of the sealing pipeline when accepting deals.

Copy link
Contributor

@dirkmc dirkmc left a comment

Choose a reason for hiding this comment

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

Looks good - just one nit.

Could you post an example of what the output looks like here too

api/types.go Outdated Show resolved Hide resolved
@nonsense nonsense force-pushed the nonsense/sealing-pipeline-state branch from 31aeb4a to 15ed5cb Compare October 15, 2021 11:40
Comment on lines +130 to +133
jobs, err := sm.WorkerJobs(ctx)
if err != nil {
return nil, xerrors.Errorf("getting worker jobs: %w", err)
}
Copy link
Contributor

Choose a reason for hiding this comment

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

WorkerJobs is already exposed no the RPC

@@ -60,6 +61,8 @@ type StorageMinerAPI struct {

EnabledSubsystems api.MinerSubsystems

Config *config.StorageMiner
Copy link
Contributor

Choose a reason for hiding this comment

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

At least the Sealing part of the config supports auto-reloading (this is why we have the getConfig function in the sealing package) - but just putting this config here like that won't get you updated values after changing the config on disk

Copy link
Contributor

Choose a reason for hiding this comment

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

(side note: we really need to unify how we support dynamic config, and make that nicer / more fully supported)

Copy link

codecov bot commented Sep 3, 2024

Codecov Report

Attention: Patch coverage is 3.57143% with 27 lines in your changes missing coverage. Please review.

Project coverage is 39.82%. Comparing base (afe54ab) to head (15ed5cb).
Report is 8009 commits behind head on master.

Files with missing lines Patch % Lines
node/impl/storminer.go 0.00% 14 Missing ⚠️
cmd/lotus-miner/sealing.go 0.00% 13 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #7513      +/-   ##
==========================================
- Coverage   39.86%   39.82%   -0.04%     
==========================================
  Files         631      631              
  Lines       66913    66941      +28     
==========================================
- Hits        26673    26662      -11     
- Misses      35629    35659      +30     
- Partials     4611     4620       +9     
Files with missing lines Coverage Δ
api/api_storage.go 0.00% <ø> (ø)
api/types.go 52.77% <ø> (ø)
node/builder_miner.go 94.89% <100.00%> (+0.03%) ⬆️
cmd/lotus-miner/sealing.go 39.01% <0.00%> (-3.01%) ⬇️
node/impl/storminer.go 26.97% <0.00%> (-0.75%) ⬇️

... and 21 files with indirect coverage changes

@rjan90 rjan90 added area/miner-maintenance need/author-input Hint: Needs Author Input and removed team/curio labels Nov 25, 2024
Copy link

github-actions bot commented Dec 1, 2024

Thank you for submitting the PR and contributing to lotus! Lotus maintainers need more of your input before merging it, please address the suggested changes or reply to the comments or this PR will be closed in 72 hours. You are always more than welcome to reopen the PR later as well!

Copy link

github-actions bot commented Dec 8, 2024

Thank you for submitting the PR and contributing to lotus! Lotus maintainers need more of your input before merging it, please address the suggested changes or reply to the comments or this PR will be closed in 72 hours. You are always more than welcome to reopen the PR later as well!

Copy link

Thank you for submitting the PR and contributing to lotus! Lotus maintainers need more of your input before merging it, please address the suggested changes or reply to the comments or this PR will be closed in 72 hours. You are always more than welcome to reopen the PR later as well!

@rjan90
Copy link
Contributor

rjan90 commented Dec 20, 2024

Closing PR as stale, will follow up and fix why stalebot was unable to do it automatically in: #12799

@rjan90 rjan90 closed this Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants