I am using github for source control for unreal engine 4. When I publish the branch to github, I get the following error
Enumerating objects: 2865, done.
Counting objects: 100% (2865/2865), done.
Delta compression using up to 8 threads
Compressing objects: 100% (2832/2832), done.
error: RPC failed; curl 56 Send failure: Connection was reset
fatal: the remote end hung up unexpectedlyMiB | 1.75 MiB/s
Writing objects: 100% (2865/2865), 2.56 GiB | 14.18 MiB/s, done.
Total 2865 (delta 198), reused 0 (delta 0), pack-reused 0
fatal: the remote end hung up unexpectedly
Everything up-to-date
I know it's an old post but just in case...
Did you setup source control from within unreal or separately?
I believe doing it from within unreal itself would seriously reduce the size of the commits
Related
I used to have GoogleDrive on my PC that uploaded all my code on the drive. I was working on the main branch because I got this project on GitHub, so I deleted all the desktop.ini files and tried to pull the project to update the changes made by my co-workers, but got this error.
The problem didn't occur to me at first because GoogleDrive takes a few minutes to make all the desktop.ini, but when it did it caused problems.
> git pull pmo main
remote: Enumerating objects: 85, done.
remote: Counting objects: 100% (77/77), done.
remote: Compressing objects: 100% (33/33), done.
remote: Total 59 (delta 25), reused 59 (delta 25), pack-reused 0
Unpacking objects: 100% (59/59), 6.63 KiB | 218.00 KiB/s, done.
fatal: bad object refs/desktop.ini
error: https://github.com/*******/*******.git did not send all necessary objects
I tried to remove the .git/refs/desktop.ini with the command rm but it says that i do not have access to it, even in the powershell.
That is why it is preferable to not work in a network-synchronized drive: git pull/push/clone won't work well with the concurrent synchronization that comes with a Google drive.
It is better to save on that drive a git bundle (which stores your repository in one file), while collaborating with other through the remote GitHub repository (cloned locally in a normal folder)
I have deployed the code once on github using github pages and now i have maked the changes in some of the code and now i am not able to push the code .I deleted the all branches and code on repo and did the process once again but still on live website i am not getting any changes .
PS D:\VJTI_Racing_Website_2.0\frontend> git add .
>> git commit -m "updated"
>> git push origin master
On branch gh-pages
nothing to commit, working tree clean
Enumerating objects: 26890, done.
Counting objects: 100% (26890/26890), done.
Delta compression using up to 8 threads
Compressing objects: 100% (21199/21199), done.
Writing objects: 100% (26890/26890), 779.96 MiB | 1.96 MiB/s, done.
Total 26890 (delta 4725), reused 26890 (delta 4725), pack-reused 0
remote: Resolving deltas: 100% (4725/4725), done.
remote: warning: File node_modules/.cache/default-development/3.pack is 52.95 MB; this is larger than GitHub's recommended maximum file size of 50.00 MB
remote: error: Trace: d119776a9de8bb6b95dccf52e4031387455d238a7a7367d558a094750a2328de
remote: error: See http://git.io/iEPt8g for more information.
remote: error: File node_modules/.cache/default-development/0.pack is 490.10 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com.
To https://github.com/vjtiracing/VJTI_Racing_Website_2.0.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://github.com/vjtiracing/VJTI_Racing_Website_2.0.git'
the error showing is of large file but I deleted the node modules file and also cleared the cache please someone help me out here.
This question already has answers here:
Issues with pushing large files through Git
(7 answers)
What is the storage mechanism behind Git Large File Storage?
(1 answer)
Closed 12 months ago.
On a local GitHub repo, I have a directory called "s3" that contains a Terraform file for creating an AWS S3 Bucket remotely. When I try pushing the directory onto my remote repo, I keep getting this error.
$ git push origin repo
Uploading LFS objects: 100% (1/1), 1.3 KB | 0 B/s, done.
Enumerating objects: 22, done.
Counting objects: 100% (22/22), done.
Delta compression using up to 12 threads
Compressing objects: 100% (15/15), done.
Writing objects: 100% (21/21), 50.31 MiB | 1.12 MiB/s, done.
Total 21 (delta 4), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (4/4), completed with 1 local object.
remote: error: Trace: 2bcd19423f0176b3048b9144f26779fab7c903f263a60b8534632e7c697ec700
remote: error: See http://git.io/iEPt8g for more information.
remote: error: File s3/.terraform/providers/registry.terraform.io/hashicorp/aws/3.74.3/windows_amd64/terraform-provider-aws_v3.74.3_x5.exe is 244.70 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com.
To github.com:User/Remote-Repo.git
! [remote rejected] repo -> repo (pre-receive hook declined)
error: failed to push some refs to 'github.com:User/Remote-Repo.git'
I have git lfs installed which should help with pushing files with large sizes, but it isn't.
What am I doing wrong?
Note: Some names in the error have been edited for privacy/security.
I have a folder with codes, i pushed it on github after creating a repository but the process was successful but i can not see any file in the repository, any help guys, this is my cli codes
SydoTech#DESKTOP-PUHK97G MINGW64 /d/james/ict-specialists (master)
$ git remote add origin https://github.com/Kato669/ict-specialist-website.git
SydoTech#DESKTOP-PUHK97G MINGW64 /d/james/ict-specialists (master)
$ git push origin main
error: src refspec main does not match any
error: failed to push some refs to 'https://github.com/Kato669/ict-specialist-website.git'
SydoTech#DESKTOP-PUHK97G MINGW64 /d/james/ict-specialists (master)
$ git push origin master
Enumerating objects: 1383, done.
Counting objects: 100% (1383/1383), done.
Delta compression using up to 4 threads
Compressing objects: 100% (1380/1380), done.
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)
send-pack: unexpected disconnect while reading sideband packet
Writing objects: 100% (1383/1383), 35.93 MiB | 323.00 KiB/s, done.
Total 1383 (delta 181), reused 0 (delta 0), pack-reused 0
fatal: the remote end hung up unexpectedly
Everything up-to-date
SydoTech#DESKTOP-PUHK97G MINGW64 /d/james/ict-specialists (master)
$
Here is the story, we have GitHub working and are using GitDesktop 1.0.10.
We are also using Git LFS 2.3.0 from https://github.com/blog/2432-git-lfs-2-3-0-released ... two devs are able to clone and push repo without issue, one has issues as follows:
WARNING: 'git lfs clone' is deprecated and will not be updated
with new flags from 'git clone'
'git clone' has been updated in upstream Git to have comparable
speeds to 'git lfs clone'.
'git clone' has been updated in upstream Git to have comparable
speeds to 'git lfs clone'.
Cloning into 'C:\Git\SomeRepo'...
remote: Counting objects: 28847, done.
remote: Compressing objects: 0% (1/331)
remote: Compressing objects: 1% (4/331)
remote: Compressing objects: 2% (7/331)
...
remote: Compressing objects: 98% (325/331)
remote: Compressing objects: 99% (328/331)
remote: Compressing objects: 100% (331/331)
remote: Compressing objects: 100% (331/331), done.
Receiving objects: 0% (1/28847)
Receiving objects: 1% (289/28847)
Receiving objects: 2% (577/28847)
Receiving objects: 3% (866/28847)
...
Receiving objects: 96% (27694/28847), 974.57 MiB | 21.10 MiB/s
Receiving objects: 97% (27982/28847), 974.57 MiB | 21.10 MiB/s
Receiving objects: 98% (28271/28847), 974.57 MiB | 21.10 MiB/s
Receiving objects: 99% (28559/28847), 974.57 MiB | 21.10 MiB/s
remote: Total 28847 (delta 547), reused 598 (delta 424), pack-reused 28092
Receiving objects: 100% (28847/28847), 974.57 MiB | 21.10 MiB/s
Receiving objects: 100% (28847/28847), 979.90 MiB | 20.95 MiB/s, done.
Resolving deltas: 0% (0/16327)
Resolving deltas: 1% (306/16327)
Resolving deltas: 2% (343/16327)
Resolving deltas: 5% (822/16327)
Resolving deltas: 7% (1162/16327)
...
Resolving deltas: 98% (16033/16327)
Resolving deltas: 99% (16175/16327)
Resolving deltas: 100% (16327/16327)
Resolving deltas: 100% (16327/16327), done.
batch response: Git credentials for
https://github.com/SomeOrg/SomeProject.git not found:
exit status 1
batch response: Git credentials for
https://github.com/SomeOrg/SomeProject.git not found:
exit status 1
batch response: Git credentials for
https://github.com/SomeOrg/SomeProject.git not found:
exit status 1
batch response: Git credentials for
https://github.com/SomeOrg/SomeProject.git not found:
exit status 1
batch response: Git credentials for
https://github.com/SomeOrg/SomeProject.git not found:
exit status 1
batch response: Git credentials for
https://github.com/SomeOrg/SomeProject.git not found:
exit status 1
batch response: Git credentials for
https://github.com/SomeOrg/SomeProject.git not found:
exit status 1
batch response: Git credentials for
https://github.com/SomeOrg/SomeProject.git not found:
exit status 1
batch response: Git credentials for
https://github.com/SomeOrg/SomeProject.git not found:
exit status 1
error: failed to fetch some objects from 'https://github.com/SomeOrg/SomeProject.git/info/lfs'
I have tried:
Logging in with working credentials on non-working machine
Uninstalling and reinstalling Github Desktop
Deleting files forcing the reinstall of Github Desktop to ask for settings again
Disabled Firewall
Any help here would be very much appreciated, thanks in advance!
This seems to be a bug described in git-lfs/git-lfs issue 2349 and Git for Windows issue 1192
It could be a bug in the way Git for Windows calls git-lfs.exe: if there is no console to use, there won't be a way to communicate with the user.
But then, maybe it does work with winpty as I suggested earlier (even if the OP indicated that it fails), that's why I want an MCVE.
#dscho I think that this is likely. In my testing, I was unable to get LFS to see a pty/tty when invoked by Git for Windows. I have set up a test repository that I have reproduced the bug with: https://github.com/ttaylorr/lfs-gfw-bug
Still, try and install the latest Git-Credential-Manager-for-Windows.
And/or try the same clone from command-line, after installing the very latest Git for Windows (the 2.15.1.2 one).
The OP OverCodingUnderSleeping adds in the comments:
Oddly enough, seems like switching over to SourceTree from GitHub For Desktop solved it....
That means SourceTree either use the "System" Git or an embedded one, which might not exhibit the same bug: check the settings.