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

Update our wasmd fork #1948

Merged
merged 9 commits into from
Apr 25, 2024
Merged

Update our wasmd fork #1948

merged 9 commits into from
Apr 25, 2024

Conversation

Taztingo
Copy link
Contributor

@Taztingo Taztingo commented Apr 23, 2024

Description

Our fork of wasmd is still needed because we have additional enforcements when handling a submessage from a smart contract. This updates our fork to v0.50.0.

Related to: #1760


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against correct branch (see CONTRIBUTING.md)
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Wrote unit and integration tests
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/)
  • Added relevant godoc comments.
  • Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
  • Re-reviewed Files changed in the Github PR explorer
  • Review Codecov Report in the comment section below once CI passes

Summary by CodeRabbit

  • Refactor
    • Modified function calls in New to improve module initialization.
  • Documentation
    • Updated the changelog for version v0.50.0.

Copy link
Contributor

coderabbitai bot commented Apr 23, 2024

Walkthrough

The changes encompass enhancements in the app and internal/provwasm packages, focusing on updating NewWrapper calls and function signatures to improve functionality and potentially impact module initialization.

Changes

File Change Summary
app/app.go, internal/provwasm/simulation.go Updated NewWrapper calls and function signatures for improved functionality.

🐇✨
In the fields of code, where logic does play,
A rabbit hopped by, leaving marks in the hay.
New wrappers and routers, a dance of the code,
Modules initialized, along a new road.
Lines of code shift, like shadows at dawn,
In the realm of software, the rabbit hops on. 🌟


Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 4d5af6b and 49af06d.
Files selected for processing (1)
  • CHANGELOG.md (1 hunks)

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

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

@Taztingo Taztingo changed the title Update our wasmd fork to v0.51.0 Update our wasmd fork Apr 23, 2024
@Taztingo Taztingo marked this pull request as ready for review April 23, 2024 16:58
@Taztingo Taztingo requested a review from a team as a code owner April 23, 2024 16:58
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

Out of diff range and nitpick comments (5)
CHANGELOG.md (5)

Line range hint 75-315: Consider using a consistent list marker style in the changelog.

The changelog uses dashes (-) for list items, which is inconsistent with the expected asterisk (*) style. For consistency and to adhere to Markdown best practices, consider using asterisks for list items throughout the changelog.


Line range hint 189-610: Ensure URLs are properly formatted in Markdown.

Several entries in the changelog contain bare URLs. For better readability and to follow Markdown best practices, consider using Markdown link syntax to format these URLs properly.


Line range hint 906-906: Remove unnecessary spaces inside emphasis markers.

- * Fixed ** some ** emphasis errors.
+ * Fixed **some** emphasis errors.

There are unnecessary spaces inside the emphasis markers, which could lead to improper rendering of the text. Removing these spaces will ensure the text is emphasized correctly.


Line range hint 302-302: Ensure there are no unnecessary spaces inside code span elements.

- Here is a ` code ` example.
+ Here is a `code` example.

There are unnecessary spaces inside the code span elements. Removing these spaces will ensure the code is displayed correctly.


Line range hint 778-1352: Remove multiple consecutive blank lines.

- 
-
+ 

There are multiple consecutive blank lines in the document, which could affect the readability and structure of the content. Reducing these to a single blank line will help maintain a cleaner and more organized document.

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

Out of diff range and nitpick comments (4)
CHANGELOG.md (4)

Line range hint 75-315: Change list markers from dashes (-) to asterisks (*) for consistency with Markdown standards.

- - Bump cosmos-SDK to `v0.50.2` (from `v0.46.13-pio-2`) [#1772](https://github.com/provenance-io/provenance/issues/1772).
+ * Bump cosmos-SDK to `v0.50.2` (from `v0.46.13-pio-2`) [#1772](https://github.com/provenance-io/provenance/issues/1772).

Line range hint 189-610: Wrap bare URLs in angle brackets to prevent them from being interpreted as Markdown links.

- https://github.com/provenance-io/provenance/issues/1772
+ <https://github.com/provenance-io/provenance/issues/1772>

Line range hint 906-906: Remove unnecessary spaces inside emphasis markers for correct Markdown formatting.

- *message ** PR<pull-request-number>**
+ *message **PR<pull-request-number>**

Line range hint 302-302: Remove unnecessary spaces inside code span elements for correct Markdown formatting.

- ` message #<issue-number> `
+ `message #<issue-number>`

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

Out of diff range and nitpick comments (3)
CHANGELOG.md (3)

Line range hint 75-316: Consistent Markdown Formatting for Unordered Lists

The changelog uses dashes (-) instead of asterisks (*) for unordered lists. For consistency and to adhere to common Markdown practices, consider using asterisks for unordered lists. Here's how you can update the formatting:

- - Bump `wasmd` to v0.17.0 [#345](https://github.com/provenance-io/provenance/issues/345)
+ * Bump `wasmd` to v0.17.0 [#345](https://github.com/provenance-io/provenance/issues/345)

Line range hint 779-1353: Remove Multiple Consecutive Blank Lines

There are multiple consecutive blank lines in the changelog, which can disrupt the flow and readability of the document. Consider removing these extra blank lines to improve the cleanliness of the document. For example:

- 
-
+ 

Line range hint 190-611: Use Markdown Link Syntax for URLs

There are several instances of bare URLs in the changelog. For better readability and to make the document more accessible, consider using Markdown link syntax. For example:

- https://github.com/provenance-io/provenance/issues/345
+ [Issue #345](https://github.com/provenance-io/provenance/issues/345)

@Taztingo Taztingo merged commit b998684 into main Apr 25, 2024
19 of 37 checks passed
@Taztingo Taztingo deleted the taztingo/update-to-wasm-51 branch April 25, 2024 14:30
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.

3 participants