* initial changes
* poetry fix
* Address ruff
* Install scripts issues
* Experiment a little bit
* Okay now try for rocky linux and use 3.12 instead
* Remove the now unused thing
* Use dnf for consistency
* Simplify installations
* Still need git
* relock poetry with 2.2.0
* relock poetry with 2.2.0
* try `git checkout main poetry.lock && .penv/bin/poetry lock` on altendky's system
---------
Co-authored-by: Kyle Altendorf <sda@fstab.net>
* Remove scripting that attempts to find and install node
* Remove using direction in start-gui.sh
* Remove unneeded npm_global files - only used to install node
* Handle guess where node or npm is not installed
* Add setup-node to test scripts workflow
* make sure to checkout submodules
* Update all installer builds to use the version of node specified in chia-blockchain-gui .nvmrc
* Update the workflows that didn't previously use the setup-node action to use it, to make future updates easier (this action now works with all the currently supported platforms we build on)
* fixup coverage handling with conditional macos-intel execution
* more mess. for the moment at least
* let a few local-only steps run regardless
* correct the version
* Swap to self hosted mac intel runners for installer build
* Change the test to also run self-hosted
* Use self hosted mac intel runners, and limit some things to not always run on mac intel
* Split the new mac intel rule to its own step
* Make some CI conditional for forks
Signed-off-by: wallentx <william.allentx@gmail.com>
* fix conditional for build installers
Signed-off-by: wallentx <william.allentx@gmail.com>
* fix macos ARM and Linux ARM onnpre-commit
Signed-off-by: wallentx <william.allentx@gmail.com>
* Testing SSH signing
* Remove conditional for checking signed commits
* Use macos-15 instead of macos-latest, and use public gh linux arm
* fix yaml array vs literal string
---------
Signed-off-by: wallentx <william.allentx@gmail.com>
<!-- 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) -->
* Update to node 20
* Update another script for minimum npm version
* update check for npm >= 10
* update npm version
---------
Co-authored-by: Zlatko <zlatko@chia.net>
<!-- 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) -->
* simplify BlockTools by making include_transactions=True independent from transaction_data
* improve error message in validate_coins()
* we don't know if a block will become a transaction block, we we can't mutate state as if spends will make it in until once it's confirmed
* factor out NewBlockGenerator creation into a function
* remove unused variable
* use latest version of test-cache
* extend timeout
* fix coverage
* extend sync timeout
* when loading the cached test blockchains, check that the first few blocks match what we would have generated if it wasn't cached. This should make CI highlight whenever BlockTools changes some way of how chains are generated that alters the chain output. When this happens, we should also update the test-cache repo
* update test-cache version to use for CI
* exempt debug message from test coverage
Earle LoweandGitHub
William AllenandGitHub
ChiaAutomationandGitHub
StarttoasterandGitHub
Richard KissandGitHub
Izumi HoshinoandGitHub
Arvid NorbergandGitHub
StarttoasterandGitHub
Amine Khaldi
Zachary BrownandGitHub
Patrick MaslanaandGitHub