update submodule

[lokax]

Summary by CodeRabbit

• Chores

  • Updated an internal submodule reference to keep internal components in sync; no functional, API, or behavioral changes.

• Notes

  • No user-visible changes in this release. Existing features and behaviors remain unchanged.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

Walkthrough

This PR updates the submodule pointer for src/mongo/db/modules/eloq/data_substrate from commit 4b74b90098f7d7c500f08474871c64d98b2f4dba to b4e33a279b1789f4e9a3cdf3430bd26d213fb424. No functional, API, or control-flow changes are introduced.

Changes

Cohort / File(s)	Summary
Submodule Reference Update src/mongo/db/modules/eloq/data_substrate	Submodule commit pointer updated from 4b74b90098f7d7c500f08474871c64d98b2f4dba to b4e33a279b1789f4e9a3cdf3430bd26d213fb424 (no code, API, or behavior changes).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• update submodule #412: Also updates the src/mongo/db/modules/eloq/data_substrate submodule pointer.
• update subm #381: Another PR changing the same submodule reference only.
• update submoulde #375: Submodule commit pointer update for the same path.

Suggested reviewers

• liunyl
• yi-xmu

Poem

🐇 I hopped a little commit and left a tiny trace,
A hash swapped places in a quiet, tidy space.
No functions startled, no tests did alarm,
I munch a crisp carrot and pat the code with charm. 🥕

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'update submodule' is vague and generic, lacking specific details about which submodule was updated or why.	Consider using a more descriptive title that specifies which submodule was updated (e.g., 'Update data_substrate submodule to b4e33a2') and ideally the reason for the update.

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

[Copilot]

Pull request overview

This PR updates the data_substrate submodule to a newer commit, advancing from commit a7a327d to 369c6bd2.

Changes:

• Updated the data_substrate submodule reference to a newer commit

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.