Range read block on RW conflict (Update data_substrate only)

[githubzilla]

Summary by CodeRabbit

• Chores
  • Updated internal subproject reference with no functional impact to end-users.

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

[coderabbitai]

Walkthrough

The data_substrate subproject reference was updated to point to a newer commit. This represents a version bump of the dependency without modifications to the consuming project's own code or interfaces.

Changes

Cohort / File(s)	Change Summary
Submodule Update data_substrate	Updated subproject commit reference from ef4c17b0 to 7c0a4262

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Verify the new commit hash exists in the upstream data_substrate repository
• Confirm the submodule update is intentional and not accidental

Poem

🐰 A tiny hop, a commit so clean,
The submodule points to somewhere new,
From one hash home to another's scene—
Dependencies dance, the reference flew!
Carrots satisfied, the merge is due! 🥕

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The PR title mentions 'Range read block on RW conflict' but the actual change only updates a subproject reference in data_substrate with no functional changes described.	Clarify whether the title accurately reflects the nature of this change—a routine subproject version update rather than a feature or fix implementation.

✅ 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

---

📜 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 39fb469 and 153a25b.

📒 Files selected for processing (1)

• data_substrate (1 hunks)

🔇 Additional comments (1)

data_substrate (1)

1-1: Verify the upstream transaction service changes and confirm CI test execution for the range-read RW-conflict behavior.

This PR moves the data_substrate gitlink to 7c0a42621ceaae1283ae0a8a531796b49c547a3a in a massive commit (559 files, 216k+ lines). While comprehensive transaction test files are included (multi.tcl, transactions-on-replica.tcl), the visible CI workflow only runs clang-format—actual test execution is not shown. The commit message "Update data_substrate" provides no details about what changed in the transaction service. Please confirm:

1. What changed in the TxService regarding "range read block on RW conflict" (diff or release notes)
2. That the test suite—particularly transaction conflict scenarios—runs and passes in CI
3. Any breaking changes or new configuration requirements

---

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