Skip to content

Conversation

jonastheis
Copy link

@jonastheis jonastheis commented Jun 5, 2025

1. Purpose or design rationale of this PR

This PR fixes an issue where the blob client API delivers an unexpected response that is not checked for length before accessed.

WARN [06-05|06:46:37.665] BlobClients: failed to get blob by versioned hash from BlobClient err="beacon node request failed, status: 404 Not Found, body: {\"code\":404,\"message\":\"NOT_FOUND: no blobs stored for block 0xb2946d447a0dc81b6bcfe3119df4e05087126770b886092a2792992890f880b0\",\"stacktraces\":[]}" blob client pos in BlobClients=1
panic: runtime error: slice bounds out of range [2:0]
goroutine 88 [running]:
github.com/scroll-tech/go-ethereum/rollup/da_syncer/blob_client.(*BlobScanClient).GetBlobByVersionedHashAndBlockTime(0xc02bb31bc0, {0x1cea5a0, 0xc01a40a320}, {0x1, 0xb9, 0x1f, 0xc, 0xf6, 0x95, 0xa0, ...}, ...)
	github.com/scroll-tech/go-ethereum/rollup/da_syncer/blob_client/blob_scan_client.go:67 +0xde5
github.com/scroll-tech/go-ethereum/rollup/da_syncer/blob_client.(*BlobClients).GetBlobByVersionedHashAndBlockTime(0xc027f489a0, {0x1cea5a0, 0xc01a40a320}, {0x1, 0xb9, 0x1f, 0xc, 0xf6, 0x95, 0xa0, ...}, ...)
	github.com/scroll-tech/go-ethereum/rollup/da_syncer/blob_client/blob_client.go:41 +0x182
github.com/scroll-tech/go-ethereum/rollup/da_syncer/da.NewCommitBatchDAV1({0x1cea5a0, 0xc01a40a320}, {0x1cf6f78, 0xc000028558}, {0x1ce01e0?, 0xc027f489a0}, {0x1cf7df0, 0x29d3500}, 0xc02c2925b0, {0xc0303600a4, ...}, ...)
	github.com/scroll-tech/go-ethereum/rollup/da_syncer/da/commitV1.go:45 +0x1e9

2. PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

  • build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
  • ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
  • docs: Documentation-only changes
  • feat: A new feature
  • fix: A bug fix
  • perf: A code change that improves performance
  • refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • test: Adding missing tests or correcting existing tests

3. Deployment tag versioning

Has the version in params/version.go been updated?

  • This PR doesn't involve a new deployment, git tag, docker image tag, and it doesn't affect traces
  • Yes

4. Breaking change label

Does this PR have the breaking-change label?

  • This PR is not a breaking change
  • Yes

Summary by CodeRabbit

  • Bug Fixes
    • Improved validation for blob data responses to prevent errors when handling invalid or empty data.
  • Chores
    • Updated the patch version number.

Copy link

coderabbitai bot commented Jun 5, 2025

Walkthrough

The patch updates the patch version constant in the versioning parameters and introduces validation checks in two blob client modules to ensure blob data fields have a minimum length before decoding. These checks prevent errors when handling insufficient or invalid blob data in JSON responses.

Changes

File(s) Change Summary
params/version.go Incremented VersionPatch constant from 51 to 52.
rollup/da_syncer/blob_client/blob_scan_client.go, rollup/da_syncer/blob_client/block_native_client.go Added validation to check blob data length before decoding; returns error if data is too short.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant BlobClient
    participant JSONResponse

    Client->>BlobClient: Request blob data
    BlobClient->>JSONResponse: Decode JSON response
    JSONResponse-->>BlobClient: Return BlobResp struct
    BlobClient->>BlobClient: Check if Data length >= 2
    alt Data too short
        BlobClient-->>Client: Return error (data too short)
    else Data valid
        BlobClient->>BlobClient: Decode hex string
        BlobClient-->>Client: Return decoded data
    end
Loading

Suggested reviewers

  • Thegaram

Poem

A patch hops in, from fifty-one to two,
With checks on blobs—no short data gets through!
If your hex is too tiny, an error you'll see,
For robust code is as sweet as can be.
🐇✨ Version up, and bugs adieu!


📜 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 cdd77c1 and 6f24e3a.

📒 Files selected for processing (3)
  • params/version.go (1 hunks)
  • rollup/da_syncer/blob_client/blob_scan_client.go (1 hunks)
  • rollup/da_syncer/blob_client/block_native_client.go (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
rollup/da_syncer/blob_client/block_native_client.go (1)
crypto/kzg4844/kzg4844.go (1)
  • Blob (31-31)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyze (go)
🔇 Additional comments (3)
params/version.go (1)

27-27: LGTM! Appropriate version bump for bug fix.

The patch version increment aligns with the bug fix addressing nil pointer panics in blob client modules. This follows proper semantic versioning practices.

rollup/da_syncer/blob_client/block_native_client.go (1)

63-66: Excellent fix for the nil pointer panic issue!

This validation check effectively prevents the slice bounds out of range panic that was occurring when result.Blob.Data[2:] was accessed on strings shorter than 2 characters. The error message is informative and includes debugging context.

rollup/da_syncer/blob_client/blob_scan_client.go (1)

68-71: Consistent and effective validation implementation!

This validation check mirrors the fix in block_native_client.go, ensuring consistent handling of short blob data across both client implementations. The check prevents slice bounds panic when accessing result.Data[2:] and provides clear error messaging.

✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Member

@colinlyguo colinlyguo left a comment

Choose a reason for hiding this comment

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

lgtm.

@Thegaram Thegaram merged commit 7fbc35d into develop Jun 5, 2025
4 checks passed
@Thegaram Thegaram deleted the fix/blob-client-nil-pointr branch June 5, 2025 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants