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

chore(go.mod): revert go-ethereum version update #260

Merged
merged 2 commits into from
Jul 29, 2024
Merged

Conversation

lumtis
Copy link
Member

@lumtis lumtis commented Jul 26, 2024

Revert change in 94d6e4e

Since node uses v1.10.26, we need to stick to this version for now. Doesn't seem to affect anything in smart contracts in any case.

Summary by CodeRabbit

  • Chores
    • Updated dependencies for the module, including a downgrade of the Ethereum package and the introduction of new testing capabilities.
    • Several indirect dependencies have been modified or removed to enhance compatibility and stability.

Copy link
Contributor

coderabbitai bot commented Jul 26, 2024

Walkthrough

The changes in the go.mod file for the github.com/zeta-chain/protocol-contracts module primarily involve dependency version updates. Notably, the github.com/ethereum/go-ethereum package has been downgraded, potentially affecting related functionalities. Additional dependencies have been added or replaced, indicating a shift towards improved compatibility and testing capabilities, particularly with the introduction of the testify package for enhanced testing support.

Changes

Files Change Summary
go.mod - Downgraded github.com/ethereum/go-ethereum from v1.13.5 to v1.10.26.
- Changed github.com/deckarep/golang-set from v2.1.0 to v1.8.0.
- Replaced github.com/mmcloughlin/addchain v0.4.0 with github.com/rjeczalik/notify v0.9.1.
- Replaced github.com/supranational/blst v0.3.11 with github.com/stretchr/testify v1.8.2.
- Removed indirect dependencies for golang.org/x/exp, golang.org/x/mod, golang.org/x/sync, and rsc.io/tmplfunc.

Poem

🐇 In the meadow where code does play,
Dependencies shift, like clouds in May.
A hop, a skip, to newer things,
With testify joyously brings!
Downgraded woes, we now set free,
Let’s celebrate this change with glee! 🌼


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.
    • @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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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

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

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 49.13%. Comparing base (2b8508e) to head (81906f2).

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #260       +/-   ##
===========================================
- Coverage   60.29%   49.13%   -11.17%     
===========================================
  Files          16       16               
  Lines         403      403               
  Branches      108      108               
===========================================
- Hits          243      198       -45     
  Misses        160      160               
- Partials        0       45       +45     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2b8508e and 81906f2.

Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
Files selected for processing (1)
  • go.mod (1 hunks)
Additional comments not posted (4)
go.mod (4)

19-19: Verify the impact of replacing blst with testify.

The addition of testify at version v1.8.2 replacing blst might affect functionalities relying on the previous package.


17-17: Verify the impact of replacing addchain with notify.

The addition of notify at version v0.9.1 replacing addchain might affect functionalities relying on the previous package.

Verification successful

No issues found with the replacement of addchain with notify.

The notify package is referenced as an indirect dependency, and there are no direct usages of either notify or addchain in the codebase. Therefore, this change should not have a direct impact on the project's functionality.

  • References to notify found in go.mod and go.sum.
  • No references to addchain found in go.mod and go.sum.
  • No direct usages of notify or addchain found in the codebase.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the impact of replacing `addchain` with `notify` on the codebase.

# Test: Search for usage of `notify` and `addchain` packages. Expect: No breaking changes due to replacement.
rg --type go 'github.com/rjeczalik/notify'
rg --type go 'github.com/mmcloughlin/addchain'

Length of output: 89


Script:

#!/bin/bash
# Description: Verify references to `notify` and `addchain` in go.mod and go.sum files, and check for indirect usages in the codebase.

# Search for references to `notify` and `addchain` in go.mod and go.sum files.
rg 'github.com/rjeczalik/notify' go.mod go.sum
rg 'github.com/mmcloughlin/addchain' go.mod go.sum

# Check for any indirect usages of `notify` and `addchain` in the codebase.
rg --type go 'notify' -g '!go.mod' -g '!go.sum'
rg --type go 'addchain' -g '!go.mod' -g '!go.sum'

Length of output: 437


5-5: Verify the impact of downgrading go-ethereum.

The downgrade from v1.13.5 to v1.10.26 might affect functionalities relying on features or fixes introduced in the later version.


10-10: Verify the impact of downgrading golang-set.

The downgrade from v2.1.0 to v1.8.0 might affect functionalities relying on features or fixes introduced in the later version.

@lumtis lumtis merged commit d1746fd into main Jul 29, 2024
10 of 11 checks passed
@lumtis lumtis deleted the revert/go-ethereum branch July 29, 2024 12:03
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.

4 participants