Files that are not under git management fail

Asked 2 years ago, Updated 2 years ago, 61 views

To push to github

git push

When you do,

 Delta compression using up to 6 threads.
Compressing objects: 100% (437/437), done.
Writing objects: 100% (445/445), 221.08 MiB | 7.39 MiB/s, done.
Total 445(delta3), reused0(delta0)
remote:Resolving delta: 100% (3/3), done.
remote:error:GH001:Large files detected.You may want to try Git Large File Storage -https://git-lfs.github.com.
remote:error:Trace:46e6e6146393dfce0c018b2491623426
remote:error:See http://git.io/iEPt8g for more information.
remote:error:File SRCNN-pytorch/BLAH_BLAH/91-image_x3.h5 is 181.82 MB; this exceeds GitHub's file size limit of 100.00 MB
remote:error:File SRCNN-pytorch/BLAH_BLAH/91-image_x4.h5 is 180.89 MB; this exceeds GitHub's file size limit of 100.00 MB
To https://github.com/Hika-Kondo/Super_Resolution.git
 ! [remote rejected] master->master (pre-receive hook decremented)
error: failed to push some refs to 'https://github.com/***/Super_Resolution.git'

I got an error, so

 gitrm --cache/SRCNN-pytorch/BLAH_BLAH

and

 gits-files

I checked the git-managed file in

SRCNN-pytorch/.gitignore
SRCNN-pytorch /README.md
SRCNN-pytorch/data/butterfly_GT.bmp
SRCNN-pytorch/data/butterfly_GT_bicubic_x3.bmp
SRCNN-pytorch/data/butterfly_GT_srcnn_x3.bmp
SRCNN-pytorch/data/ppt3.bmp
SRCNN-pytorch/data/ppt3_bicubic_x3.bmp
SRCNN-pytorch/data/ppt3_srcnn_x3.bmp
SRCNN-pytorch/data/zebra.bmp
SRCNN-pytorch/data/zebra_bicubic_x3.bmp
SRCNN-pytorch/data/zebra_srcnn_x3.bmp
SRCNN-pytorch /datasets.py
SRCNN-pytorch /models.py
SRCNN-pytorch /prepare.py
SRCNN-pytorch /test.py
SRCNN-pytorch/thumbnails/fig1.png
SRCNN-pytorch /train.py
SRCNN-pytorch /utils.py

Verify that the file with the error next to it is out of control
Again

git push

I did, but

 Delta compression using up to 6 threads.
Compressing objects: 100% (437/437), done.
Writing objects: 100% (445/445), 221.08 MiB | 7.39 MiB/s, done.
Total 445(delta3), reused0(delta0)
remote:Resolving delta: 100% (3/3), done.
remote:error:GH001:Large files detected.You may want to try Git Large File Storage -https://git-lfs.github.com.
remote:error:Trace:46e6e6146393dfce0c018b2491623426
remote:error:See http://git.io/iEPt8g for more information.
remote:error:File SRCNN-pytorch/BLAH_BLAH/91-image_x3.h5 is 181.82 MB; this exceeds GitHub's file size limit of 100.00 MB
remote:error:File SRCNN-pytorch/BLAH_BLAH/91-image_x4.h5 is 180.89 MB; this exceeds GitHub's file size limit of 100.00 MB
To https://github.com/Hika-Kondo/Super_Resolution.git
 ! [remote rejected] master->master (pre-receive hook decremented)
error: failed to push some refs to 'https://github.com/***/Super_Resolution.git'

That's it.
In this case, how should I push it?

git github

2022-09-30 15:54

2 Answers

  • The error occurred in the SRCNN-pytorch/BLAH_BLAH/91-image_x* below the current directory.
    On the other hand, the /SRCNN-pytorch/BLAH_BLAH path you specified in gitrm is the absolute path below the root directory and they are different.Didn't you get another error when you ran the command?

  • gitrm specifies the default filename.Because you specified the directory,
    For example, gitrm SRCNN-pytorch/BLAH_BLAH/*.

The error occurred in the SRCNN-pytorch/BLAH_BLAH/91-image_x* below the current directory.
On the other hand, the /SRCNN-pytorch/BLAH_BLAH path you specified in gitrm is the absolute path below the root directory and they are different.Didn't you get another error when you ran the command?

gitrm specifies the default filename.Because you specified the directory,
For example, gitrm SRCNN-pytorch/BLAH_BLAH/*.


2022-09-30 15:54

As you can see in the error message, one file is rejected because it is over 100 megabytes in size.
If you sign up for a fee and set up git lfs, it's okay.

I reflected on myself that it was hard to understand, so I added it

github provides a specific description.

When you try to push a file to Git, you receive an error stating, "This exceeds the file size limit of 100 MB for Git LFS."

Hasn't the file in question already been commit in the past?
Therefore, it is too late to delete the file you want to commit in --chace.


To go back to the commit of git and delete the file(s) Rewrite History
The fundamental solution is to do .

It's a bit complicated, so try to do it with the meaning of studying.

If the number of commits is still small, give up the past history and
Another option is to commit without a large file.

Limiting github disk space

The github limits the size per file that can be sent per day.
In Billing for accounts

Also, there is a git lfs detailed instructions page, so
Please give it a try.
This is also a historical rewrite of previously committed large files
The procedure is to track the file again for git lfs.

There is a limit to the amount of push per day, so you can also use the technique (?) of pushing for one month and then returning to the free contract.


2022-09-30 15:54

If you have any answers or tips


© 2024 OneMinuteCode. All rights reserved.