You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ venv/bin/chia plots create -k 20 -n 1 -b 4096 -r 8 -t /chia/temporary -d /chia/final/22:26:46.652 src.plotting.create_plots : WARNING CREATING PLOTS WITH SIZE k=20, which is less than the minimum required for mainnet22:26:46.652 src.plotting.create_plots : INFO Creating 1 plots of size 20, pool public key: a55d8fdada643a43d86a889c2c746ce848c0e2d00f7c012fc4c6e77d1e2f9f54a99dd38af59f8284f2178b810ecc7a95 farmer public key: b0a374845f4f4d6eab62fc4c5e17965d82ad7eee105818e5bd0cfcb46275a16acc4cd30955779bec841a716473416b2122:26:46.658 src.plotting.create_plots : INFO Adding directory /chia/final to harvester for farming22:26:46.682 src.plotting.create_plots : INFO Starting plot 1/1Caught plotting error: Stripe size too largeTraceback (most recent call last): File "venv/bin/chia", line 33, in <module> sys.exit(load_entry_point('chia-blockchain', 'console_scripts', 'chia')()) File "/home/altendky/repos/chia-blockchain/src/cmds/chia.py", line 60, in main return chia(args, parser) File "/home/altendky/repos/chia-blockchain/src/cmds/chia.py", line 54, in chia return args.function(args, parser) File "/home/altendky/repos/chia-blockchain/src/cmds/plots.py", line 158, in handler create_plots(args, root_path) File "/home/altendky/repos/chia-blockchain/src/plotting/create_plots.py", line 153, in create_plots args.nobitfield,RuntimeError: std::exception
There are known issues with k's below 25. The way python imports the C++ plotting library means that it can only report the C failure. I'll add warning or disable under 25 in the python side.
Describe the bug
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It seems to detect a bad situation (stripe size too large) so I would expect it to not
RuntimeError
following that.Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: