Upstream node-0.20.0 changes #557
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* first patch didn't contain all of the change. --------- Co-authored-by: Justin Frevert <justinfrevert@gmail.com>
Signed-off-by: Giles Cope <gilescope@gmail.com>
rc4 - all aiken contracts
* revert to previous postgres connection config * whoops * change file
* fix: remove check for spends in gov utxo query The query will get the latest gov utxo at the time of block query The previous query checked if that utxo had been spent, including in blocks that are not yet stable (vulnerability) * chore: add pr link to change file * fix(e2e): wait for registration observation before minting in tests Fix race condition in cNIGHT E2E tests where tokens were minted before the Midnight node had observed and processed the registration. This caused the UtxoOwners storage to not be populated because handle_create couldn't find the mapping in Mappings storage. Added subscribe_to_cnight_observation_events calls after registrations to ensure the mapping is in storage before minting tokens. Tests fixed: - cnight_produces_dust - deregister_first_mapping - deregister_with_valid_cnight_utxo - produce_dust_from_tokens_owned_before_registration - register_twice_with_same_cardano_address - spend_cnight_producing_dust - stop_dust_producing_after_deregistration_and_rotation * Revert "fix(e2e): wait for registration observation before minting in tests" This reverts commit 9fd298d. The test failures are not caused by a race condition but by incorrect cnight_asset_name configuration. * fix: reset cnight_asset_name to empty in qanet config The cnight_asset_name was incorrectly set to "NIGHT" which is the mainnet value. For testnet/qanet, this should be empty ("") to match what the local-env midnight-setup produces. This was causing the local-env E2E tests to fail because the minted cNIGHT tokens had no asset name but the node was configured to look for tokens with asset name "NIGHT". * fix: doc * fix: docs 2 * fix: set token asset back to empty * fix: remove haskell contracts usage from local-env Refs: PM-21472 * chain spec regeneration * chore: rebuild chainspecs with empty cnight asset name Rebuilt chainspecs for node-dev-01, preprod, preview, and qanet networks. * remove qanet addresses --------- Co-authored-by: Oscar Bailey <79094698+ozgb@users.noreply.github.com> Co-authored-by: Mike Clay <mike.clay@shielded.io> Co-authored-by: NachoPal <ignacio.palacios.santos@gmail.com> Co-authored-by: Radosław Sporny <404@rspo.dev>
* fix: remove check for spends in gov utxo query (#529) * fix: remove check for spends in gov utxo query The query will get the latest gov utxo at the time of block query The previous query checked if that utxo had been spent, including in blocks that are not yet stable (vulnerability) * chore: add pr link to change file * fix(e2e): wait for registration observation before minting in tests Fix race condition in cNIGHT E2E tests where tokens were minted before the Midnight node had observed and processed the registration. This caused the UtxoOwners storage to not be populated because handle_create couldn't find the mapping in Mappings storage. Added subscribe_to_cnight_observation_events calls after registrations to ensure the mapping is in storage before minting tokens. Tests fixed: - cnight_produces_dust - deregister_first_mapping - deregister_with_valid_cnight_utxo - produce_dust_from_tokens_owned_before_registration - register_twice_with_same_cardano_address - spend_cnight_producing_dust - stop_dust_producing_after_deregistration_and_rotation * Revert "fix(e2e): wait for registration observation before minting in tests" This reverts commit 9fd298d. The test failures are not caused by a race condition but by incorrect cnight_asset_name configuration. * fix: reset cnight_asset_name to empty in qanet config The cnight_asset_name was incorrectly set to "NIGHT" which is the mainnet value. For testnet/qanet, this should be empty ("") to match what the local-env midnight-setup produces. This was causing the local-env E2E tests to fail because the minted cNIGHT tokens had no asset name but the node was configured to look for tokens with asset name "NIGHT". * fix: doc * fix: docs 2 * fix: set token asset back to empty * fix: remove haskell contracts usage from local-env Refs: PM-21472 * chain spec regeneration * chore: rebuild chainspecs with empty cnight asset name Rebuilt chainspecs for node-dev-01, preprod, preview, and qanet networks. * remove qanet addresses --------- Co-authored-by: Mike Clay <mike.clay@shielded.io> Co-authored-by: NachoPal <ignacio.palacios.santos@gmail.com> Co-authored-by: Radosław Sporny <404@rspo.dev> Co-authored-by: Justin Frevert <justinfrevert@gmail.com> * docs: governance (#475) * Tweak architecture diagram and security information (#442) Updated architecture diagram to be clearer. Security notes in README now link to polkadot validator setup notes as there are some excellent points on securing nodes. Co-authored-by: justinfrevert <81839854+justinfrevert@users.noreply.github.com> * chore(deps): bump taiki-e/install-action from 2.66.2 to 2.66.7 (#496) Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.66.2 to 2.66.7. - [Release notes](https://github.com/taiki-e/install-action/releases) - [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md) - [Commits](taiki-e/install-action@03ef6f5...542ceba) --- updated-dependencies: - dependency-name: taiki-e/install-action dependency-version: 2.66.7 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * feat: more determinism in tests (#512) * chore(deps): bump Compact.js to 2.4.0-rc.10 (#514) * chore(deps): bump Compact.js to 2.4.0-rc.10 * docs: tweak advice on change files * chore: add pr link to change file * feat: Fix support issue url (#329) * feat: Fix support issue url * chore: set PR * feat: highlight if main is broken. (#231) * feat: highlight if main is broken. * chore(deps): replace dependency @tsconfig/node22 with @tsconfig/node24 (#427) * feat: add block limits to update-ledger-parameters (#531) * feat: add block limits to update-ledger-parameters Included: re-use the root-call implementation for running governance process * docs: add change file --------- Co-authored-by: Squirrel <giles.cope@shielded.io> * chore(deps): bump the npm_and_yarn group across 2 directories with 1 update (#509) Bumps the npm_and_yarn group with 1 update in the /ui directory: [tar](https://github.com/isaacs/node-tar). Bumps the npm_and_yarn group with 1 update in the /ui/tests directory: [tar](https://github.com/isaacs/node-tar). Updates `tar` from 7.5.3 to 7.5.6 - [Release notes](https://github.com/isaacs/node-tar/releases) - [Changelog](https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md) - [Commits](isaacs/node-tar@v7.5.3...v7.5.6) Updates `tar` from 7.5.3 to 7.5.6 - [Release notes](https://github.com/isaacs/node-tar/releases) - [Changelog](https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md) - [Commits](isaacs/node-tar@v7.5.3...v7.5.6) --- updated-dependencies: - dependency-name: tar dependency-version: 7.5.6 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: tar dependency-version: 7.5.6 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump ledger to ledger-2.0.0-rc.2 (#540) * chore(deps): bump ledger to ledger-2.0.0-rc.2 * chore: add pr link to change file * fix: panic when using update-ledger-parameters --parameters (#541) * fix: panic when using update-ledger-parameters --parameters * chore: add change file --------- Co-authored-by: Squirrel <giles.cope@shielded.io> * feat: big speedup for cnight queries (1000x for mainnet data) (#525) * fix: speed-up query exec 100x by indexing separately Queries used to use tuple comparisons like: ```sql AND (block.block_no, tx.block_index) >= ($4, $5) AND (block.block_no, tx.block_index) < ($6, $7) ``` PostgreSQL often can't use individual column indexes efficiently for row comparisons. Updated to: ```sql AND (block.block_no > $4 OR (block.block_no = $4 AND tx.block_index >= $5)) AND (block.block_no < $6 OR (block.block_no = $6 AND tx.block_index < $7)) ``` * fix: tweak ordering of select in queries for 40x speed-up * chore: update change file Signed-off-by: Giles Cope <gilescope@gmail.com> --------- Signed-off-by: Giles Cope <gilescope@gmail.com> Co-authored-by: Giles Cope <gilescope@gmail.com> Co-authored-by: Squirrel <giles.cope@shielded.io> --------- Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Giles Cope <gilescope@gmail.com> Co-authored-by: Oscar Bailey <79094698+ozgb@users.noreply.github.com> Co-authored-by: Mike Clay <mike.clay@shielded.io> Co-authored-by: NachoPal <ignacio.palacios.santos@gmail.com> Co-authored-by: Radosław Sporny <404@rspo.dev> Co-authored-by: Justin Frevert <justinfrevert@gmail.com> Co-authored-by: justinfrevert <81839854+justinfrevert@users.noreply.github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Signed-off-by: Giles Cope <gilescope@gmail.com>
Signed-off-by: Giles Cope <gilescope@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automated Pull Request
Note: Workflow runs will not be triggered by this automated PR
To trigger them, manually open and close the pull request.
This is a "feature" of GitHub Actions, which does not trigger workflows on automated PRs.
Updated
mainbranch with changes from the releaseReplaced 'changes/' directory with an empty template
Archived current changes to '.changes_archive/node-0.20.0'