* chia plotnft CLI improvements
* use CliRpcConnectionError
* add check to show
* fix typo
* Update plotnft CLI to newer framework
* Fix help cut-paste error
* add test using new framework
* some minor fixes
* use click.Choice for pool/local option
* some click options
* Some more plotnft cli tests
* drop test_pool_cmdline from mypy-exclusions
* mypy fixes
* several fixes
* Add leave test
* join tests
* more join tests
* missing await
* Try setting config
* use root_path from NeedsWalletRPC
* linting
* Some cleanup
* Add claim tests
* Improved tests
* refactor some test code
* Add inspect tests
* Skip bad test for now
* Add in change payout tests
* quoting error
* Add test for get_login_link
* Add in a few negative tests for join
* Few more tests
* Experment with clirunner env overrides
* put back chia_root into context dict
* Some cleanup and one more test
* maybe final test
* some updates
* some dedup and reorg of test code
* run trusted and untrusted paramertization
* make reuse puzhash stuff work
* Add in required mock object for test_update_pool_config_new_config
* rearrange code per review comment - limit use of NeedsWalletRPC to chia_command
* Add in plotnft click parsing tests
* added ability to pass in obj to runner invoke
* Add in some more test cases
* fix up create issues with config
* Add in couple more test cases for error conditions
* Minor code cleanup
* Use long options for readability, minor code cleanup
* Use config file for farmer rpc port
* simplify code
* Add testing for prompt cases
* Add mocking for default_root_path
* context cleanup
* temp debugging output
* patch the proper object
* move some wallet fixtures into top level conftest and remove conftest import
* merge to origin/main
* `VALIDATE_GITHUB_ACTIONS: true`
* fixups
* there
* and the config...
* wrong way, back again
* shellcheck
* tweak
* wrong place
* see ya super-linter
* Revert "wrong place"
This reverts commit 478fde7b2e.
* -shellcheck
* reintroduce actionlint/shellcheck issue to show failure
* Revert "reintroduce actionlint/shellcheck issue to show failure"
This reverts commit 24b034522f.
* blech
* fix trusted wallet sync on deep reorg
* handle long sync exception case in finish sync
* fix_wallet_sync_test
* fix test_long_sync_wallet
* reconnect only untrusted node in test
* fix long_sync test, update only on finish_sync()
* revert add_blocks_in_batches
* types
* fix flakey test_long_reorg_nodes_and_wallet
<!-- Merging Requirements:
- Please give your PR a title that is release-note friendly
- In order to be merged, you must add the most appropriate category
Label (Added, Changed, Fixed) to your PR
-->
<!-- Explain why this is an improvement (Does this add missing
functionality, improve performance, or reduce complexity?) -->
### Purpose:
<!-- Does this PR introduce a breaking change? -->
### Current Behavior:
### New Behavior:
<!-- As we aim for complete code coverage, please include details
regarding unit, and regression tests -->
### Testing Notes:
<!-- Attach any visual examples, or supporting evidence (attach any
.gif/video/console output below) -->
<!-- Merging Requirements:
- Please give your PR a title that is release-note friendly
- In order to be merged, you must add the most appropriate category
Label (Added, Changed, Fixed) to your PR
-->
<!-- Explain why this is an improvement (Does this add missing
functionality, improve performance, or reduce complexity?) -->
### Purpose:
<!-- Does this PR introduce a breaking change? -->
### Current Behavior:
### New Behavior:
<!-- As we aim for complete code coverage, please include details
regarding unit, and regression tests -->
### Testing Notes:
<!-- Attach any visual examples, or supporting evidence (attach any
.gif/video/console output below) -->
<!-- Merging Requirements:
- Please give your PR a title that is release-note friendly
- In order to be merged, you must add the most appropriate category
Label (Added, Changed, Fixed) to your PR
-->
<!-- Explain why this is an improvement (Does this add missing
functionality, improve performance, or reduce complexity?) -->
### Purpose:
<!-- Does this PR introduce a breaking change? -->
### Current Behavior:
### New Behavior:
<!-- As we aim for complete code coverage, please include details
regarding unit, and regression tests -->
### Testing Notes:
<!-- Attach any visual examples, or supporting evidence (attach any
.gif/video/console output below) -->
Earle LoweandGitHub
Kyle AltendorfandGitHub
Matt HauffandGitHub
Arvid NorbergandGitHub
Chris MarslenderandGitHub
Almog De PazandGitHub
Florin ChiricaandGitHub
Amine KhaldiandGitHub