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

upgrade fury to apache fury #1434

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

funky-eyes
Copy link

@funky-eyes funky-eyes commented Aug 9, 2024

Motivation:

Explain the context, and why you're making that change.
To make others understand what is the problem you're trying to solve.

Modification:

Describe the idea and modifications you've done.

Result:

Fixes #.

If there is no issue then describe the changes introduced by this PR.

Summary by CodeRabbit

  • New Features

    • Upgraded the Fury library version to 0.7.0, potentially introducing new features and improvements.
  • Bug Fixes

    • Adjusted group identifiers for the Fury library, aligning with the Apache namespace, which may enhance compatibility and stability.
  • Refactor

    • Updated import statements across multiple files to reflect the new package organization under org.apache.fury, ensuring continued functionality.

@sofastack-cla sofastack-cla bot added cla:yes CLA is ok First-time contributor First-time contributor size/M labels Aug 9, 2024
Copy link
Contributor

coderabbitai bot commented Aug 9, 2024

Walkthrough

The recent changes focus on upgrading the fury library across multiple project files. This includes updating the version from 0.4.1 to 0.7.0 and changing the group identifiers from org.furyio to org.apache.fury. These adjustments reflect a significant reorganization of the library, aligning it with Apache's naming conventions, which may improve dependency resolution and project stability.

Changes

Files Change Summary
all/pom.xml, bom/pom.xml Updated fury version from 0.4.1 to 0.7.0 and changed group ID from org.furyio to org.apache.fury.
codec/codec-sofa-fury/pom.xml Changed group ID for fury-core dependency from org.furyio to org.apache.fury.
codec/codec-sofa-fury/src/main/java/com/alipay/... Updated import statements in various files (FurySerializer, SofaRequestFurySerializer, SofaResponseFurySerializer) from io.fury to org.apache.fury, reflecting the new package structure.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant FuryLibrary as Fury
    Client->>Fury: Request Serialization
    Fury-->>Client: Return Serialized Data
Loading

Poem

🐇 In the world of code so bright,
New paths emerge to share the light.
Fury hops from io to org,
With each change, we cheer and forge!
Upgraded versions bring us cheer,
Stability and joy, oh dear! 🌟


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.

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 UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2d8190f and 21152c6.

Files selected for processing (6)
  • all/pom.xml (2 hunks)
  • bom/pom.xml (2 hunks)
  • codec/codec-sofa-fury/pom.xml (1 hunks)
  • codec/codec-sofa-fury/src/main/java/com/alipay/sofa/rpc/codec/fury/FurySerializer.java (1 hunks)
  • codec/codec-sofa-fury/src/main/java/com/alipay/sofa/rpc/codec/fury/serialize/SofaRequestFurySerializer.java (1 hunks)
  • codec/codec-sofa-fury/src/main/java/com/alipay/sofa/rpc/codec/fury/serialize/SofaResponseFurySerializer.java (1 hunks)
Files skipped from review due to trivial changes (2)
  • codec/codec-sofa-fury/src/main/java/com/alipay/sofa/rpc/codec/fury/serialize/SofaRequestFurySerializer.java
  • codec/codec-sofa-fury/src/main/java/com/alipay/sofa/rpc/codec/fury/serialize/SofaResponseFurySerializer.java
Additional comments not posted (6)
codec/codec-sofa-fury/pom.xml (1)

31-31: Dependency Group ID Updated

The group ID for the fury-core dependency has been updated to org.apache.fury, aligning with the Apache version of the library. Ensure that this change is compatible with the rest of the project dependencies.

codec/codec-sofa-fury/src/main/java/com/alipay/sofa/rpc/codec/fury/FurySerializer.java (1)

33-38: Import Statements Updated

The import statements have been updated to reflect the new package structure under org.apache.fury. This change is necessary for compatibility with the Apache version of the Fury library. Ensure that all usages of these imports are compatible with the new library version.

Also applies to: 44-44

bom/pom.xml (2)

42-42: Fury Library Version Updated

The version of the Fury library has been upgraded from 0.4.1 to 0.6.0. This update may include new features, improvements, or bug fixes. Ensure compatibility with the rest of the project.


306-306: Dependency Group ID Updated

The group ID for the fury-core dependency has been updated to org.apache.fury, aligning with the Apache version of the library. Ensure that this change is compatible with the rest of the project dependencies.

all/pom.xml (2)

445-445: Verify the correct usage of the new group ID org.apache.fury.

The groupId for fury-core has been changed from org.furyio to org.apache.fury. Ensure this new group ID is correctly referenced throughout the project.

Verification successful

The new group ID org.apache.fury is correctly used throughout the project.

The old group ID org.furyio is not found, indicating a successful transition to the new group ID. The relevant pom.xml files reflect this change consistently.

  • codec/codec-sofa-fury/pom.xml
  • all/pom.xml
  • bom/pom.xml
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the correct usage of the new group ID `org.apache.fury`.
# Test: Search for references to the old and new group IDs to ensure consistency.

rg --type xml 'org\.furyio|org\.apache\.fury' -A 3

Length of output: 733


76-76: Verify compatibility with Fury version 0.6.0.

The fury.version has been upgraded from 0.4.1 to 0.6.0. Ensure that this version is compatible with your project and does not introduce breaking changes.

@funky-eyes
Copy link
Author

@chuailiwu PTAL

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 UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 21152c6 and 793fa7f.

Files selected for processing (3)
  • all/pom.xml (2 hunks)
  • bom/pom.xml (2 hunks)
  • codec/codec-sofa-fury/src/main/java/com/alipay/sofa/rpc/codec/fury/FurySerializer.java (1 hunks)
Files skipped from review due to trivial changes (1)
  • codec/codec-sofa-fury/src/main/java/com/alipay/sofa/rpc/codec/fury/FurySerializer.java
Additional comments not posted (4)
bom/pom.xml (2)

42-42: Upgrade to Apache Fury version 0.7.0.

The version upgrade from 0.4.1 to 0.7.0 indicates potential new features or improvements. Ensure compatibility with the rest of the codebase.


306-306: Update group ID to org.apache.fury.

The group ID change from org.furyio to org.apache.fury reflects a rebranding or organizational change. Verify that all relevant references in the codebase are updated accordingly.

all/pom.xml (2)

76-76: Upgrade to Apache Fury version 0.7.0.

The version upgrade from 0.4.1 to 0.7.0 indicates potential new features or improvements. Ensure compatibility with the rest of the codebase.


445-445: Update group ID to org.apache.fury.

The group ID change from org.furyio to org.apache.fury reflects a rebranding or organizational change. Verify that all relevant references in the codebase are updated accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla:yes CLA is ok First-time contributor First-time contributor size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant