feat: enable pebble

[faddat]

• support pebble
• bump pyroscope

Overview

Checklist

• New and updated code has appropriate documentation
• New and updated code has new and/or updated testing
• Required CI checks are passing
• Visual proof for any user facing features like CLI or documentation updates
• Linked issues closed with keywords

[coderabbitai]

Important

Auto Review Skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository.

To trigger a single review, invoke the @coderabbitai review command.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

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>.
  • Generate unit-tests for this file.
• 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 generate unit tests for this file.
  • @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 generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[faddat]

@coderabbitai review

@coderabbitai & reviewers - to finish off this PR, there's a second PR on the celestia-core repository, here:

• feat: use pebble celestia-core#1237

The celestia-core PR allows celestia-core to use go 1.22 and so it needed to update some pyroscope dependencies.

There's also a PR to cometbft-db here:

• remove Dockerfile, use only pure go dabase backends cometbft/cometbft-db#135

Once the cometbft-db PR is merged, I'll be able to use it without the replace statement in the celestia-core PR, and in this PR, too.

[coderabbitai]

@faddat, I understand the dependencies between the PRs across the celestia-app, celestia-core, and cometbft-db repositories. While I can't directly check the merge status of external PRs or their specific changes, I can review the changes within the celestia-app PR that are related to the Go 1.22 update and pyroscope dependencies adjustments.

Please ensure that any necessary updates or dependency changes in the celestia-app PR are aligned with the updates in the celestia-core and cometbft-db PRs. If there are specific files or configurations within the celestia-app PR that you would like me to focus on, especially those affected by the updates in the other repositories, please let me know.

Action performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[evan-forbes]

thanks for this @faddat

[evan-forbes]

ideally we would do this in a separate PR, is this required for the other changes here? if so, then we will likely need to create a different PR that also updates all the CI to use the latest go version

[evan-forbes]

I'm assuming that this is just blocked by the same PR in core, but we might want to mention that in the draft comment

[evan-forbes]

does this what are the other consequences of this? could this be upstreamed or is this also blocked by an upstream PR?

[rootulp]

Closing b/c this doesn't appear to be actively worked on. Please re-open if I misinterpreted.