-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugs encountered when cloning a module with a submodule #1853
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
I encountered some problems when I'm trying to use the online service to clone my repository
skscope
. Here is the error message:Waiting for build to start...
Picked Git content provider.
Cloning into '/tmp/repo2dockeri6matnuh'...
HEAD is now at 0a0dc68 Merge pull request #98 from abess-team/create-pull-request/patch
Submodule 'pybind11' ([email protected]:pybind/pybind11.git) registered for path 'pybind11'
Cloning into '/tmp/repo2dockeri6matnuh/pybind11'...
error: cannot run ssh: No such file or directory
fatal: unable to fork
fatal: clone of '[email protected]:pybind/pybind11.git' into submodule path '/tmp/repo2dockeri6matnuh/pybind11' failed
Failed to clone 'pybind11'. Retry scheduled
Cloning into '/tmp/repo2dockeri6matnuh/pybind11'...
error: cannot run ssh: No such file or directory
fatal: unable to fork
fatal: clone of '[email protected]:pybind/pybind11.git' into submodule path '/tmp/repo2dockeri6matnuh/pybind11' failed
Failed to clone 'pybind11' a second time, aborting
Error during build: Command '['git', 'submodule', 'update', '--init', '--recursive']' returned non-zero exit status 1.Error in event stream: Error
To reproduce the message, just enter "https:/abess-team/skscope" in
GitHub repository name or URL
and enter "master" inGit ref (branch, tag, or commit)
and clickLaunch
.From the description, it seems that it goes wrong when cloning
pybind11
, I just want to know how to deal with that?Thanks!
The text was updated successfully, but these errors were encountered: