Skip to content

chore(beep boop 🤖): Bump uv.lock (main) (2026-02-20)#2455

Closed
svcnvidia-nemo-ci wants to merge 1 commit intomainfrom
bump-ci-container-2026-02-20-main
Closed

chore(beep boop 🤖): Bump uv.lock (main) (2026-02-20)#2455
svcnvidia-nemo-ci wants to merge 1 commit intomainfrom
bump-ci-container-2026-02-20-main

Conversation

@svcnvidia-nemo-ci
Copy link
Contributor

@svcnvidia-nemo-ci svcnvidia-nemo-ci commented Feb 20, 2026

🚀 PR to bump uv.lock in main.

🤖 This PR will be merged automatically once CI passes.

Summary by CodeRabbit

  • Chores
    • Updated internal dependencies to the latest available versions.

Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@svcnvidia-nemo-ci
Copy link
Contributor Author

/ok to test 1862d35

@copy-pr-bot
Copy link

copy-pr-bot bot commented Feb 20, 2026

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 20, 2026

📝 Walkthrough

Walkthrough

This PR updates the Megatron-LM submodule pointer from commit 8f1c2f8 to commit 7b6e226. The change involves moving the tracked submodule reference to a different commit without modifying code, tests, or public interfaces.

Changes

Cohort / File(s) Summary
Submodule Reference Update
3rdparty/Megatron-LM
Updated submodule pointer to reference a different commit in the Megatron-LM repository.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested reviewers

  • maanug-nv
  • yaoyu-33
🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Title check ⚠️ Warning The title mentions bumping 'uv.lock' but the actual change is a Megatron-LM submodule reference update, not a uv.lock file change. Update the title to accurately reflect the main change: updating the Megatron-LM submodule reference, e.g., 'chore: Update Megatron-LM submodule reference'.
✅ Passed checks (3 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.
Test Results For Major Changes ✅ Passed This PR contains only minor changes—a routine dependency lock file bump and submodule version update with +1/-1 lines changed, not a new feature or breaking change.

✏️ 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
  • Commit unit tests in branch bump-ci-container-2026-02-20-main

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@3rdparty/Megatron-LM`:
- Line 1: The submodule reference for 3rdparty/Megatron-LM points to a
non-existent commit (7b6e226ae0f4e247ccadc5d6a057016b2287ebc5); update the
submodule to a valid upstream ref by verifying the intended commit in the
upstream NVIDIA/Megatron-LM repo, then set the submodule to a reachable
commit/tag/branch (update the commit SHA in the submodule entry or change the
branch in .gitmodules), run git submodule sync and git submodule update --init
--recursive to record the correct SHA, and commit the updated submodule
reference so the repo no longer points to the missing commit.

@@ -1 +1 @@
Subproject commit 8f1c2f8ae53b4e3f32c0ae7f397d8b38a675eaa2
Subproject commit 7b6e226ae0f4e247ccadc5d6a057016b2287ebc5
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# First, check if .gitmodules exists and what it says about Megatron-LM
if [ -f .gitmodules ]; then
  echo "=== .gitmodules content for Megatron-LM ==="
  grep -A 3 "path = 3rdparty/Megatron-LM" .gitmodules
fi

# Check current state of the submodule
echo ""
echo "=== Git status for submodule ==="
cd 3rdparty/Megatron-LM 2>/dev/null && pwd || echo "3rdparty/Megatron-LM directory does not exist or is not accessible"

# Try to verify the commit exists
if [ -d 3rdparty/Megatron-LM/.git ] || [ -f 3rdparty/Megatron-LM/.git ]; then
  echo ""
  echo "=== Verifying commit 7b6e226ae0f4e247ccadc5d6a057016b2287ebc5 ==="
  cd 3rdparty/Megatron-LM
  git cat-file -t 7b6e226ae0f4e247ccadc5d6a057016b2287ebc5 2>&1
  
  echo ""
  echo "=== Log between old (8f1c2f8ae53b4e3f32c0ae7f397d8b38a675eaa2) and new (7b6e226ae0f4e247ccadc5d6a057016b2287ebc5) ==="
  git log --oneline 8f1c2f8ae53b4e3f32c0ae7f397d8b38a675eaa2..7b6e226ae0f4e247ccadc5d6a057016b2287ebc5 2>&1 | head -20
fi

Repository: NVIDIA-NeMo/Megatron-Bridge

Length of output: 266


🏁 Script executed:

#!/bin/bash
cd 3rdparty/Megatron-LM

echo "=== Verifying commit 7b6e226ae0f4e247ccadc5d6a057016b2287ebc5 ==="
git cat-file -t 7b6e226ae0f4e247ccadc5d6a057016b2287ebc5 2>&1

echo ""
echo "=== Checking if previous commit 8f1c2f8ae53b4e3f32c0ae7f397d8b38a675eaa2 exists ==="
git cat-file -t 8f1c2f8ae53b4e3f32c0ae7f397d8b38a675eaa2 2>&1

echo ""
echo "=== Log between old and new commit ==="
git log --oneline 8f1c2f8ae53b4e3f32c0ae7f397d8b38a675eaa2..7b6e226ae0f4e247ccadc5d6a057016b2287ebc5 2>&1 | head -20

echo ""
echo "=== Current submodule commit ==="
git rev-parse HEAD 2>&1

Repository: NVIDIA-NeMo/Megatron-Bridge

Length of output: 852


🏁 Script executed:

#!/bin/bash
cd 3rdparty/Megatron-LM

echo "=== Searching for commit 7b6e226ae0f4e247ccadc5d6a057016b2287ebc5 in all branches/tags ==="
git branch -r --contains 7b6e226ae0f4e247ccadc5d6a057016b2287ebc5 2>&1 || echo "Commit not found in any remote branch"
git tag --contains 7b6e226ae0f4e247ccadc5d6a057016b2287ebc5 2>&1 || echo "Commit not found in any tag"

echo ""
echo "=== List recent commits from main/master branch ==="
git log --oneline -20 origin/main 2>&1 || git log --oneline -20 origin/master 2>&1

echo ""
echo "=== Check if this is a shallow clone ==="
git rev-parse --is-shallow-repository 2>&1

Repository: NVIDIA-NeMo/Megatron-Bridge

Length of output: 1768


🏁 Script executed:

#!/bin/bash
# Check the parent repo's .gitmodules and git index for the submodule pointer
echo "=== Parent repo .gitmodules ==="
cd /home/jailuser/git
cat .gitmodules | grep -A 3 "Megatron-LM"

echo ""
echo "=== Current submodule status in parent repo ==="
git submodule status | grep Megatron-LM

echo ""
echo "=== Check git ls-files for submodule ==="
git ls-files --stage | grep Megatron-LM

Repository: NVIDIA-NeMo/Megatron-Bridge

Length of output: 440


Submodule commit 7b6e226ae0f4e247ccadc5d6a057016b2287ebc5 does not exist in the upstream NVIDIA/Megatron-LM repository.

The commit cannot be found on any remote branch or tag, and the upstream repository refuses it as "not our ref". This will cause submodule initialization and updates to fail. Verify the intended commit is correct, or use a reachable commit from the upstream repository.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@3rdparty/Megatron-LM` at line 1, The submodule reference for
3rdparty/Megatron-LM points to a non-existent commit
(7b6e226ae0f4e247ccadc5d6a057016b2287ebc5); update the submodule to a valid
upstream ref by verifying the intended commit in the upstream NVIDIA/Megatron-LM
repo, then set the submodule to a reachable commit/tag/branch (update the commit
SHA in the submodule entry or change the branch in .gitmodules), run git
submodule sync and git submodule update --init --recursive to record the correct
SHA, and commit the updated submodule reference so the repo no longer points to
the missing commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants