update submoulde

[lokax]

Summary by CodeRabbit

• Chores
  • Updated an internal dependency reference for a backend component. No user-facing changes or functional differences expected from this update.

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

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request updates the submodule reference for src/mongo/db/modules/eloq/data_substrate to a newer commit hash; no code changes are included.

Changes

Cohort / File(s)	Summary
Submodule update src/mongo/db/modules/eloq/data_substrate	Updated submodule commit pointer from 00f64054ae7a7d18d8ab9005f2c1797485ee4370 to 44c32ca3e94c3a382cea2d72b86443e1015c8372

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Verify the target commit hash and its provenance.

Possibly related PRs

• update submodule #341: Also updates the submodule pointer for src/mongo/db/modules/eloq/data_substrate (different target commit).
• refactor init process #342: Related update/refactor inside the same data_substrate submodule referenced here.

Suggested labels

trigger-ci

Suggested reviewers

• lzxddz

Poem

🐰 I hopped the git log, changed a line so small,
A pointer nudged forward, no code to stall.
Commits rearranged like carrots in a row,
Quiet update — springtime in the repo! 🥕

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'update submoulde' contains a typo ('submoulde' instead of 'submodule') and is too vague to clearly describe which submodule is being updated or why.	Correct the typo and use a more specific title like 'Update data_substrate submodule to e514120' to clearly indicate which submodule is being updated and provide context.

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

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 23c01c0 and 879e041.

📒 Files selected for processing (1)

• src/mongo/db/modules/eloq/data_substrate (1 hunks)

---

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 pointer to a new commit. The change advances the submodule from commit 00f64054ae7a7d18d8ab9005f2c1797485ee4370 to commit e514120cee8e39d298a82aaa06711046234e8275.

• Updates the submodule reference to incorporate latest changes from the data_substrate repository

Comments suppressed due to low confidence (1)

src/mongo/db/modules/eloq/data_substrate:1

• Corrected spelling of 'submoulde' to 'submodule' in the PR title.

---

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

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fda3b2a and 23c01c0.

📒 Files selected for processing (1)

• src/mongo/db/modules/eloq/data_substrate (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: githubzilla
Repo: eloqdata/eloqdoc PR: 279
File: src/mongo/db/modules/eloq/CMakeLists.txt:54-55
Timestamp: 2025-11-28T10:55:21.020Z
Learning: In src/mongo/db/modules/eloq/CMakeLists.txt, the CMake options EXT_TX_PROC_ENABLED, FORK_HM_PROCESS, and STATISTICS are used by the data_substrate submodule build system and should be retained as configuration interface options.

📚 Learning: 2025-11-28T10:55:21.020Z

Learnt from: githubzilla
Repo: eloqdata/eloqdoc PR: 279
File: src/mongo/db/modules/eloq/CMakeLists.txt:54-55
Timestamp: 2025-11-28T10:55:21.020Z
Learning: In src/mongo/db/modules/eloq/CMakeLists.txt, the CMake options EXT_TX_PROC_ENABLED, FORK_HM_PROCESS, and STATISTICS are used by the data_substrate submodule build system and should be retained as configuration interface options.

Applied to files:

• src/mongo/db/modules/eloq/data_substrate

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Minor: Fix PR title typo.

The PR title contains "submoulde" which should be "submodule".

🤖 Prompt for AI Agents

In src/mongo/db/modules/eloq/data_substrate around lines 1 to 1, the PR title
contains a typo "submoulde" — update the PR title to "submodule" to correct the
spelling; ensure any related branch name or references (if used) are also
updated to match the corrected word.

---

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash

# Check if the submodule reference file exists
if [ -f "src/mongo/db/modules/eloq/data_substrate" ]; then
  echo "=== Submodule reference file exists ==="
  cat "src/mongo/db/modules/eloq/data_substrate"
else
  echo "=== Submodule reference file not found ==="
  ls -la src/mongo/db/modules/eloq/ 2>/dev/null || echo "Directory does not exist"
fi

# Search for CMakeLists.txt in the parent build configuration
echo ""
echo "=== Searching for CMakeLists.txt ==="
find src/mongo/db/modules/eloq -name "CMakeLists.txt" -type f 2>/dev/null | head -5

# Look for the mentioned CMake options in CMakeLists.txt
echo ""
echo "=== Searching for CMake options ==="
if [ -f "src/mongo/db/modules/eloq/CMakeLists.txt" ]; then
  echo "Found CMakeLists.txt at src/mongo/db/modules/eloq/CMakeLists.txt"
  sed -n '45,65p' "src/mongo/db/modules/eloq/CMakeLists.txt"
else
  rg "EXT_TX_PROC_ENABLED|FORK_HM_PROCESS|STATISTICS" src/mongo/db/modules/eloq/ 2>/dev/null || echo "Options not found in eloq directory"
fi

# Check .gitmodules to understand submodule configuration
echo ""
echo "=== Checking .gitmodules ==="
if [ -f ".gitmodules" ]; then
  grep -A 2 "data_substrate" .gitmodules || echo "data_substrate not found in .gitmodules"
fi

Repository: eloqdata/eloqdoc

Length of output: 1302

---

🏁 Script executed:

#!/bin/bash

# Check current submodule commit
echo "=== Current submodule status ==="
cd src/mongo/db/modules/eloq/data_substrate 2>/dev/null && {
  git log --oneline -1
  echo "Current commit: $(git rev-parse HEAD)"
} || echo "Not a git repository or submodule not initialized"

# Check if the old and new commit hashes from the review exist
echo ""
echo "=== Checking commit references ==="
cd - >/dev/null 2>&1

# Look at git index to understand what changed
echo ""
echo "=== Git status for data_substrate ==="
git status src/mongo/db/modules/eloq/data_substrate 2>/dev/null || echo "Unable to check git status"

# Check the actual submodule pointer
echo ""
echo "=== Submodule pointer in .git/config ==="
git config --file=.git/config --name-only --get-regexp "submodule.*.url" 2>/dev/null | head -5

# Show the submodule commit reference from git ls-files
echo ""
echo "=== Git index info for data_substrate ==="
git ls-files -s src/mongo/db/modules/eloq/data_substrate 2>/dev/null || echo "Unable to read index"

Repository: eloqdata/eloqdoc

Length of output: 492

---

Verify the data_substrate submodule update maintains build compatibility.

This PR updates the data_substrate submodule reference. Before merging, ensure:

1. The submodule update is compatible with the existing CMake configuration, particularly the options (EXT_TX_PROC_ENABLED, FORK_HM_PROCESS, STATISTICS) passed from the parent build system.
2. The full build pipeline passes with the updated submodule reference.
3. Any breaking changes introduced in the submodule are identified and addressed.

Update the PR description to document what changed in the submodule and why this update is necessary.

🤖 Prompt for AI Agents

In src/mongo/db/modules/eloq/data_substrate (lines 1-1), the updated
data_substrate submodule may break the parent CMake integration and CI; verify
compatibility by pulling the new submodule commit, inspect its CMakeLists and
any interface headers for changes to the build options EXT_TX_PROC_ENABLED,
FORK_HM_PROCESS, and STATISTICS, and ensure the parent project still forwards or
defines those options (add option forwarding or compatibility shims in the
parent CMake if needed); run a full configure+build (cmake && make) and the full
test suite/CI pipeline to surface build or runtime regressions; if any API/CMake
option changes are found, update the parent code to adapt (or add conditional
fallbacks) and then update the PR description documenting the exact submodule
commit, the changes that affected compatibility, and the fixes you applied.