update subm

[yi-xmu]

Summary by CodeRabbit

• Chores
  • Updated internal dependencies to ensure stability and compatibility.

Note: This release contains internal updates with no user-facing changes or new features.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This PR updates two submodule commit references within the storage/eloq directory: store_handler and tx_service are pinned to newer upstream commits. No functional code changes, control flow modifications, or public API alterations are present.

Changes

Cohort / File(s)	Summary
Submodule updates storage/eloq/store_handler, storage/eloq/tx_service	Commit pointers updated to track newer upstream versions; no functional changes

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• These are metadata-only submodule pointer updates with no code logic to review
• Verification that commit hashes are intentional and commits are accessible may be all that's needed

Possibly related PRs

• Update submodules #130: Updates the same submodule pointers (store_handler and tx_service) with identical change patterns
• update subm #117: Also updates both storage/eloq/store_handler and storage/eloq/tx_service submodule references with no functional changes
• Update submodule for txservice #161: Updates both submodule commit references in the same files with comparable scope

Suggested reviewers

• liunyl
• lzxddz
• thweetkomputer

Poem

🐰 A hop, a skip, submodules align,
Two commits refreshed—pure storage design!
No logic bent, no control flow changed,
Just pointers advanced, dependencies arranged.
✨ Git refs dance onward, clean and refined

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'update subm' is vague and incomplete—it appears to be truncated ('subm' likely stands for 'submodule') and does not clearly convey what submodules are being updated or why.	Expand the title to be more descriptive, such as 'Update storage submodule references' or 'Update eloq storage submodules to latest commits' to clearly communicate the purpose of the change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update_subms_ysw

---

📜 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 1258d98 and d26cdfd.

📒 Files selected for processing (2)

• storage/eloq/store_handler (1 hunks)
• storage/eloq/tx_service (1 hunks)

🔇 Additional comments (2)

storage/eloq/tx_service (1)

1-1: Submodule reference format is valid.

The commit hash 4385208f19e195afe27bce888ccf980d83905fb6 follows the correct 40-character SHA-1 format, and the submodule is properly configured in .gitmodules pointing to https://github.com/eloqdata/tx_service.git.

Ensure that:

1. The referenced commit has been reviewed and approved in the tx_service repository.
2. The changes in this submodule version are compatible with the current eloq-10.6.10 branch.

storage/eloq/store_handler (1)

1-1: The review comment contains incorrect assumptions about the submodule changes.

Upon verification, the git state shows that both storage/eloq/store_handler and storage/eloq/tx_service are being added as submodules (not updated), not transitioning from the old commit hash mentioned in the review comment (4def573ca78dab2f59039f0c10e05d5f429e413e). That old commit does not exist in any branch of this repository.

The current state shows:

• store_handler submodule added with commit db471e81e8302d795c997ed441cf14de6730543f
• tx_service submodule added with commit 4385208f19e195afe27bce888ccf980d83905fb6

The verification request in the review comment is based on a false premise. If this is truly a submodule update rather than an initial addition, the old commit hash and context need to be corrected.

Likely an incorrect or invalid review comment.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}