Deps and perf

[joe-bowman]

1. Summary

• Update dependencies prior to v1.7.6 release.
• Performance improvement by preallocating slice in utils.Keys()

Summary by CodeRabbit

• Dependency Updates

  • Updated multiple Go module dependencies to their latest versions
  • Upgraded dependencies for go-square, aws-sdk-go, flatbuffers, and OpenTelemetry libraries
  • Incremented versions of cloud services and various Go packages

• Performance Optimization

  • Improved slice initialization in utils/sort.go by pre-allocating capacity

[coderabbitai]

Walkthrough

This pull request primarily focuses on updating dependencies across multiple files. The go.mod files for the main project and icq-relayer have been modified to upgrade various dependencies to their latest versions. Additionally, a small optimization was made in the utils/sort.go file, where the slice initialization now includes a capacity hint based on the input map's length. The changes are mostly version bumps for libraries like OpenTelemetry, Google Cloud, AWS SDK, and various other packages.

Changes

File	Change Summary
go.mod	Updated multiple dependencies, including github.com/celestiaorg/go-square/v2 to v2.1.0, cloud.google.com/go to v0.118.0, and various OpenTelemetry and Google API dependencies
icq-relayer/go.mod	Updated dependencies like cosmossdk.io/math to v1.5.0, github.com/quicksilver-zone/quicksilver to v1.7.5, and multiple cloud, AWS, and telemetry-related packages
utils/sort.go	Modified Keys function to initialize out slice with capacity equal to input map length: out := make([]string, 0, len(in))

Possibly related PRs

• bump math v1.3.0 -> v1.4.0 #1750: Similar go.mod dependency updates, including cosmossdk.io/math and other package version changes

Suggested reviewers

• faddat
• ajansari95

Poem

🐰 Hop, hop, dependencies dance!
Versions leap with each new chance
Slices grow with careful might
Modules update, future bright
Code hops forward, clean and light! 🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b26f4b8 and a2508fe.

⛔ Files ignored due to path filters (3)

• go.sum is excluded by !**/*.sum
• go.work.sum is excluded by !**/*.sum
• icq-relayer/go.sum is excluded by !**/*.sum

📒 Files selected for processing (3)

• go.mod (12 hunks)
• icq-relayer/go.mod (9 hunks)
• utils/sort.go (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: test quicksilver (darwin, arm64)
• GitHub Check: test quicksilver (amd64, windows)
• GitHub Check: test quicksilver (amd64, linux)
• GitHub Check: Analyze

🔇 Additional comments (3)

utils/sort.go (1)

11-11: Great performance optimization!

Preallocating the slice capacity with len(in) eliminates the need for slice growth and reallocation during map key iteration. This is a good optimization, especially for large maps.

icq-relayer/go.mod (1)

Line range hint 6-15: Verify compatibility with updated dependencies.

The dependency updates look good, but please ensure:

1. Compatibility with the updated OpenTelemetry stack (v1.34.0).
2. No breaking changes from cloud.google.com/go upgrade (v0.118.0).
3. Compatibility with the new quicksilver version (v1.7.5).

Run the following script to check for any compatibility issues or breaking changes:

Also applies to: 23-30, 36-39, 47-49, 69-76, 88-88, 112-121, 127-127, 130-130, 141-143, 149-152, 180-188, 220-223, 230-230, 261-261, 268-268, 330-338, 347-347, 352-355

✅ Verification successful

Dependencies verified successfully - all compatibility checks passed

The dependency updates have been verified and show no compatibility issues:

• OpenTelemetry stack (v1.34.0) ✓
• cloud.google.com/go (v0.118.0) ✓
• quicksilver (v1.7.5) ✓

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for breaking changes in major dependency updates.

# Test: Check go.mod and go.sum for any compatibility issues
go mod tidy
go mod verify

# Test: Check if all dependencies can be resolved
go list -m all

Length of output: 62625

go.mod (1)

9-9: Verify dependency updates and replacements.

The dependency updates match those in icq-relayer/go.mod, which is good for consistency. Please ensure:

1. The replace directives remain valid with the updated dependencies.
2. The retracted version v1.7.0 is not referenced anywhere in the codebase.

Run the following script to verify the replace directives and check for any references to the retracted version:

Also applies to: 37-37, 39-39, 50-57, 69-76, 88-88, 112-121, 127-127, 130-130, 141-143, 149-152, 180-188, 220-223, 230-230, 261-261, 268-268, 330-338, 347-347, 352-355

✅ Verification successful

Dependencies and replace directives verified successfully

All dependencies are properly resolved, replace directives are valid, and the retracted version v1.7.0 is not used as a dependency. The v1.7.0 references in the codebase are only in comments, documentation, and upgrade name constants.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify replace directives and check for retracted version references.

# Test: Check if replaced dependencies are still needed and valid
go mod verify

# Test: Search for any references to the retracted version
rg -l "v1\.7\.0"

# Test: Check if all dependencies can be resolved with the replace directives
go list -m all

Length of output: 39538

---

Script:

#!/bin/bash
# Check actual content of files containing v1.7.0 references
echo "=== go.mod ==="
rg "v1\.7\.0" go.mod -A 2 -B 2

echo -e "\n=== x/interchainstaking/keeper/keeper.go ==="
rg "v1\.7\.0" x/interchainstaking/keeper/keeper.go -A 2 -B 2

echo -e "\n=== proto/quicksilver/interchainquery/v1/query.proto ==="
rg "v1\.7\.0" proto/quicksilver/interchainquery/v1/query.proto -A 2 -B 2

echo -e "\n=== app/upgrades/types.go ==="
rg "v1\.7\.0" app/upgrades/types.go -A 2 -B 2

Length of output: 2079

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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>, please review it.
  • 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 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.

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]

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 63.37%. Comparing base (b26f4b8) to head (a2508fe).
Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
utils/sort.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1808   +/-   ##
=======================================
  Coverage   63.37%   63.37%           
=======================================
  Files         172      172           
  Lines       15422    15422           
=======================================
  Hits         9773     9773           
  Misses       4838     4838           
  Partials      811      811           

Flag	Coverage Δ
unittests	63.37% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
utils/sort.go	0.00% <0.00%> (ø)