Skip to content

Conversation

altendky
Copy link
Contributor

@altendky altendky commented Sep 5, 2025

Source hash: ebf8105
Remaining commits: 0

AmineKhaldi and others added 30 commits July 23, 2025 09:40
Fix rebasing fast forward spends on new peak.
…age exists (#19865)

Handle items that spend an older ff version when newer lineage exists.
…nt/main_from_release_2.5.5_d2e9df3b510fdf8f9312af58096378902baddc67
fast-forward spends can be treated as regular spends if the coin doesn't appear to support the rebasing
…_macos (#19890)

build(deps): bump form-data in /build_scripts/npm_macos

Bumps [form-data](https://github.com/form-data/form-data) from 4.0.0 to 4.0.4.
- [Release notes](https://github.com/form-data/form-data/releases)
- [Changelog](https://github.com/form-data/form-data/blob/master/CHANGELOG.md)
- [Commits](form-data/form-data@v4.0.0...v4.0.4)

---
updated-dependencies:
- dependency-name: form-data
  dependency-version: 4.0.4
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Include plotNFT rewards in get_farmed_amount

* Add flag to include pool rewards in farm summary

* Add -i for short flag

* Fix expected args

* Include additional farming detail

* Include additional farming detail

* Format/organize output

* Move block rewards

* Update test

* Format

* Update test_farm_cmd.py

* revert test bool

* Passing tests

* Added test for 'include_pool_rewards=True'

* Address linting errors
* build(deps): bump mypy from 1.15.0 to 1.17.0

---
updated-dependencies:
- dependency-name: mypy
  dependency-version: 1.17.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

* handle mypy commentary

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Kyle Altendorf <[email protected]>
* bump chia_rs to 0.29

* correct return value from get_spends_for_trusted_block()

* remove unnecessary casts

* adjust test for the new error messages in chia_rs

* Update chia/full_node/full_node_rpc_api.py

Co-authored-by: Kyle Altendorf <[email protected]>

---------

Co-authored-by: Kyle Altendorf <[email protected]>
* Change `TransactionRecord` to use dict instead of list of tuples for memos

* Update streamable and fix tests

* Update test to accidentally fixed memos generation

* Remove `TransactionRecord.*_json_dict_convenience`

* Fix test

* Use AddressType library in WSM method

* Use AddressType library in transaction_store method
…h R-CATs (#19831)

* Port `test_trade_cancellation`

* Port `test_trade_conflict`

* Port `test_trade_bad_spend`

* Port `test_trade_high_fee`

* Port `test_aggregated_trade_state`
* Port `get_wallet_balance(s)`

* Use Streamable dict functionality
Remove some dependencies in `chia.server`.
Bumps [mypy](https://github.com/python/mypy) from 1.17.0 to 1.17.1.
- [Changelog](https://github.com/python/mypy/blob/master/CHANGELOG.md)
- [Commits](python/mypy@v1.17.0...v1.17.1)

---
updated-dependencies:
- dependency-name: mypy
  dependency-version: 1.17.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [ruff](https://github.com/astral-sh/ruff) from 0.12.4 to 0.12.7.
- [Release notes](https://github.com/astral-sh/ruff/releases)
- [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md)
- [Commits](astral-sh/ruff@0.12.4...0.12.7)

---
updated-dependencies:
- dependency-name: ruff
  dependency-version: 0.12.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [pyinstaller](https://github.com/pyinstaller/pyinstaller) from 6.14.2 to 6.15.0.
- [Release notes](https://github.com/pyinstaller/pyinstaller/releases)
- [Changelog](https://github.com/pyinstaller/pyinstaller/blob/develop/doc/CHANGES.rst)
- [Commits](pyinstaller/pyinstaller@v6.14.2...v6.15.0)

---
updated-dependencies:
- dependency-name: pyinstaller
  dependency-version: 6.15.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [anyio](https://github.com/agronholm/anyio) from 4.9.0 to 4.10.0.
- [Release notes](https://github.com/agronholm/anyio/releases)
- [Changelog](https://github.com/agronholm/anyio/blob/master/docs/versionhistory.rst)
- [Commits](agronholm/anyio@4.9.0...4.10)

---
updated-dependencies:
- dependency-name: anyio
  dependency-version: 4.10.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
---
updated-dependencies:
- dependency-name: aiohttp
  dependency-version: 3.12.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…#19910)

Bumps [tmp](https://github.com/raszi/node-tmp) from 0.2.1 to 0.2.4.
- [Changelog](https://github.com/raszi/node-tmp/blob/master/CHANGELOG.md)
- [Commits](raszi/node-tmp@v0.2.1...v0.2.4)

---
updated-dependencies:
- dependency-name: tmp
  dependency-version: 0.2.4
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…50801 (#19906)

build(deps): bump types-setuptools

Bumps [types-setuptools](https://github.com/typeshed-internal/stub_uploader) from 80.9.0.20250529 to 80.9.0.20250801.
- [Commits](https://github.com/typeshed-internal/stub_uploader/commits)

---
updated-dependencies:
- dependency-name: types-setuptools
  dependency-version: 80.9.0.20250801
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps chia-puzzles-py from 0.20.1 to 0.20.2.

---
updated-dependencies:
- dependency-name: chia-puzzles-py
  dependency-version: 0.20.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [boto3](https://github.com/boto/boto3) from 1.39.11 to 1.40.3.
- [Release notes](https://github.com/boto/boto3/releases)
- [Commits](boto/boto3@1.39.11...1.40.3)

---
updated-dependencies:
- dependency-name: boto3
  dependency-version: 1.40.3
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…19842)

* Port `test_nft_offer_nft_for_cat`

* Port `test_nft_offer_nft0_and_xch_for_cat`

* Forgot to delete an unnecessary state process

* Port `test_nft_offer_sell_nft_for_cat`

* Port `test_nft_offer_request_nft_for_cat`

* Port `test_complex_nft_offer`

* Fix a new issue in complex test

* Minor change.

---------

Co-authored-by: Amine Khaldi <[email protected]>
… get_unspent_lineage_info_for_puzzle_hash (#19909)

Be explicit about falling back to coin_puzzle_hash index in get_unspent_lineage_info_for_puzzle_hash.
arvidn and others added 17 commits September 3, 2025 09:24
* stub chiapos2 API

* update block tools to support v2 plots when generating chains, as well as using the solve_proof() stub in the solver

* review comments
Bumps [coverage](https://github.com/nedbat/coveragepy) from 7.10.4 to 7.10.5.
- [Release notes](https://github.com/nedbat/coveragepy/releases)
- [Changelog](https://github.com/nedbat/coveragepy/blob/master/CHANGES.rst)
- [Commits](nedbat/coveragepy@7.10.4...7.10.5)

---
updated-dependencies:
- dependency-name: coverage
  dependency-version: 7.10.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…CH (#20016)

improve logging of NO_OVERFLOWS_IN_FIRST_SUB_SLOT_NEW_EPOCH
* remove redundant comment

* add solver to farmer group
Source hash: ecb54a5
Remaining commits: 1

In addition to changes in the network protocol and its generated files,
between the original and this checkpoint, here are the introduced code
changes in order to get back to a working state:

```diff
diff --git a/chia/_tests/harvester/test_harvester_api.py b/chia/_tests/harvester/test_harvester_api.py
index 479adb6..5c9e6d5 100644
--- a/chia/_tests/harvester/test_harvester_api.py
+++ b/chia/_tests/harvester/test_harvester_api.py
@@ -51,7 +51,7 @@ async def harvester_environment(
 
 def signage_point_from_block(
     block: FullBlock, constants: ConsensusConstants
-) -> harvester_protocol.NewSignagePointHarvester:
+) -> harvester_protocol.NewSignagePointHarvester2:
     sp_index = block.reward_chain_block.signage_point_index
     challenge_hash = block.reward_chain_block.pos_ss_cc_challenge_hash
     sp_hash = (
@@ -59,7 +59,7 @@ def signage_point_from_block(
         if block.reward_chain_block.reward_chain_sp_vdf
         else challenge_hash
     )
-    return harvester_protocol.NewSignagePointHarvester(
+    return harvester_protocol.NewSignagePointHarvester2(
         challenge_hash=challenge_hash,
         difficulty=uint64(constants.DIFFICULTY_STARTING),
         sub_slot_iters=uint64(constants.SUB_SLOT_ITERS_STARTING),
@@ -75,7 +75,7 @@ def create_test_setup(
     harvester_environment: HarvesterTestEnvironment,
     default_400_blocks: list[FullBlock],
     blockchain_constants: ConsensusConstants,
-) -> tuple[HarvesterTestEnvironment, harvester_protocol.NewSignagePointHarvester, MagicMock]:
+) -> tuple[HarvesterTestEnvironment, harvester_protocol.NewSignagePointHarvester2, MagicMock]:
     env = harvester_environment
     block = default_400_blocks[2]
     new_challenge = signage_point_from_block(block, blockchain_constants)
@@ -128,7 +128,7 @@ async def test_new_signage_point_harvester_pool_difficulty(
         sub_slot_iters=uint64(67108864),
     )
 
-    new_challenge = harvester_protocol.NewSignagePointHarvester(
+    new_challenge = harvester_protocol.NewSignagePointHarvester2(
         challenge_hash=new_challenge.challenge_hash,
         difficulty=new_challenge.difficulty,
         sub_slot_iters=new_challenge.sub_slot_iters,
diff --git a/chia/harvester/harvester_api.py b/chia/harvester/harvester_api.py
index 0ff578c74a..54fc6e1 100644
--- a/chia/harvester/harvester_api.py
+++ b/chia/harvester/harvester_api.py
@@ -53,7 +53,7 @@ class HarvesterAPI:
     def ready(self) -> bool:
         return True
 
-    def _plot_passes_filter(self, plot_info: PlotInfo, challenge: harvester_protocol.NewSignagePointHarvester) -> bool:
+    def _plot_passes_filter(self, plot_info: PlotInfo, challenge: harvester_protocol.NewSignagePointHarvester2) -> bool:
         filter_prefix_bits = calculate_prefix_bits(
             self.harvester.constants,
             challenge.peak_height,
```
* 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
Bumps [cryptography](https://github.com/pyca/cryptography) from 45.0.6 to 45.0.7.
- [Changelog](https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst)
- [Commits](pyca/cryptography@45.0.6...45.0.7)

---
updated-dependencies:
- dependency-name: cryptography
  dependency-version: 45.0.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [boto3](https://github.com/boto/boto3) from 1.40.18 to 1.40.22.
- [Release notes](https://github.com/boto/boto3/releases)
- [Commits](boto/boto3@1.40.18...1.40.22)

---
updated-dependencies:
- dependency-name: boto3
  dependency-version: 1.40.22
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [ruff](https://github.com/astral-sh/ruff) from 0.12.10 to 0.12.11.
- [Release notes](https://github.com/astral-sh/ruff/releases)
- [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md)
- [Commits](astral-sh/ruff@0.12.10...0.12.11)

---
updated-dependencies:
- dependency-name: ruff
  dependency-version: 0.12.11
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* remove unnecessary NPCResult in mempool_manager

* review comment

* Update chia/full_node/mempool_manager.py

Co-authored-by: Amine Khaldi <[email protected]>

---------

Co-authored-by: Amine Khaldi <[email protected]>
…retrying potential transactions (#20002)

Add a test to cover new peak returning added transactions as a result of retrying potential transactions.
…long_lived_datalayer_merkle_blob_from_main_ebf8105fc12c351888069ba399be6cf998f680e0
@altendky altendky requested review from a team as code owners September 5, 2025 19:07
@altendky altendky added checkpoint_merge Changed Required label for PR that categorizes merge commit message as "Changed" for changelog labels Sep 5, 2025
Copy link

Copy link

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
pypi/[email protected] has a License Policy Violation.

License: GPL-2.0 (pyinstaller_hooks_contrib-2025.8/LICENSE)

License: GPL-2.0 (pyinstaller_hooks_contrib-2025.8/LICENSE)

License: GPL-2.0 (pyinstaller_hooks_contrib-2025.8/PKG-INFO)

From: poetry.lockpypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/[email protected] has a License Policy Violation.

License: GPL-2.0-or-later (pyinstaller_hooks_contrib-2025.8.dist-info/licenses/LICENSE)

License: GPL-2.0 (pyinstaller_hooks_contrib-2025.8.dist-info/licenses/LICENSE)

License: GPL-2.0 (pyinstaller_hooks_contrib-2025.8.dist-info/METADATA)

From: ?pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: poetry.lockpypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/pywin32@311 has a License Policy Violation.

License: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) (adodbapi/setup.py)

From: ?pypi/pywin32@311

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pywin32@311. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/[email protected] has a License Policy Violation.

License: GPL-3.0-or-later (ruff-0.12.11/LICENSE)

From: poetry.lockpypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/[email protected] has a License Policy Violation.

License: GPL-3.0-or-later (ruff-0.12.11.dist-info/licenses/LICENSE)

From: ?pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/[email protected] has a License Policy Violation.

License: GPL-3.0-or-later (ruff-0.12.11.dist-info/licenses/LICENSE)

From: ?pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/[email protected] has a License Policy Violation.

License: GPL-3.0-or-later (ruff-0.12.11.dist-info/licenses/LICENSE)

From: ?pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/[email protected] has a License Policy Violation.

License: GPL-3.0-or-later (ruff-0.12.11.dist-info/licenses/LICENSE)

From: ?pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/[email protected] has a License Policy Violation.

License: GPL-3.0-or-later (ruff-0.12.11.dist-info/licenses/LICENSE)

From: ?pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
pypi/[email protected] has a License Policy Violation.

License: GPL-3.0-or-later (ruff-0.12.11.dist-info/licenses/LICENSE)

From: ?pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

See 12 more rows in the dashboard

View full report

@altendky altendky removed request for a team September 5, 2025 19:17
Copy link
Contributor

github-actions bot commented Sep 5, 2025

File Coverage Missing Lines
chia/_tests/blockchain/blockchain_test_utils.py 66.7% lines 122
chia/_tests/cmds/test_farm_cmd.py 86.2% lines 105-108
chia/_tests/core/full_node/test_full_node.py 61.5% lines 3168-3172
chia/_tests/core/server/test_rate_limits.py 99.6% lines 444
chia/_tests/util/setup_nodes.py 35.7% lines 354-355, 365-366, 368-369, 383, 394-395, 398-403, 405, 408, 410
chia/cmds/farm_funcs.py 66.7% lines 133-137
chia/cmds/plotnft_funcs.py 71.4% lines 166-167
chia/cmds/show_funcs.py 60.0% lines 51, 62
chia/cmds/solver.py 71.4% lines 12, 29, 31, 33
chia/cmds/solver_funcs.py 0.0% lines 1, 3-4, 6-8, 11, 16-21
chia/cmds/wallet_funcs.py 88.9% lines 295, 342, 997, 1281
chia/consensus/block_header_validation.py 97.4% lines 1044
chia/consensus/get_block_challenge.py 84.2% lines 97-99
chia/consensus/pos_quality.py 90.9% lines 45
chia/daemon/keychain_proxy.py 25.0% lines 388-390
chia/data_layer/data_layer_wallet.py 80.0% lines 595, 599
chia/full_node/coin_store.py 83.3% lines 174-175
chia/full_node/eligible_coin_spends.py 0.0% lines 281, 283-284
chia/full_node/full_node_api.py 57.1% lines 1137-1138, 1141
chia/full_node/full_node_rpc_api.py 80.0% lines 490, 1014
chia/full_node/mempool_manager.py 88.2% lines 275-276
chia/harvester/harvester.py 60.0% lines 197-198
chia/harvester/harvester_api.py 44.7% lines 81, 94-101, 106-109, 164-166, 171, 176-177, 180-182, 184-188, 191-192, 194-196, 206-207, 209-210, 212-214, 226-228, 386, 394, 410, 415, 420
chia/plotting/cache.py 85.7% lines 184, 193
chia/plotting/check_plots.py 0.0% lines 8, 136-137, 175-179, 184, 198, 202, 204, 206-207, 209-212, 217, 219-221, 223, 227-228, 231, 240-244, 246-249, 271, 273-276
chia/plotting/create_plots.py 50.0% lines 88
chia/plotting/manager.py 50.0% lines 343, 349
chia/plotting/prover.py 92.3% lines 128
chia/seeder/crawl_store.py 0.0% lines 198-201
chia/server/node_discovery.py 50.0% lines 232-233
chia/server/server.py 50.0% lines 269-270
chia/simulator/block_tools.py 90.9% lines 1523, 1533, 1537, 1557
chia/solver/solver.py 83.8% lines 39-40, 42, 70-75, 78, 81
chia/solver/solver_api.py 78.8% lines 40-41, 48-49, 57-59
chia/solver/solver_rpc_api.py 86.7% lines 26, 29
chia/solver/solver_rpc_client.py 83.3% lines 16
chia/solver/start_solver.py 69.5% lines 77-83, 85-88, 90, 94-95, 97, 100-101, 105
chia/timelord/timelord.py 33.3% lines 165-167, 171
chia/types/blockchain_format/proof_of_space.py 93.3% lines 30, 36
chia/util/db_wrapper.py 66.7% lines 134
chia/util/streamable.py 95.0% lines 447
chia/wallet/nft_wallet/nft_wallet.py 0.0% lines 553-555
chia/wallet/transaction_record.py 85.7% lines 110
chia/wallet/wallet_node.py 81.8% lines 1160, 1274, 1663-1664
chia/wallet/wallet_request_types.py 98.4% lines 307, 311, 1125
chia/wallet/wallet_rpc_api.py 92.1% lines 1334, 1719, 1977, 1988, 1990, 2065, 2080, 2086
chia/wallet/wallet_rpc_client.py 93.5% lines 195, 1133
Total Missing Coverage
2916 lines 256 lines 91%

@altendky altendky merged commit 0d7a723 into long_lived/datalayer_merkle_blob Sep 5, 2025
248 of 249 checks passed
@altendky altendky deleted the catchup/long_lived_datalayer_merkle_blob_from_main_ebf8105fc12c351888069ba399be6cf998f680e0 branch September 5, 2025 20:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Changed Required label for PR that categorizes merge commit message as "Changed" for changelog checkpoint_merge coverage-diff
Projects
None yet
Development

Successfully merging this pull request may close these issues.