ci(machines): mark container mounts as safe git directories#588
Conversation
Agent-Logs-Url: https://github.com/deepmodeling/dpdispatcher/sessions/f5f1bda5-3b73-4cfc-9a60-d0515318eeb5 Co-authored-by: njzjz <9496702+njzjz@users.noreply.github.com>
The previous fix only marked the GitHub Actions workspace on the host runner as safe for git. The failing setuptools/vcs-versioning build runs inside containers where the repository is mounted at /dpdispatcher, so git still rejects the repo as a dubious ownership checkout. Mark the actual in-container repository mount as safe before installing and building the package in the ssh, ssh_rsync, slurm, and pbs CI jobs. Authored by OpenClaw (model: custom-chat-jinzhezeng-group/gpt-5.4)
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 18 minutes and 50 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #588 +/- ##
=======================================
Coverage 48.33% 48.33%
=======================================
Files 40 40
Lines 3958 3958
=======================================
Hits 1913 1913
Misses 2045 2045 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
Fixes CI failures in the “machines” GitHub Actions workflow caused by Git’s “dubious ownership” protections when setuptools_scm introspects the repo inside containers mounted at /dpdispatcher.
Changes:
- Add a workflow step to mark
$GITHUB_WORKSPACEas a Git safe directory. - Update CI container scripts (
ssh,ssh_rsync,slurm,pbs) to mark/dpdispatcheras a Git safe directory before installing/building.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
ci/ssh.sh |
Configure /dpdispatcher as a safe Git directory inside the test container prior to install/test. |
ci/ssh_rsync.sh |
Same safe-directory configuration inside the rsync-enabled test container. |
ci/slurm.sh |
Configure /dpdispatcher as safe inside the Slurm controller container before build/test. |
ci/pbs.sh |
Configure /dpdispatcher as safe inside the PBS master container before build/install. |
.github/workflows/machines.yml |
Add workflow-level safe-directory config for the host runner workspace. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Problem
/dpdispatcher, sogitstill aborts with a dubious ownership error during setuptools/vcs-versioning introspection.Change
/dpdispatcheras a safe Git directory inside thessh,ssh_rsync,slurm, andpbsCI scripts before installing/building the package.Notes
fatal: detected dubious ownership in repository at '/dpdispatcher'.Authored by OpenClaw (model: custom-chat-jinzhezeng-group/gpt-5.4)