Skip to content

fix: Increase claimed storage size for Relayers to 32Gi#7180

Merged
ameten merged 1 commit intomainfrom
ameten/relayer-storage-size
Oct 10, 2025
Merged

fix: Increase claimed storage size for Relayers to 32Gi#7180
ameten merged 1 commit intomainfrom
ameten/relayer-storage-size

Conversation

@ameten
Copy link
Copy Markdown
Contributor

@ameten ameten commented Oct 10, 2025

Description

Increase claimed storage size for Relayers to 32Gi

Related issues

Yes

Testing

Testnet

Summary by CodeRabbit

  • Chores
    • Increased relayer storage allocation from 16Gi to 32Gi to provide more capacity for data and logs.
    • Aims to improve reliability during high-load periods and reduce risk of storage-related interruptions.
    • No functional changes to user-facing behavior; deployments will use the updated default storage size.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Oct 10, 2025

⚠️ No Changeset found

Latest commit: 026e20a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Oct 10, 2025

📝 Walkthrough

Walkthrough

In the Helm values for hyperlane-agent, the relayer storage size value changed from 16Gi to 32Gi. No other values were modified.

Changes

Cohort / File(s) Summary
Helm values tweak
rust/main/helm/hyperlane-agent/values.yaml
Bumped hyperlane.relayer.storage.size from 16Gi to 32Gi; no other changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A wee bump in the bog of bytes today,
From 16Gi to 32Gi, we pave the way.
No dragons stirred, no swamps rearranged,
Just room for logs where paths are ranged.
Carry on, lass—storage’s got more clay.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The PR description includes the main change, related issue reference, and testing details but omits the required Drive-by changes and Backward compatibility section headings prescribed by the template, and the standalone “Yes” is uncontextualized. Without those sections, it’s unclear whether any minor changes were made or if infrastructure implications have been considered. This absence prevents full compliance with the repository’s pull request standards. Please add a ### Drive-by changes section (or indicate none) and a ### Backward compatibility section with Yes or No, moving the “Yes” under the appropriate heading to follow the repository’s template.
✅ Passed checks (2 passed)
Check name Status Explanation
Title Check ✅ Passed The title clearly and concisely addresses the primary change by stating the relayer storage size increase to 32Gi and uses a conventional prefix to indicate a bug fix. It directly matches the change in the Helm values file without extraneous detail. It’s specific enough for a teammate to understand the main update at a glance and follows best practices.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch ameten/relayer-storage-size

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f79517d and 026e20a.

📒 Files selected for processing (1)
  • rust/main/helm/hyperlane-agent/values.yaml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (11)
  • GitHub Check: infra-test
  • GitHub Check: build-and-push-to-gcr
  • GitHub Check: e2e-matrix (cosmosnative)
  • GitHub Check: e2e-matrix (evm)
  • GitHub Check: e2e-matrix (radix)
  • GitHub Check: e2e-matrix (sealevel)
  • GitHub Check: e2e-matrix (starknet)
  • GitHub Check: e2e-matrix (cosmwasm)
  • GitHub Check: lander-coverage
  • GitHub Check: lint-rs
  • GitHub Check: test-rs

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@ameten ameten added this pull request to the merge queue Oct 10, 2025
Merged via the queue into main with commit 132bf04 Oct 10, 2025
40 checks passed
@ameten ameten deleted the ameten/relayer-storage-size branch October 10, 2025 14:32
@github-project-automation github-project-automation Bot moved this from In Review to Done in Hyperlane Tasks Oct 10, 2025
@codecov
Copy link
Copy Markdown

codecov Bot commented Oct 10, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (f79517d) to head (026e20a).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@          Coverage Diff          @@
##            main   #7180   +/-   ##
=====================================
  Coverage   0.00%       0           
=====================================
  Files          1       0    -1     
  Lines         14       0   -14     
=====================================
+ Misses        14       0   -14     
Components Coverage Δ
core ∅ <ø> (∅)
hooks ∅ <ø> (∅)
isms ∅ <ø> (∅)
token ∅ <ø> (∅)
middlewares ∅ <ø> (∅)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

This was referenced Oct 13, 2025
This was referenced Nov 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants