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 proving check 0 - ERROR: rg is nil #10098

Closed
8 of 18 tasks
ghost opened this issue Jan 23, 2023 · 1 comment
Closed
8 of 18 tasks

lotus-miner proving check 0 - ERROR: rg is nil #10098

ghost opened this issue Jan 23, 2023 · 1 comment
Labels
kind/bug Kind: Bug

Comments

@ghost
Copy link

ghost commented Jan 23, 2023

Checklist

  • This is not a security-related bug/issue. If it is, please follow please follow the security policy.
  • This is not a question or a support request. If you have any lotus related questions, please ask in the lotus forum.
  • This is not a new feature request. If it is, please file a feature request instead.
  • This is not an enhancement request. If it is, please file a improvement suggestion instead.
  • I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
  • I am running the Latest release, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
  • I did not make any code changes to lotus.

Lotus component

  • lotus daemon - chain sync
  • lotus miner - mining and block production
  • lotus miner/worker - sealing
  • lotus miner - proving(WindowPoSt)
  • lotus miner/market - storage deal
  • lotus miner/market - retrieval deal
  • lotus miner/market - data transfer
  • lotus client
  • lotus JSON-RPC API
  • lotus message management (mpool)
  • Other

Lotus Version

lotus-miner version 1.18.0+mainnet+git.bd10bdf99

Describe the Bug

lotus-miner proving check 0 

ERROR: rg is nil

command fails with unclear error message

lotus-miner proving compute wondow-post 0 works fine

Took 2m45.159382168s
[{"Deadline":0,"Partitions":[{"Index":0,"Skipped":[0]}],"Proofs":[{"PoStProof":8,"ProofBytes":"p0x7Qh9ROI5/jhzQQuwTD849yLU3A8n3QScZdTG+9p47e6hDQAOJwxEP0rPP5vnTtu40bUAXhRr40V3ehlu8DB2v/tMKUxc5mxY3J2wtHUztWDFog7Bh2JKwq24Snz36AWRJPrO2VUwhwOXgUc+upx/3qcQHUMX3T9dWIbGszw/XRLeTPIDl2BFuf/I1eP9RpgVVtJcOShONS0P1JCK9PZs7FLSln4FaXKQFgE14dZAe9PYUQ9/AnccE9nk4e6iN"}],"ChainCommitEpoch":0,"ChainCommitRand":null}]

Logging Information

tell me what you need and we get it

Repo Steps

  1. Run '...'
  2. Do '...'
  3. See error '...'
    ...
@ghost ghost added kind/bug Kind: Bug need/triage labels Jan 23, 2023
@rjan90
Copy link
Contributor

rjan90 commented Jan 23, 2023

Hey @f8-fil-ops! Thank you so much for the issue report. This issue has been fixed with this PR: #9643, which is included in Lotus v1.19.0 and higher

@rjan90 rjan90 closed this as completed Jan 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Kind: Bug
Projects
None yet
Development

No branches or pull requests

1 participant