* server: Enable and fix `mypy` in `server.py`
* Add a comment about the `Message` hint
Co-authored-by: Kyle Altendorf <sda@fstab.net>
* Tweak assert message
Co-authored-by: Kyle Altendorf <sda@fstab.net>
* Make `name` non-optional
Co-authored-by: Kyle Altendorf <sda@fstab.net>
* Properly reject incoming connections to crawlers
Co-authored-by: Kyle Altendorf <sda@fstab.net>
* Hint `StreamResponse` and return the existing `WebSocketResonse`
* Raise if `remote` is `None`
* Restore old behaviour: succeed, don't fail for self connection
* Raise `HTTPInternalServerError` if `remote` is `None`
* Cast config values to `int`
Co-authored-by: Kyle Altendorf <sda@fstab.net>
* 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>
Includes:
Remaining fee estimator integrations
Removal of SkyNFT links
Offer Builder royalty amounts when creating an offer for an NFT
Memo field when sending XCH (memos not shown due to backend issue)
Removal of backup.chia.net references
Update to Electron 20.3.5
NFT metadata caching fix for non-UTF8 charsets
Fix for switching between farming/wallet mode
Fix for importing/adding key and including whitespace in key label
Assorted code cleanup
* 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>
Seems like the idea was to log an overview of message types for the
currently active api calls whenever we have multiples of 100 running.
This currently isn't working at all because `len(message_types) % 100 ==
0` will only trigger if there are 100 different message types in the
counter (we don't even have that much different messages). A fix would
be to check `message_types.total() % 100 == 0`. But then, if we hover
around 100 active messages this will repeatedly trigger logs since we
decrement for each processed message, im not sure this all makes much
sense and we anyway log all received message types with `DEBUG` logs so
i decided to just drop this. If someone thinks we should keep it with
the fix or has ideas to make this a more reasonable log instead of
dropping it, let me know :)
