Remove an error message for the replication feature from old versions

[komamitsu]

Description

We found branch 3.15 and 3.14 contain an error message for the replication feature. It looks like #2652 unexpectedly introduced it to the old versions. This PR removes it from 3.15 and 3.14.

Related issues and/or PRs

#2652

Changes made

Removed the replication feature related error message from CoreError

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes.
• I have considered whether similar issues could occur in other products, components, or modules if this PR is for bug fixes.
• Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
• Tests (unit, integration, etc.) have been added for the changes.
• My changes generate no new warnings.
• Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

None

Release notes

N/A

[gemini-code-assist]

Summary of Changes

Hello @komamitsu, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses an unintended inclusion of a replication feature-related error message in older stable branches of the codebase. The change specifically removes the REPLICATION_NOT_ENABLED error from the CoreError enum, ensuring that these versions accurately reflect their intended functionality and error handling without displaying irrelevant messages.

Highlights

• Error Message Removal: The REPLICATION_NOT_ENABLED error message has been removed from the CoreError enum. This message was inadvertently introduced into older versions (3.14 and 3.15) of the codebase and is not relevant for those branches.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly removes the REPLICATION_NOT_ENABLED error message, which was unintentionally introduced in older versions. The change is straightforward and limited to deleting the unnecessary enum constant from CoreError.java. After reviewing the changes, I find them to be correct and in line with the stated goal. There are no issues.

[Torch3333]

LGTM, thank you!

[brfrn169]

LGTM! Thank you!

[josh-wong]

LGTM! Thank you!🙇🏻‍♂️