chore: update submodule data_substrate

[thweetkomputer]

Context

Behavior before and after

Implementation

Design decisions and alternatives

Test plan

• Unit/TCL tests
• Integration or manual validation
• Formatting/build checks
• Compatibility or performance validation, when relevant

Commands and results:

<!-- Paste exact commands and outcomes. State checks that were not run. -->

Risk assessment

Rollback plan

Reviewer guide

Follow-up work

Summary by CodeRabbit

• Chores
  • Updated the underlying data substrate component to a newer revision.
  • No user-facing features or behavior changes were introduced.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 823fb6e7-84ed-4d00-8f2c-3d15f1707da5

📥 Commits

Reviewing files that changed from the base of the PR and between 74fa2f4 and 4349604.

📒 Files selected for processing (1)

• data_substrate

---

Walkthrough

The data_substrate submodule reference advances from commit 9cd8840d71fece0ef61de85c51050f7355411fde to e4247773305eb433d7e0d522b1484e498e45271a. No source declarations or public entities change.

Changes

Submodule update

Layer / File(s)	Summary
Advance data_substrate reference data_substrate	The recorded submodule commit changes to e4247773305eb433d7e0d522b1484e498e45271a.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• eloqdata/eloqkv#536: Updates the same data_substrate submodule pointer.
• eloqdata/eloqkv#517: Updates the pinned data_substrate commit.
• eloqdata/eloqkv#482: Makes the same type of submodule-reference change.

Suggested labels: trigger-ci

Suggested reviewers: liunyl

Poem

A rabbit hops where submodules grow,
One hash departs, one hash says hello.
No code was changed, no branches unfurled,
Just a tiny pointer hopping the world. 🐇

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is only the template headings and contains no actual context, implementation, test, risk, or rollback details.	Fill in each section with concrete PR details, especially context, behavior changes, implementation, test results, risk, rollback, reviewer guide, and follow-up work.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately describes the submodule update.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch update-submodule-zc

---

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