We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Similar to issue #4220, on a restart the lotus-miner is resetting the Max Piece Size down to 1 MiB.
Price per GiB/Epoch Verified Min. Piece Size (padded) Max. Piece Size (padded) Expiry (Epoch) Expiry (Appx. Rem. Time) Seq. No. 0.0000001 FIL 0.0000001 FIL 128 MiB 1 MiB 237661 719h59m0s 79
To Reproduce Steps to reproduce the behavior:
lotus-miner storage-deals set-ask --price 0.0000001 --verified-price 0.0000001 --min-piece-size 128MiB --max-piece-size 32GiB
lotus-miner storage-deals get-ask
Expected behavior Miner should store set-ask values between restarts.
Screenshots If applicable, add screenshots to help explain your problem.
Version (run lotus version): lotus version 0.10.2+git.8bb84acbc
lotus version
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
We have the same issue.
See the error and get ask config below:
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Describe the bug
Similar to issue #4220, on a restart the lotus-miner is resetting the Max Piece Size down to 1 MiB.
To Reproduce
Steps to reproduce the behavior:
lotus-miner storage-deals set-ask --price 0.0000001 --verified-price 0.0000001 --min-piece-size 128MiB --max-piece-size 32GiB
lotus-miner storage-deals get-ask
and check Min/Max Piece SizeExpected behavior
Miner should store set-ask values between restarts.
Screenshots
If applicable, add screenshots to help explain your problem.
Version (run
lotus version
):lotus version 0.10.2+git.8bb84acbc
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: