I clone project from server centOS to window , here is the error I got:
git clone ssh://git#xx.xxx.xx.xx:/home/git/srv/repos/projet.t2.company.com.git PROJ_V2
Cloning into 'PROJ_V2'...
git#xx.xxx.xx.xx's password:
remote: Counting objects: 7078, done.
remote: Compressing objects: 100% (5672/5672), done.
remote: Total 7078 (delta 1276), reused 6862 (delta 1073)
Receiving objects: 100% (7078/7078), 107.96 MiB | 18.00 KiB/s, done.
Resolving deltas: 100% (1276/1276), done.
Checking connectivity... done.
fatal: cannot create directory at ' ': No such file or directory
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry the checkout with 'git checkout -f HEAD'
Anyone know how to solve this ?
Related
I get this error when deploying my Heroku application from the CLI. It always worked fine, even today a moment ago. Now I'm getting this:
$ git push heroku main
Enumerating objects: 46, done.
Counting objects: 100% (46/46), done.
Delta compression using up to 8 threads
Compressing objects: 100% (31/31), done.
Writing objects: 100% (31/31), 4.62 KiB | 788.00 KiB/s, done.
Total 31 (delta 23), reused 0 (delta 0), pack-reused 0
remote: Compressing source files... done.
remote: Building source:
remote:
remote: ! Heroku Git error, please try again shortly.
remote: ! See http://status.heroku.com for current Heroku platform status.
remote: ! If the problem persists, please open a ticket
remote: ! on https://help.heroku.com/tickets/new
remote: ! and provide the Request ID dee02a42-c0d2-4740-b9f3-cbfb58c7d95f
remote:
To https://git.heroku.com/vaquita-escolar.git
! [remote rejected] main -> main (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/vaquita-escolar.git'
Advice is appreciated.
It was a temporary Heroku issue. It works now (today).
So I'm trying to do a git clone in windows CMD. But I end-up with following error. I tried every work around. But had no luck.
Cloning into 'tomato-api'...
remote: Counting objects: 67887, done.
remote: Total 17346 (delta 0), reused 0 (delta 0), pack-reused 17346
Receiving objects: 100% (67887/67887), 643.56 MiB | 742.00 KiB/s, done.
Resolving deltas: 100% (7654/7654), done.
fatal: cannot create directory at 'vegitables/market/github.com/docker/distribution/sharing/united-streets/generated_certs.d/localregistry:5440': Invalid argument
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry the checkout with 'git checkout -f HEAD'
The git repository you are trying to clone from has a directory with path consisting of the Windows reserved word - colon (:). Therefore, that directory is not able to be created.
Another approach more recently discussed is to:
git clone --no-checkout the repository
delete all files with ':' in their name (same for files with \ in their name)
Using git filter-repo, you can remove them from the full history of the repository.
When I try to update my Java app on Heroku it fails with a "Argument list too long - bin/receive_untrusted". This happens before the actual build process starts and it's the only error that I'm getting. Of course it build perfect locally..
Counting objects: 95506, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (28630/28630), done.
Writing objects: 100% (95506/95506), 16.95 MiB | 2.82 MiB/s, done.
Total 95506 (delta 42943), reused 94815 (delta 42643)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: Build stream timed out, reverting to polling...
remote:
remote: Build output:
remote: Argument list too long - bin/receive_untrusted
remote: ! Push rejected to xxxxx.
remote:
To https://git.heroku.com/xxxx.git
! [remote rejected] develop -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/xxxxx.git'
The only thing that fixed it for me was resetting the Git repo in Heroku and pushing it from scratch, a described in this answer.
I would like to host couchdb in a free heroku instance. I found here on stackoverflow an answer and it says, it is possible to host erlang code on heroku.
Now I had the idea, to host couchdb on heroku. But it doesn't work. Here is my try:
.>git clone https://github.com/apache/couchdb
.git
Cloning into 'couchdb'...
remote: Counting objects: 55066, done.
remote: Compressing objects: 100% (1582/1582), done.
remote: Total 55066 (delta 2125), reused 3094 (delta 1808)
Receiving objects: 100% (55066/55066), 26.56 MiB | 1.34 MiB/s, done.
Resolving deltas: 100% (36610/36610), done.
Checking out files: 100% (338/338), done.
.>cd couchdb
.\couchdb>explorer .
.\couchdb>git add .
.\couchdb>git commit -m "added proc file"
[master 9c6da00] added proc file
1 file changed, 1 insertion(+)
create mode 100644 Procfile
.\couchdb>heroku create couchdb-cl --region e
u --buildpack https://github.com/archaelus/heroku-buildpack-erlang
Creating couchdb-cl... done, region is eu
BUILDPACK_URL=https://github.com/archaelus/heroku-buildpack-erlang
https://couchdb-cl.herokuapp.com/ | git#heroku.com:couchdb-cl.git
Git remote heroku added
.\couchdb>git push heroku master
Enter passphrase for key '/c/Users/Imanuel/.ssh/id_rsa':
Initializing repository, done.
Counting objects: 40416, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (12588/12588), done.
Writing objects: 100% (40416/40416), 17.50 MiB | 562 KiB/s, done.
Total 40416 (delta 27271), reused 40371 (delta 27237)
-----> Fetching custom git buildpack... done
! Push rejected, no Cedar-supported app detected
To git#heroku.com:couchdb-cl.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git#heroku.com:couchdb-cl.git'
But it fails to push.
Here is the Procfile:
web: erl -pa ebin deps/*/ebin -noshell -boot start_sasl -s reloader -s couchdb
Anyone an idea or maybe another option to host a couchdb instance for free? :)
Heroku built their polyglot platform, which currently supports Ruby or Rails, Node.js, Java, Spring or Play, Python or Django, Clojure and Scala (source).
All other languages including Erlang are built using build packs. You can find Erlang build pack on github. Run the instructions from README and you should be good to go.
when i pull the chages from clone, it is reflected in server and vice versa. but when i push it shows error.
Error message:
git.exe push --progress "origin" master:master
Counting objects: 11, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 474 bytes | 0 bytes/s, done.
Total 6 (delta 3), reused 0 (delta 0)
remote: error: refusing to update checked out branch: refs/heads/master
remote: error: By default, updating the current branch in a non-bare repository
remote: error: is denied, because it will make the index and work tree inconsistent
remote: error: with what you pushed, and will require 'git reset --hard' to match
remote: error: the work tree to HEAD.
remote: error:
remote: error: You can set 'receive.denyCurrentBranch' configuration variable to
remote: error: 'ignore' or 'warn' in the remote repository to allow pushing into
remote: error: its current branch; however, this is not recommended unless you
remote: error: arranged to update its work tree to match what you pushed in some
remote: error: other way.
remote: error:
remote: error: To squelch this message and still keep the default behaviour, set
remote: error: 'receive.denyCurrentBranch' configuration variable to 'refuse'.
To //INCHNLRDFS06/CUB Ebanking$/GIT_Ebank
! [remote rejected] master -> master (branch is currently checked out)
error: failed to push some refs to '//INCHNLRDFS06/CUB Ebanking$/GIT_Ebank'
git did not exit cleanly (exit code 1) (1029 ms # 9/10/2014 6:43:09 PM)
If you are cloning from another user's repository, the origin remote (assuming you're pushing to origin) is linked to that user's repo.
In order to commit and push your changes, you first must fork that user's repo and clone from your fork. Doing so will set up your remote to your repo and you can commit and push as you please.
You can view your remotes in the .git/config file and correct them if you're still having trouble.