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

fix: update nitro #1380

Merged
merged 1 commit into from
Jan 29, 2024
Merged

fix: update nitro #1380

merged 1 commit into from
Jan 29, 2024

Conversation

jcstein
Copy link
Member

@jcstein jcstein commented Jan 24, 2024

Overview

i hit an error building, so need to look into again, unless it was due to network issues

https://app.warp.dev/block/7NE249p1K1OoCcrPNrlPde

Update: yep, was due to network issues. runs as expected!

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

Summary by CodeRabbit

  • Documentation
    • Updated the tutorial to work with version v2.2.2-no-blobstream.

@jcstein jcstein self-assigned this Jan 24, 2024
Copy link
Contributor

coderabbitai bot commented Jan 24, 2024

Warning

Rate Limit Exceeded

@jcstein has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 28 minutes and 57 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits Files that changed from the base of the PR and between e0955e6 and 72975b9.

Walkthrough

The update to the Arbitrum deployment documentation includes a critical change to the Git checkout command. This modification ensures that developers pull the correct version of the code, tags/v2.2.2-no-blobstream, for a seamless tutorial experience.

Changes

File Path Change Summary
developers/.../arbitrum-deploy.md Updated Git checkout command to tags/v2.2.2-no-blobstream

🐇✨
To the code we hop and bound,
A new tag in git is found.
v2.2.2 without a stream,
For smoother deploys, we team! 🚀
🐇✨

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

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.

Copy link
Contributor

github-actions bot commented Jan 24, 2024

PR Preview Action v1.4.6
🚀 Deployed preview to https://celestiaorg.github.io/docs/pr-preview/pr-1380/
on branch gh-pages at 2024-01-24 20:05 UTC

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between e0955e6 and 77ded87.
Files selected for processing (1)
  • developers/arbitrum-deploy.md (1 hunks)
Files skipped from review due to trivial changes (1)
  • developers/arbitrum-deploy.md

@jcstein jcstein force-pushed the jcs/update-2.2.2-nitro-no-blobstream branch from 77ded87 to 72975b9 Compare January 24, 2024 20:04
@jcstein jcstein changed the title fix: linting and formatting fix: update nitro Jan 24, 2024
@jcstein jcstein added the documentation Improvements or additions to documentation label Jan 29, 2024
@Ferret-san Ferret-san enabled auto-merge (squash) January 29, 2024 21:04
@Ferret-san Ferret-san merged commit 2bec065 into main Jan 29, 2024
4 checks passed
@Ferret-san Ferret-san deleted the jcs/update-2.2.2-nitro-no-blobstream branch January 29, 2024 21:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants