* Add Python 3.11 to CI
* 3.11 in the install scripts
* ${{ format('{0}.0-alpha - {0}.X', matrix.python) }}
* bump chiavdf and chiabip158 for releases with 3.11 wheels
* also bump blspy and clvm-tools-rs
* drop the extra .X for the python setup version
* chia_rs==0.1.13
* Update install.sh
* pyinstaller==5.5
* less mutable defaults
* memory_profiler
* assert sqlite3.threadsafety >= 1
* create tasks for stopping services
(cherry picked from commit 3384714f2e3e0bdc8c3d3741027e9e4fb69a6002)
* psutil==5.9.4
* drop memory_profiler transitive dep since it now supports 3.11
* drop redundant pre-release python getting incantation
* watchdog==2.2.0
* black for py311
* Setting actions version to latest
* Fix decode-base64-into-file-action version
Cannot use normal versioning as https://github.com/kitek/decode-base64-into-file-action does not use semver and GHA cannot interpret the version without the exact version specified.
* Satisfying new version shellcheck linting test
Co-authored-by: Zachary Brown <z.brown@chia.net>
* Add a workflow for scanning python deps for chia-blockchain
Signed-off-by: wallentx <william.allentx@gmail.com>
* Add a blank line to separate steps and move the test secret step
Signed-off-by: wallentx <william.allentx@gmail.com>
Signed-off-by: wallentx <william.allentx@gmail.com>
* Use Chia-Network/actions/check-commit-signing
* @add_check_commit_signing
* use @main
* move check commit signing to a dedicated workflow
* Update check-commit-signing.yml
* add cache to speed up manage_clvm/clvm_hex pre-commit check
* Update tools/manage_clvm.py
* add version to cache along with handling of incorrect versions
* force skipping the cache in ci
* Add `-l` option to `install.sh` and use it for linux tests on CI
* Implement and test `tools/legacy_keyring.py`
* Update install.sh
Co-authored-by: Jeff <paninaro@gmail.com>
Co-authored-by: Jeff <paninaro@gmail.com>
* Add a workflow for scanning python deps
* Removed the requirements.txt file from the commit
* Change to any pull request for running the workflow
* Remove some wording and fix concurrency
* Change python version
* Add a step to pip install requirements.
* Adding skip unresolved when pip installing requirements.txt
* Pip install ignore installed
* Adding a step to update pip
* Fix spacing
* Running each line for the pip install.
* Adding continue-on-error when pip installing
* using skip-unresolved with when monitoring with snyk.
* Remove pip install step and add names to steps
* Removed leading line and set "Cancel-in-progress" for concurrency to true
* Change when the workflow runs to pushes and PRs
* Update .github/workflows/snyk-python-scan.yml
Co-authored-by: Kyle Altendorf <sda@fstab.net>
* Update build-windows-installer.yml
Use GITHUB_OUTPUT instead of set-output.
Use PowerShell syntax for PowerShell, Bash Syntax for Bash.
Why?
GitHub is deprecating set-output as per their blog:
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Signed-off-by: wallentx <william.allentx@gmail.com>
* Use GITHUB_OUTPUT in workflows
Use GITHUB_OUTPUT in workflows instead of set-output.
Why?
GitHub is deprecating set-output as per their blog:
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Signed-off-by: wallentx <william.allentx@gmail.com>
* Workflow dispatch added to MacOS and Linux ARM
Signed-off-by: wallentx <william.allentx@gmail.com>
* Fix Tests for Windows
Use PowerShell syntax for Windows, Bash for others.
Signed-off-by: wallentx <william.allentx@gmail.com>
* Use setup-python@v4
Update to resolve the set-output warnings
Signed-off-by: wallentx <william.allentx@gmail.com>
* Fix Tests and Benchmarks for Windows
Signed-off-by: wallentx <william.allentx@gmail.com>
* Update test.yml
Fix missed setup-python@v2
Signed-off-by: wallentx <william.allentx@gmail.com>
* Use Chia setup-python wrapper
Signed-off-by: wallentx <william.allentx@gmail.com>
* Revert "Fix Tests and Benchmarks for Windows"
This reverts commit 4fbc6d354b.
Signed-off-by: wallentx <william.allentx@gmail.com>
* Revert "Fix Tests for Windows"
This reverts commit 5860048344.
Signed-off-by: wallentx <william.allentx@gmail.com>
* Use bash for all OS to get pip cache dir
Signed-off-by: wallentx <william.allentx@gmail.com>
* Fixing windows workflow error
* Replacing instances of Out-File
* Fixing ps1 -> bash
* Fixing path when ps1 -> bash
* Escaping Windows path when using bash
* Escaping Windows path when using bash
Signed-off-by: wallentx <william.allentx@gmail.com>
Co-authored-by: zcomputerwiz <zcomputerwiz@users.noreply.github.com>
* retryAfter: 2 for conflict check
* two minutes
* Use 'Chia-Network/actions/label-conflict@main' for conflict check action
Co-authored-by: ChiaMineJP <admin@chiamine.jp>
* Fix ref check to github.ref instead of github.event.ref, so its always present (#13661)
* Fixing s3 upload conditional for windows builds (#13658)
Co-authored-by: Chris Marslender <chrismarslender@gmail.com>
* Revert "Set up json files for python versions, to run a more restricted set on private testing repos (#13641)"
This reverts commit aff3cf5c10.
* hard coded poc
* ${{ 'limited' }}
* env.MATRIX_MODE
* via a the existing configure step
* and ad the parameter
* also define the output
* conditional on not being the main repo
* Fix secret check for windows/mac (which have more granular checks because of different secret types)
* Make all the workflows use granular secret checks
* Fix whitespace issues
* Add bladebit for pre-release mac builds. Update pyinstaller to include bladebit if the file exists
* Make plotter inclusion conditional based on if they are present for the build or not
* temp: always get pre-release bladebit plotter for testing
* Only include bladebit on pre-release
* add final coverage handling
* switch to development coverage
* correct url
* only run one directory for now
* only 3.10
* delete windows data for now
* drop the 35% failure point
* recover full test matrix
* Use regular coverage
* Update test.yml
* put coverage reporting into an artifact
* oops
* oopsy
* pytest-cov
* maybe
* maybe help out flakes
* farm the spend bundle...
* some more
* more funds for the did test?
* more...
* report chia/ and tests/ separately
* job_timeout = 45 for core
* tidy and disable diff-cover
* remove job_timeout = 45
* --rcfile=.coveragerc
* Update .github/workflows/test.yml
* revert time and blocks
* assert spend is in mempool, lower times and block count
* remove sleep
* lint
* up timeout
* cat test - farm blocks until spend is included
* add spend check for nft endpoints
* fix nft endpoint test
* remove unused code
* 4
Co-authored-by: almog <almogdepaz@gmail.com>
Even the blocks and plots cache appears to finish in its entirety in 15 seconds, so the 1 minute 'segment' (not sure exactly what that means) timeout seems reasonable.
https://github.com/actions/cache/issues/810