Skip to content

feat: allow configuration of max_body_size_limit in upload relay#2809

Closed
wbbradley wants to merge 1 commit into
mainfrom
variable-upload-relay-max-size
Closed

feat: allow configuration of max_body_size_limit in upload relay#2809
wbbradley wants to merge 1 commit into
mainfrom
variable-upload-relay-max-size

Conversation

@wbbradley

Copy link
Copy Markdown
Contributor

Description

Allow configuration of max_body_size_limit in upload relay.

Test plan

Manual testing. CI Pipeline.

Comment thread crates/walrus-simtest/tests/simtest_failure.rs
@wbbradley wbbradley force-pushed the variable-upload-relay-max-size branch from 1bf0cee to 3e7c06a Compare December 29, 2025 21:02
@github-actions

Copy link
Copy Markdown
Contributor

Warning: This PR modifies one of the example config files. Please consider the
following:

  • Make sure the changes are backwards compatible with the current configuration.
  • Make sure any added parameters follow the conventions of the existing parameters; in
    particular, durations should take seconds or milliseconds using the naming convention
    _secs or _millis, respectively.
  • If there are added optional parameter sections, it should be possible to specify them
    partially. A useful pattern there is to implement Default for the struct and derive
    #[serde(default)] on it, see BlobRecoveryConfig as an example.
  • You may need to update the documentation to reflect the changes.

@wbbradley wbbradley changed the title feat: allow configuration of max_body_size_limit feat: allow configuration of max_body_size_limit in upload relay Dec 29, 2025
@wbbradley wbbradley force-pushed the variable-upload-relay-max-size branch from 3e7c06a to d88e09a Compare December 30, 2025 23:12

@halfprice halfprice left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

LGTM! It'll be great if we can test that this works as expected, since a simple test case that stores limit size +1 would do it.

Comment on lines +2651 to +2657
match basic_store_and_read(
&cluster_client,
1,
BLOB_SIZE,
Some(upload_relay_client),
|| Ok(()),
)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

suggestion: looks like you can add a simple test case where the test tries to store BLOB_SIZE +1, and expect to get rejected.

tip_config: TipConfig::NoTip,
tx_freshness_threshold: Duration::from_mins(5),
tx_max_future_threshold: Duration::from_secs(10),
max_body_size_limit: BLOB_SIZE,

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

question: this could be set to anything that is larger than BLOB_SIZE, is that correct? Any particular reason to use BLOB_SIZE instead of the default_max_body_size_limit() here?

@wbbradley wbbradley force-pushed the variable-upload-relay-max-size branch from d88e09a to d48ac69 Compare January 7, 2026 04:40
@github-actions

Copy link
Copy Markdown
Contributor

This PR is stale because it has been open 14 days with no activity. It will be closed in 7 days unless you remove the stale label, add the do-not-close label, or comment on it.

@github-actions github-actions Bot added the stale label Jan 26, 2026
@github-actions

github-actions Bot commented Feb 2, 2026

Copy link
Copy Markdown
Contributor

This PR was closed because it has not seen any activity since being marked as stale.

@github-actions github-actions Bot closed this Feb 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants