10000 Update README.md by faddat · Pull Request #178 · eve-network/eve · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Update README.md #178

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

Merged
merged 2 commits into from
Mar 23, 2024
Merged

Update README.md #178

merged 2 commits into from
Mar 23, 2024

Conversation

faddat
Copy link
Contributor
@faddat faddat commented Mar 23, 2024

Summary by CodeRabbit

  • Documentation
    • Updated software version details in README to reflect transition to CosmWasm v0.51.x.
    • Removed references to vote extensions and Packet Forward Middleware.
    • Added affirmations regarding module and middleware maintenance.

Copy link
Contributor
coderabbitai bot commented Mar 23, 2024

Walkthrough

The changes focus on updating software versions to CosmWasm v0.51.x, removing vote extensions from cosmos-sdk and cometbft versions, and eliminating the mention of Packet Forward Middleware. The emphasis is on maintaining modules and middleware for system efficiency and compatibility with evolving standards.

Changes

Files Change Summary
README.md Updated to transition to CosmWasm v0.51.x, remove vote extensions, eliminate Packet Forward Middleware reference, and affirm commitment to module and middleware maintenance.

🐇✨

CodeRabbit hops through lines of code,
Upgrading systems on its agile mode.
Vote extensions vanish, like a magician's trick,
Modules and middleware, a harmonious pick.
🌟🐇🌿

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.
    • 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 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 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
@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: 4

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 3bc0ad8 and 997d1e5.
Files selected for processing (1)
  • README.md (1 hunks)
Additional comments: 1
README.md (1)
  • 8-19: > 📝 NOTE

This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [70-70]

The repetition of "code == docs" and "docs == logo" seems to be a typo or an oversight. Consider revising for clarity and to avoid redundancy.

Consider revising the contribution guidelines to avoid redundancy and provide clear distinctions between different types of contributions.

README.md Outdated
Comment on lines 8 to 19

## Software at launch

Note: it is possible that we fall back to v0.47.x if simply avoiding vote extensions proves to be ineffective in stopping the issues seen in deployments of comet v0.38.x

* cosmos-sdk v0.50.x without vote extensions
* cometbft v0.38.x without vote extensions
* CosmWasm v0.50.x
* cosmos-sdk v0.50.x
* cometbft v0.38.x
* CosmWasm v0.51.x
* WasmVM v2.0.x
* IBC-go v8.1.x
* Token Factory
* Packet Forward Middleware
* IBC Hooks

this also means fhat Eve, as loving mother and repeatable template, is committed to ensuring that the modules amd middlewares above are kept up to date rigorously, with up to date being defined as supporting the latest release of cosmos-sdk, **regardless of the decisions of other teams**. Eve is very confident in the current cosmos-sdk and ibc-go maintenance teams and smiles warmly at them.
Copy link
Contributor
@coderabbitai coderabbitai bot Mar 23, 2024

Choose a reason for hiding this comment

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

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [41-41]

There's a spelling mistake in "produciton" which should be corrected to maintain professionalism in the documentation.

- Quicksilver and affiliated teams plan to use eve to put the newest SDK, IBC and WASMD into produciton quickly.
+ Quicksilver and affiliated teams plan to use eve to put the newest SDK, IBC, and WASMD into production quickly.

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [47-47]

There's a spelling mistake in "becasue" which should be corrected. Additionally, consider rephrasing for clarity.

- Eve won't use her community pool to compete with your contracts, becasue eve does not have a community pool.
+ Eve won't use a community pool to compete with your contracts, because Eve does not have a community pool.

Copy link
Contributor Author
@faddat faddat Mar 23, 2024

Choose a reason for hiding this comment

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

we refer to eve as a female, like a pirate talking about their ship.

Copy link
Contributor

Choose a reason for hiding this comment

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

@faddat, thank you for clarifying the narrative style of referring to "eve" as a female in the documentation. I'll keep this in mind for future reviews to ensure that my suggestions align with your project's stylistic choices.


New Learnings Added
User: faddat
PR: eve-network/eve#178
File: README.md:8-19
Timestamp: 2024-03-23T21:26:19.771Z
Learning: In the eve-network/eve project documentation, "eve" is personified and referred to as a female. This stylistic choice should be respected in all interactions and suggestions related to the project's documentation.

Note: Learnings are effective only in the context of specific code segments. To apply general coding guidelines, please configure path-based instructions.

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
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: 4

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 997d1e5 and 84e69b3.
Files selected for processing (1)
  • README.md (1 hunks)

Comment on lines +11 to +13
* cosmos-sdk v0.50.x
* cometbft v0.38.x
* CosmWasm v0.51.x
Copy link
Contributor

Choose a reason for hiding this comment

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

The software version updates are accurately reflected, aligning with the PR objectives. However, there are minor typographical errors and inconsistencies in the formatting of the software list that could be improved for better readability.

* cosmos-sdk v0.50.x 
* cometbft v0.38.x 
- * CosmWasm v0.51.x
- * WasmVM v2.0.x
- * IBC-go v8.1.x
- * Token Factory
- * IBC Hooks
+ * CosmWasm v0.51.x
+ * WasmVM v2.0.x
+ * IBC-go v8.1.x
+ * Token Factory
+ * IBC Hooks

Ensure consistent capitalization and spacing for list items to enhance readability.


Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
* cosmos-sdk v0.50.x
* cometbft v0.38.x
* CosmWasm v0.51.x
* cosmos-sdk v0.50.x
* cometbft v0.38.x
* CosmWasm v0.51.x
* WasmVM v2.0.x
* IBC-go v8.1.x
* Token Factory
* IBC Hooks

* IBC Hooks

this also means fhat Eve, as loving mother and repeatable template, is committed to ensuring that the modules amd middlewares above are kept up to date rigorously, with up to date being defined as supporting the latest release of cosmos-sdk, **regardless of the decisions of other teams**. Eve is very confident in the current cosmos-sdk and ibc-go maintenance teams and smiles warmly at them.
This also means that Eve, as a loving mother and repeatable template, is committed to ensuring that the modules and middlewares above are kept up to date rigorously, with "up to date" being defined as supporting the latest release of cosmos-sdk, **regardless of the decisions of other teams**. Eve is very confident in the current cosmos-sdk and ibc-go maintenance teams and smiles warmly at them.
Copy link
Contributor

Choose a reason for hiding this comment

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

The affirmation regarding module and middleware maintenance is clear and aligns with the PR objectives. However, there are grammatical issues and a spelling mistake that need correction.

- This also means that Eve, as a loving mother and repeatable template, is committed to ensuring that the modules and middlewares above are kept up to date rigorously, with "up to date" being defined as supporting the latest release of cosmos-sdk, **regardless of the decisions of other teams**.  Eve is very confident in the current cosmos-sdk and ibc-go maintenance teams and smiles warmly at them.
+ This also means that Eve, as a loving mother and repeatable template, is committed to ensuring that the modules and middlewares above are kept up to date rigorously, with "up to date" being defined as supporting the latest release of cosmos-sdk, **regardless of the decisions of other teams**. Eve is very confident in the current cosmos-sdk and ibc-go maintenance teams and smiles warmly at them.

Correct the grammatical issues and remove the extra space before "Eve is very confident..." for consistency.


Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
This also means that Eve, as a loving mother and repeatable template, is committed to ensuring that the modules and middlewares above are kept up to date rigorously, with "up to date" being defined as supporting the latest release of cosmos-sdk, **regardless of the decisions of other teams**. Eve is very confident in the current cosmos-sdk and ibc-go maintenance teams and smiles warmly at them.
This also means that Eve, as a loving mother and repeatable template, is committed to ensuring that the modules and middlewares above are kept up to date rigorously, with "up to date" being defined as supporting the latest release of cosmos-sdk, **regardless of the decisions of other teams**. Eve is very confident in the current cosmos-sdk and ibc-go maintenance teams and smiles warmly at them.

Comment on lines 8 to 23

## Software at launch

Note: it is possible that we fall back to v0.47.x if simply avoiding vote extensions proves to be ineffective in stopping the issues seen in deployments of comet v0.38.x

* cosmos-sdk v0.50.x without vote extensions
* cometbft v0.38.x without vote extensions
* CosmWasm v0.50.x
* cosmos-sdk v0.50.x
* cometbft v0.38.x
* CosmWasm v0.51.x
* WasmVM v2.0.x
* IBC-go v8.1.x
* Token Factory
* Packet Forward Middleware
* IBC Hooks

this also means fhat Eve, as loving mother and repeatable template, is committed to ensuring that the modules amd middlewares above are kept up to date rigorously, with up to date being defined as supporting the latest release of cosmos-sdk, **regardless of the decisions of other teams**. Eve is very confident in the current cosmos-sdk and ibc-go maintenance teams and smiles warmly at them.
This also means that Eve, as a loving mother and repeatable template, is committed to ensuring that the modules and middlewares above are kept up to date rigorously, with "up to date" being defined as supporting the latest release of cosmos-sdk, **regardless of the decisions of other teams**. Eve is very confident in the current cosmos-sdk and ibc-go maintenance teams and smiles warmly at them.


## Planned software

Copy link
Contributor

Choose a reason for hiding this comment

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

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [42-42]

There's a spelling mistake in "produciton" which should be corrected to maintain professionalism in the documentation.

- Quicksilver and affiliated teams plan to use eve to put the newest SDK, IBC and WASMD into produciton quickly.
+ Quicksilver and affiliated teams plan to use eve to put the newest SDK, IBC, and WASMD into production quickly.

Correct the spelling of "production" and add a comma after "IBC" for grammatical correctness.


📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [48-48]

There's a spelling mistake in "becasue" which should be corrected. Additionally, consider rephrasing for clarity.

- Eve won't use her community pool to compete with your contracts, becasue eve does not have a community pool.
+ Eve won't use her community pool to compete with your contracts, because Eve does not have a community pool.

Correct the spelling of "because" and capitalize "Eve" for consistency.

@faddat faddat merged commit 29359d7 into main Mar 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant
0