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

docs: fix typo #4180

Merged
merged 1 commit into from
Jan 6, 2025
Merged

docs: fix typo #4180

merged 1 commit into from
Jan 6, 2025

Conversation

yangquanshi
Copy link
Contributor

Overview

fix typo for docs/architecture/adr-018-network-upgrades.md

@yangquanshi yangquanshi requested a review from a team as a code owner January 5, 2025 08:47
@yangquanshi yangquanshi requested review from cmwaters and rach-id and removed request for a team January 5, 2025 08:47
Copy link
Contributor

coderabbitai bot commented Jan 5, 2025

📝 Walkthrough

Walkthrough

The document adr-018-network-upgrades.md has been updated to provide more comprehensive details about network upgrade processes. The changes focus on enhancing the understanding of upgrade mechanisms, particularly addressing potential challenges during transaction migrations. A new paragraph in the "Detailed Design" section elaborates on handling halting bugs, introducing a circuit breaker mechanism and discussing approaches to manage apphash mismatches. The "Future Work" section has been expanded to include considerations for signaling upgrade heights and version upgrades during validator voting.

Changes

File Change Summary
docs/architecture/adr-018-network-upgrades.md - Added detailed explanation of halting bug handling
- Introduced circuit breaker mechanism concept
- Expanded "Future Work" section with upgrade signaling considerations

Suggested labels

external

Suggested reviewers

  • cmwaters
  • rach-id
  • evan-forbes
  • rootulp
  • ninabarbakadze

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:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • 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 testing code 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 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 generate unit testing code.
    • @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.

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. (Beta)
  • @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.

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
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.

Actionable comments posted: 0

🧹 Nitpick comments (1)
docs/architecture/adr-018-network-upgrades.md (1)

54-54: Several grammar and style improvements needed

Please apply these corrections to improve readability:

-  - There is a halting bug in the migration or in processing of the first transactions. This most likely would be in the form of an apphash mismatch. This becomes more problematic with delayed execution as the block (with v2 transactions) has already been committed. Immediate execution has the advantage of the apphash mismatch being realised before the data is committed. It's still however feasible to over come this but it involves nodes rolling back the previous state and re-executing the transactions using the v1 state machine (which will skip over the v2 transactions). This means node operators should be able to manually override the app version that the proposer will propose with. Lastly, if state migrations occurred between v2 and v1, a reverse migration would need to be performed which would make things especially difficult. If we are unable to fallback to the previous version and continue then the other option is to remain halted until the bug is patched and the network can update and continue
+  - There is a halting bug in the migration or in processing of the first transactions. This most likely would be in the form of an apphash mismatch. This becomes more problematic with delayed execution, as the block (with v2 transactions) has already been committed. Immediate execution has the advantage of the apphash mismatch being realized before the data is committed. It's still, however, feasible to overcome this, but it involves nodes rolling back the previous state and re-executing the transactions using the v1 state machine (which will skip over the v2 transactions). This means node operators should be able to manually override the app version that the proposer will propose with. Lastly, if state migrations occurred between v2 and v1, a reverse migration would need to be performed, which would make things especially difficult. If we are unable to fall back to the previous version and continue, then the other option is to remain halted until the bug is patched, and the network can update and continue

Changes:

  • Added missing commas in compound sentences
  • Fixed spelling consistency: "realised" → "realized"
  • Corrected compound word: "over come" → "overcome"
  • Fixed verb form: "fallback" → "fall back"
🧰 Tools
🪛 LanguageTool

[uncategorized] ~54-~54: Possible missing comma found.
Context: ...s becomes more problematic with delayed execution as the block (with v2 transactions) has...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~54-~54: Do not mix variants of the same word (‘realise’ and ‘realize’) within a single text.
Context: ...advantage of the apphash mismatch being realised before the data is committed. It's stil...

(EN_WORD_COHERENCY)


[grammar] ~54-~54: This is normally spelled as one word.
Context: ...mmitted. It's still however feasible to over come this but it involves nodes rolling back...

(OVER_COMPOUNDS)


[uncategorized] ~54-~54: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...still however feasible to over come this but it involves nodes rolling back the prev...

(COMMA_COMPOUND_SENTENCE)


[uncategorized] ~54-~54: Possible missing comma found.
Context: ...1, a reverse migration would need to be performed which would make things especially diff...

(AI_HYDRA_LEO_MISSING_COMMA)


[grammar] ~54-~54: The word “fallback” is a noun. The verb is spelled with a white space.
Context: ...pecially difficult. If we are unable to fallback to the previous version and continue th...

(NOUN_VERB_CONFUSION)


[uncategorized] ~54-~54: Possible missing comma found.
Context: ...to fallback to the previous version and continue then the other option is to remain halt...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~54-~54: Use a comma before “and” if it connects two independent clauses (unless they are closely connected and short).
Context: ...o remain halted until the bug is patched and the network can update and continue -...

(COMMA_COMPOUND_SENTENCE_2)


[typographical] ~54-~54: Consider adding a comma.
Context: ... and the network can update and continue - There is a bug that is detected that could ha...

(IF_THERE_COMMA)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d80f027 and f88d025.

📒 Files selected for processing (1)
  • docs/architecture/adr-018-network-upgrades.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/architecture/adr-018-network-upgrades.md

[uncategorized] ~54-~54: Possible missing comma found.
Context: ...s becomes more problematic with delayed execution as the block (with v2 transactions) has...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~54-~54: Do not mix variants of the same word (‘realise’ and ‘realize’) within a single text.
Context: ...advantage of the apphash mismatch being realised before the data is committed. It's stil...

(EN_WORD_COHERENCY)


[grammar] ~54-~54: This is normally spelled as one word.
Context: ...mmitted. It's still however feasible to over come this but it involves nodes rolling back...

(OVER_COMPOUNDS)


[uncategorized] ~54-~54: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...still however feasible to over come this but it involves nodes rolling back the prev...

(COMMA_COMPOUND_SENTENCE)


[uncategorized] ~54-~54: Possible missing comma found.
Context: ...1, a reverse migration would need to be performed which would make things especially diff...

(AI_HYDRA_LEO_MISSING_COMMA)


[grammar] ~54-~54: The word “fallback” is a noun. The verb is spelled with a white space.
Context: ...pecially difficult. If we are unable to fallback to the previous version and continue th...

(NOUN_VERB_CONFUSION)


[uncategorized] ~54-~54: Possible missing comma found.
Context: ...to fallback to the previous version and continue then the other option is to remain halt...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~54-~54: Use a comma before “and” if it connects two independent clauses (unless they are closely connected and short).
Context: ...o remain halted until the bug is patched and the network can update and continue -...

(COMMA_COMPOUND_SENTENCE_2)


[typographical] ~54-~54: Consider adding a comma.
Context: ... and the network can update and continue - There is a bug that is detected that could ha...

(IF_THERE_COMMA)

🔇 Additional comments (1)
docs/architecture/adr-018-network-upgrades.md (1)

54-54: Excellent addition of failure handling scenarios!

The new paragraph adds crucial information about handling halting bugs during upgrades, including apphash mismatches and the circuit breaker mechanism. This significantly improves the document's completeness regarding upgrade safety.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~54-~54: Possible missing comma found.
Context: ...s becomes more problematic with delayed execution as the block (with v2 transactions) has...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~54-~54: Do not mix variants of the same word (‘realise’ and ‘realize’) within a single text.
Context: ...advantage of the apphash mismatch being realised before the data is committed. It's stil...

(EN_WORD_COHERENCY)


[grammar] ~54-~54: This is normally spelled as one word.
Context: ...mmitted. It's still however feasible to over come this but it involves nodes rolling back...

(OVER_COMPOUNDS)


[uncategorized] ~54-~54: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...still however feasible to over come this but it involves nodes rolling back the prev...

(COMMA_COMPOUND_SENTENCE)


[uncategorized] ~54-~54: Possible missing comma found.
Context: ...1, a reverse migration would need to be performed which would make things especially diff...

(AI_HYDRA_LEO_MISSING_COMMA)


[grammar] ~54-~54: The word “fallback” is a noun. The verb is spelled with a white space.
Context: ...pecially difficult. If we are unable to fallback to the previous version and continue th...

(NOUN_VERB_CONFUSION)


[uncategorized] ~54-~54: Possible missing comma found.
Context: ...to fallback to the previous version and continue then the other option is to remain halt...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~54-~54: Use a comma before “and” if it connects two independent clauses (unless they are closely connected and short).
Context: ...o remain halted until the bug is patched and the network can update and continue -...

(COMMA_COMPOUND_SENTENCE_2)


[typographical] ~54-~54: Consider adding a comma.
Context: ... and the network can update and continue - There is a bug that is detected that could ha...

(IF_THERE_COMMA)

@rootulp rootulp changed the title chore: fix typo for docs/architecture/adr-018-network-upgrades.md chore: fix typo Jan 6, 2025
@rootulp rootulp changed the title chore: fix typo docs: fix typo Jan 6, 2025
@rootulp rootulp enabled auto-merge (squash) January 6, 2025 14:19
@rootulp rootulp merged commit e4c9f2d into celestiaorg:main Jan 6, 2025
31 checks passed
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.

3 participants