forked from solana-labs/solana
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate native program #1
Closed
Closed
Conversation
This file contains 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
…olana-labs#33742) Currently each outgoing repair request will attempt to establish a connection if one does not already exist. This is very wasteful and consumes many tokio tasks if the remote node is down or unresponsive. The commit decouples routing packets from establishing connections by adding a buffering channel for each remote address. Outgoing packets are always sent down this channel to be processed once the connection is established. If connecting attempt fails, all packets already pushed to the channel are dropped at once, reducing the number of attempts to make a connection if the remote node is down or unresponsive.
…bs#33599) Currently each outgoing shred will attempt to establish a connection if one does not already exist. This is very wasteful and consumes many tokio tasks if the remote node is down or unresponsive. The commit decouples routing packets from establishing connections by adding a buffering channel for each remote address. Outgoing packets are always sent down this channel to be processed once the connection is established. If connecting attempt fails, all packets already pushed to the channel are dropped at once, reducing the number of attempts to make a connection if the remote node is down or unresponsive.
…labs#33513) * Split compute budget instruction processing from ComputeBudget struct itself, allow compute_budget_instructions be processed elsewhere without having to instantiate ComputeBudget * updated tests
* add ancient append vec test * Update accounts-db/src/ancient_append_vecs.rs Co-authored-by: Brooks <[email protected]> * add some comments --------- Co-authored-by: Brooks <[email protected]>
…33756) A previous change removed logic that populated the TransactionStatusIndex entries at each of the legacy primary index keys (0 and 1). While these entries will not be read or written in the future, these entries are necessary for backwards compatibility. Namely, branches <= v1.17 expect these entries to be present and .unwrap()'s could fail if they are not. So, add the initialization of these entries back into Blockstore logic. We can remove initialization of these entries once our stable and beta branches are both versions that do not expect these entries to be present (should be v1.18).
Co-authored-by: Richard Patel <[email protected]>
Co-authored-by: Richard Patel <[email protected]>
solana-labs#33784) Revert "Split compute budget instructions process from struct itself (solana-labs#33513)" This reverts commit c73bebe. This was found to be a consensus breaking change.
* Set a global fork graph in program cache * fix deadlock * review feedback
…olana-labs#33675) * Add check for CHANGELOG.md change when changelog label applied to PR * Update changelog
* add many_refs_this_is_newest_alive * fix pathological case, add comments * add log * update comments * add log when we fail to pack * use with_capacity * fix log comment * clippy
…labs#33709) fix(dockerfile): make sure to use the bullseye image for building Solana's release image is based on bullseye, make sure we compile Solana with the same environment
The commit implements lazy eviction for repair QUIC connections. The cache is allowed to grow to 2 x capacity at which point at least half of the entries with lowest stake are evicted, resulting in an amortized O(1) performance.
* Bumps solana_rbpf to v0.8.0 * Adjustments: Replaces declare_syscall!() with declare_builtin_function!(). Removes Config::encrypt_runtime_environment. Simplifies error propagation.
…#33700) * limit max seed length for elgamal keypairs * limit max seed length for authenticated encryption keys * Apply suggestions from code review Co-authored-by: Jon Cinque <[email protected]> * rename `SeedLengthTooLarge` to `SeedLengthTooLong` --------- Co-authored-by: Jon Cinque <[email protected]>
The commit implements lazy eviction for turbine QUIC connections. The cache is allowed to grow to 2 x capacity at which point at least half of the entries with lowest stake are evicted, resulting in an amortized O(1) performance.
…a-labs#34103) feature gate zk-token-proof transfer with fee
* ci: run bench test in docker * ci: fix bench test triggering rule
…ctivations()` (solana-labs#34124) * Moves modification of feature accounts from Bank::compute_active_feature_set() into Bank::apply_feature_activations(). * Renames allow_new_activations and newly_activated to include_pending and pending. * Fix test_compute_active_feature_set.
* build(deps): bump test-case from 3.2.1 to 3.3.0 Bumps [test-case](https://github.com/frondeus/test-case) from 3.2.1 to 3.3.0. - [Release notes](https://github.com/frondeus/test-case/releases) - [Changelog](https://github.com/frondeus/test-case/blob/master/CHANGELOG.md) - [Commits](frondeus/test-case@v3.2.1...v3.3.0) --- updated-dependencies: - dependency-name: test-case dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * [auto-commit] Update all Cargo lock files --------- Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: dependabot-buildkite <[email protected]>
* build(deps): bump rustls from 0.21.8 to 0.21.9 Bumps [rustls](https://github.com/rustls/rustls) from 0.21.8 to 0.21.9. - [Release notes](https://github.com/rustls/rustls/releases) - [Commits](rustls/rustls@v/0.21.8...v/0.21.9) --- updated-dependencies: - dependency-name: rustls dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> * [auto-commit] Update all Cargo lock files --------- Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: dependabot-buildkite <[email protected]>
fix tests Co-authored-by: HaoranYi <[email protected]>
The function matches the access type and calls a different RocksDB function depending on whether we have primary or secondary access. But, lots of the code is the same for these two paths so de-duplicate the repeated sections.
…bs#34066) * gossip: process duplicate proofs for merkle root conflicts * pr comments + abi
…s#34106) #### Problem TieredAccountMeta currently uses `u32` for owner_offset, while we already have a dedicate type for that --- OwnerOffset. #### Summary of Changes This PR makes TieredAccountMeta use OwnerOffset for its owner_offset field. #### Test Plan Existing unit-tests.
…olana-labs#34132) * CI: automatically add a warning comment to PRs with backport labels * Update .mergify.yml Co-authored-by: Trent Nelson <[email protected]> * Update .mergify.yml Co-authored-by: Trent Nelson <[email protected]> --------- Co-authored-by: Trent Nelson <[email protected]>
…lana-labs#34128) * HvA9J * Rename file and change orders of definitions. * Use .from() on u16 to usize which shouldn't fail. * Update ABI congest.
#### Problem In TieredStorage, we want to make AccountOffset and IndexOffset u32 instead of usize just like OwnerOffset. However, we need to first change what we persist in the storage. Currently, IndexBlock persists offsets as u64 instead of u32. #### Summary of Changes This PR makes IndexBlock persist u32 offsets. #### Test Plan Existing test cases.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
Summary of Changes
Fixes #