chore: update tx_service submodule to 9b5be6b

[eatbreads]

Summary by CodeRabbit

• Chores
  • Updated a submodule dependency to a newer commit; this is an internal maintenance update with no user-facing functional changes.
  • No changes to public APIs or exported declarations.

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

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

Walkthrough

This PR updates the data_substrate submodule pointer from commit ecb6998bc1e7a08c5a9c787d9b198e77a2049f18 to 7a746586ce989f44c0438478a29d5ebf7aaa22ec with no other code or API changes.

Changes

Cohort / File(s)	Summary
Submodule Update data_substrate	Updated submodule pointer from ecb6998bc1e7a08c5a9c787d9b198e77a2049f18 → 7a746586ce989f44c0438478a29d5ebf7aaa22ec

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update submodule #187 — Also updates the data_substrate submodule pointer (different target commit).
• update submodule: adapt to submodule rearragement #200 — Pointer-only update of the data_substrate submodule.
• update submodule #167 — Updates the same data_substrate submodule pointer to a different commit.

Suggested reviewers

• lzxddz
• yi-xmu

Poem

🐰 A little hop, a tiny tick—
The pointer skips, the trees stay thick.
New commit found, the trail’s in view,
I nibble carrots, merge is through. ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title references commit 9b5be6b, but the actual commit message and summary indicate the submodule was updated to commit 7a746586ce989f44c0438478a29d5ebf7aaa22ec, creating a discrepancy between the title and the actual change.	Update the PR title to match the actual commit hash: 'chore: update tx_service submodule to 7a74658' to accurately reflect what was changed.

✅ 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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a 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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@data_substrate`:
- Line 1: The PR title and commit message reference the wrong commit hash for
the data_substrate submodule update: the submodule (data_substrate →
data_substrate/tx_service pointing to tx_service.git) is actually being moved to
commit 7a746586ce989f44c0438478a29d5ebf7aaa22ec but the PR title shows 9b5be6b;
update the PR title and the submodule update commit message to use the full
correct hash 7a746586ce989f44c0438478a29d5ebf7aaa22ec (and optionally include
the short form 7a74658) so the title/message accurately reflect the target
revision for the tx_service submodule.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: List all submodules and check the data_substrate submodule status

# List all submodules in the repository
echo "=== Configured submodules ==="
git config --file .gitmodules --get-regexp path || echo "No .gitmodules found"

# Check if tx_service submodule exists
echo -e "\n=== Checking for tx_service submodule ==="
git config --file .gitmodules --get-regexp 'submodule\..*tx_service.*' || echo "No tx_service submodule found in .gitmodules"

# Show current submodule status
echo -e "\n=== Submodule status ==="
git submodule status

Repository: eloqdata/eloqsql

Length of output: 1124

---

Update PR title to reflect correct commit hash.

The submodule update targets data_substrate (which is the data_substrate/tx_service submodule pointing to the tx_service.git repository), so the PR title's reference to tx_service is correct. However, the commit hash in the PR title appears to be incorrect: the title references 9b5be6b, but the actual commit being updated to is 7a746586ce989f44c0438478a29d5ebf7aaa22ec. Please verify and update the PR title and commit message to reflect the correct commit hash.

🤖 Prompt for AI Agents

In `@data_substrate` at line 1, The PR title and commit message reference the
wrong commit hash for the data_substrate submodule update: the submodule
(data_substrate → data_substrate/tx_service pointing to tx_service.git) is
actually being moved to commit 7a746586ce989f44c0438478a29d5ebf7aaa22ec but the
PR title shows 9b5be6b; update the PR title and the submodule update commit
message to use the full correct hash 7a746586ce989f44c0438478a29d5ebf7aaa22ec
(and optionally include the short form 7a74658) so the title/message accurately
reflect the target revision for the tx_service submodule.