Skip to content
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

Enforce the block size limit #2195

Merged
merged 53 commits into from
Sep 27, 2024
Merged

Conversation

rafal-ch
Copy link
Contributor

@rafal-ch rafal-ch commented Sep 13, 2024

Closes #2133

Linked Issues/PRs

Built on top of: #2188

Description

This PR adds the handling and enforcement of then new consensus parameter added here.

Changes summary:

  • TransactionsSource and transaction_selector use the new block_transaction_size_limit parameter.
  • ExecutionData contains used_size in addition to used_gas
  • Introduces integration tests covering the expected behavior
  • E2E tests affected by the new limit are updated

Checklist

  • Breaking changes are clearly marked as such in the PR description and changelog
  • New behavior is reflected in tests

Before requesting review

  • I have reviewed the code myself

Base automatically changed from 2133_block_size_consensus_parameter to feature/wasm-interface-breaking-changes September 17, 2024 13:58
Base automatically changed from feature/wasm-interface-breaking-changes to master September 17, 2024 14:50
Cargo.lock Outdated
@@ -1252,9 +1252,9 @@ checksum = "1fd0f2584146f6f2ef48085050886acf353beff7305ebd1ae69500e27c67f64b"

[[package]]
name = "bytes"
version = "1.7.1"
version = "1.7.2"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Usually, we run cargo update in a separate PR or during release. Could you revert this changes(unless you need them), please?=)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes to Cargo.lock reverted in 9bdea6d

Comment on lines 31 to 35

let maybe_new_used_block_gas_space =
used_block_gas_space.checked_add(tx_block_gas_space);
let maybe_new_used_block_size_space =
used_block_size_space.checked_add(tx_block_size_space);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can use saturating_add isntead

Copy link
Contributor Author

@rafal-ch rafal-ch Sep 21, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right. Updated in 36ab508

assert!(status.is_ok())
}

let _ = tokio::time::sleep(Duration::from_millis(10)).await;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need to wait? You can use the srv.shared_state.txpool.insert function if you want to be sure that the transaction is inserted. But client.submit(tx).await should work as well

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a leftover from my initial test attempts. Removed in 15a2cf7.

cc: @MitchTurner - you may want to have a look at this.

assert!(status.is_ok())
}

let _ = tokio::time::sleep(Duration::from_millis(10)).await;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The same here, do we need to wait if you use manual block production?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

xgreenx
xgreenx previously approved these changes Sep 24, 2024
@rafal-ch rafal-ch requested a review from a team September 25, 2024 09:55
acerone85
acerone85 previously approved these changes Sep 25, 2024
Copy link
Contributor

@acerone85 acerone85 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had a look at the code and the tests.

It looks like the implementation for OnceTransactionsSource is still ignoring the block_txs_size parameter (

impl TransactionsSource for OnceTransactionsSource {
), but this could be done as a follow up.

LGTM.

@rafal-ch
Copy link
Contributor Author

It looks like the implementation for OnceTransactionsSource is still ignoring the block_txs_size parameter

Summoning @xgreenx for a comment.

According to my current understanding, we don't necessarily need the support for block_txs_size in the OnceTransactionsSource.

@rafal-ch rafal-ch dismissed stale reviews from acerone85 and xgreenx via 70e9178 September 25, 2024 13:56
@xgreenx
Copy link
Collaborator

xgreenx commented Sep 25, 2024

According to my current understanding, we don't necessarily need the support for block_txs_size in the OnceTransactionsSource.

Yes, OnceTransactionsSource shouldn't event exist in production, it is just a hack for dry run=)

@@ -194,7 +194,7 @@ impl TransactionsSource for OnceTransactionsSource {
&self,
_: u64,
transactions_limit: u16,
_: u32,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I missed that, but the block size should be u32.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated in e748837

@@ -84,7 +84,7 @@ mod host {
pub(crate) fn peek_next_txs_size(
gas_limit: u64,
tx_count_limit: u32,
size_limit: u32,
block_transaction_size_limit: u64,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is a breaking change

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated in e748837

@xgreenx xgreenx merged commit 4a55b7d into master Sep 27, 2024
36 checks passed
@xgreenx xgreenx deleted the 2133_enforce_the_block_size_limit branch September 27, 2024 08:43
@xgreenx xgreenx mentioned this pull request Oct 5, 2024
xgreenx added a commit that referenced this pull request Oct 5, 2024
## Version v0.37.0

### Added
- [1609](#1609): Add DA
compression support. Compressed blocks are stored in the offchain
database when blocks are produced, and can be fetched using the GraphQL
API.
- [2290](#2290): Added a new
CLI argument `--graphql-max-directives`. The default value is `10`.
- [2195](#2195): Added
enforcement of the limit on the size of the L2 transactions per block
according to the `block_transaction_size_limit` parameter.
- [2131](#2131): Add flow in
TxPool in order to ask to newly connected peers to share their
transaction pool
- [2182](#2151): Limit number
of transactions that can be fetched via TxSource::next
- [2189](#2151): Select next
DA height to never include more than u16::MAX -1 transactions from L1.
- [2162](#2162): Pool
structure with dependencies, etc.. for the next transaction pool module.
Also adds insertion/verification process in PoolV2 and tests refactoring
- [2265](#2265): Integrate
Block Committer API for DA Block Costs.
- [2280](#2280): Allow comma
separated relayer addresses in cli
- [2299](#2299): Support blobs
in the predicates.
- [2300](#2300): Added new
function to `fuel-core-client` for checking whether a blob exists.

### Changed

#### Breaking
- [2299](#2299): Anyone who
wants to participate in the transaction broadcasting via p2p must
upgrade to support new predicates on the TxPool level.
- [2299](#2299): Upgraded
`fuel-vm` to `0.58.0`. More information in the
[release](https://github.com/FuelLabs/fuel-vm/releases/tag/v0.58.0).
- [2276](#2276): Changed how
complexity for blocks is calculated. The default complexity now is
80_000. All queries that somehow touch the block header now are more
expensive.
- [2290](#2290): Added a new
GraphQL limit on number of `directives`. The default value is `10`.
- [2206](#2206): Use timestamp
of last block when dry running transactions.
- [2153](#2153): Updated
default gas costs for the local testnet configuration to match
`fuel-core 0.35.0`.

## What's Changed
* fix: use core-test.fuellabs.net for dnsaddr resolution by @rymnc in
#2214
* Removed state transition bytecode from the local testnet by @xgreenx
in #2215
* Send whole transaction pool upon subscription to gossip by @AurelienFT
in #2131
* Update default gas costs based on 0.35.0 benchmarks by @xgreenx in
#2153
* feat: Use timestamp of last block when dry running transactions by
@netrome in #2206
* fix(dnsaddr_resolution): use fqdn separator to prevent suffixing by
dns resolvers by @rymnc in
#2222
* TransactionSource: specify maximum number of transactions to be
fetched by @acerone85 in #2182
* Implement worst case scenario for price algorithm v1 by @rafal-ch in
#2219
* chore(gas_price_service): define port for L2 data by @rymnc in
#2224
* Block producer selects da height to never exceed u64::MAX - 1
transactions from L1 by @acerone85 in
#2189
* Weekly `cargo update` by @github-actions in
#2236
* Use fees to calculate DA reward and avoid issues with Gwei/Wei
conversions by @MitchTurner in
#2229
* Protect against passing `i128::MIN` to `abs()` which causes overflow
by @rafal-ch in #2241
* Acquire `da_finalization_period` from the command line by @rafal-ch in
#2240
* Executor: test Tx_count limit with incorrect tx source by @acerone85
in #2242
* Minor updates to docs + a few typos fixed by @rafal-ch in
#2250
* chore(gas_price_service): move algorithm_updater to
fuel-core-gas-price-service by @rymnc in
#2246
* Use single heavy input in the `transaction_throughput.rs` benchmarks
by @xgreenx in #2205
* Enforce the block size limit by @rafal-ch in
#2195
* feat: build ARM and AMD in parallel by @mchristopher in
#2130
* Weekly `cargo update` by @github-actions in
#2268
* chore(gas_price_service): split into v0 and v1 and squash
FuelGasPriceUpdater type into GasPriceService by @rymnc in
#2256
* feat(gas_price_service): update block committer da source with
established contract by @rymnc in
#2265
* Use bytes from `unrecorded_blocks` rather from the block from DA by
@MitchTurner in #2252
* TxPool v2 General architecture by @AurelienFT in
#2162
* Add value delimiter and tests args by @AurelienFT in
#2280
* fix(da_block_costs): remove Arc<Mutex<>> on shared_state and expose
channel by @rymnc in #2278
* fix(combined_database): syncing auxiliary databases on startup with
custom behaviour by @rymnc in
#2272
* fix: Manually encode Authorization header for eventsource_client by
@Br1ght0ne in #2284
* Address `async-graphql` vulnerability by @MitchTurner in
#2290
* Update the WASM compatibility tests for `0.36` release by @rafal-ch in
#2271
* DA compression by @Dentosal in
#1609
* Use different port for every version compatibility test by @rafal-ch
in #2301
* Fix block query complexity by @xgreenx in
#2297
* Support blobs in predicates by @Voxelot in
#2299


**Full Changelog**:
v0.36.0...v0.37.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support block size limit
3 participants