Gitlab произошла ошибка при получении содержимого папки

По умолчанию вы не можете отправлять изменения в извлеченную ветвь репозитория. Обычно это вызывает большие проблемы! Вот что обычно происходит:

$ git push герой мастер
...Сообщения об ошибках...
к героку
 ! [удаленный отказ] master -> master (ветвь в настоящее время проверена) ошибка: не удалось отправить некоторые ссылки на 'героку'

Поскольку вы ничего не упомянули Сообщения об ошибках, я предполагаю, что вы добавили следующее в свой heroku конфигурация репозитория, или вы используете довольно старую версию Git:

[получить] denyCurrentBranch = false

Похоже, вы хотите проверить свежую копию основной ветки всякий раз, когда вы отправляете новую версию на свой heroku репозиторий. Этого можно добиться с помощью хука post-receive. Создайте файл в своем heroku хранилище .git/hooks/post-receive, и дать это +x разрешения.

#!/bin/sh
while read oldrev newrev refname
do
    if test "$refname" = refs/heads/master
    then
        ( cd ..; GIT_DIR=.git; git reset --hard )
    fi
done

Теперь всякий раз, когда вы нажимаете новый master филиал в heroku, хук запустится и проверит новую ветку. Есть лучшие способы сделать такие вещи, но это просто.

Резюме: По умолчанию, когда вы отправляете изменения, изменяется только история но не рабочее дерево. Предполагается, что кто-то может работать с этим деревом, поэтому любые действия с ним могут быть разрушительными.

Sometimes when you do a git push, you might get the following permission error message.

This error typically happens when multiple users are working on a particular git repository.

The following git push error indicates that it doesn’t have enough permission for adding a new object to the ./objects directory under your repository.

Apart from the obvious permission issue, there is also another underlying problem that needs to be addressed, which is explained in this tutorial.

$ git push
counting objects: 6, done.
Delta compression using upto 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 388 bytes, | 0 bytes/s, done.
Total: 4 (delta 1), reused 0 (delta 0)

error: insufficient permission for adding an object to repository database ./objects
fatal: failed to write object
error: unpack failed: unpack-objects abnormal exit
 ! [remote rejected] master -> master (n/a (unpacker error))
error: failed to push some refs to john@192.168.100.1:/home/git/myproj

It also shows that the git unpack failed with unpack-objects abnormal exit. Because of this error, it failed to push some refs as shown above.

First, cd to the git repository which is having this issue. If you don’t see the objects directory directly under your repository folder, then look under the .git folder as shown below.

[john@devdb]$ cd /home/git/myproj
(or)
[john@devdb]$ cd /home/git/myproj/.git

In this particular case, when john is trying to do ‘git push’, he is getting the above error because some of the directories under the objects folder of git repository are owned by lisa as shown below.

[john@devdb]$ ls -l objects
drwxr-xr-x 2 john  git 4096 Oct  8  2016 01
drwxr-xr-x 2 john  git 4096 Oct  8  2016 02
drwxr-xr-x 2 lisa lisa 4096 Oct  8  2016 03
drwxr-xr-x 2 lisa lisa 4096 May  1  2017 04
drwxr-xr-x 2 john  git 4096 May  1  2017 05
drwxr-xr-x 2 john  git 4096 May  6  2017 06

Set the Appropriate Permissions on Objects Directory

To solve this problem, execute the following, which will set the group to git (or whatever group where all the users belongs to. Also make sure the user and group has read and write permission to the directory.

cd /your/git/repo

chgrp -R git objects

chmod -R g+rws objects

In the above:

• Make sure all your users who need access to git are part of the git group. Change the “git” in the above chgrp command to whatever group where all your developers belong to.
• The “s” option in the “g+rws” is to set the setuid bit on the objects folder. This will make sure any new directory created under objects folder will make the group name from the objects folder which is owned by git group.

You may be tempted to execute the following on your objects directory, which will solve the problem that you are having. But, as you can imagine, it is not a good idea to do 777. Instead execute the above chgrp and chmod command.

chmod -R 777 objects

Share the Git Repository with a Group

But, even after doing the above, the same problem might return again, and you may have to do the above chgrp and chmod whenever the problem occurs.

So, apart from fixing the permission error as explained above, we also need to fix the underlying problem.

In this case, the git repository (for example: myproj) is not setup as shared repository for groups. It might just be a bare repository.

If it is not setup as shared repository, you’ll see the above “insufficient permission on objects directory” issue starts to show-up again.

To verify whether your repository is already setup for group sharing, do the following git config -l option inside your git repository that has the problem.

$ cd /home/git/myproj

$ git config -l
user.name=John Smith
user.email=john@thegeekstuff.com
core.repositoryformatversion=0
core.filemode=true
core.bare=true
core.logallrefupdates=true

In the above output, we don’t see a parameter called “core.sharedrepository”. So, this particular repository (i.e myproj is not setup as shared repository).

The above command displays the configuration values from the “config” file that is located under your git repository.

$ cd /your/git/repo

$ cat config 
[core]
        repositoryformatversion = 0
        filemode = true
        bare = true
        logallrefupdates = true

The above is setup as a bare repository. To convert a bare repository to shared repository, do the following:

git config core.sharedRepository group

Note: In the above command, don’t replace the keyword “group” with your groupname (for example: git). Use the above above command exactly as shown without changing anything. The “group” in the above command should be typed exactly as it is.

Now, if you view the git config as shown below, you’ll see the “core.sharedrepository” parameter set to group.

$ git config -l
user.name=John Smith
user.email=john@thegeekstuff.com
core.repositoryformatversion=0
core.filemode=true
core.bare=true
core.logallrefupdates=true
core.sharedrepository=group

The above will solve the insufficient permission issue permanently.

After you set the sharedrepository, if you view the config file under your git repository, you’ll notice that the value of sharedrepository parameter is set to 2 (which is group) as shown below.

$ cat config 
[core]
        repositoryformatversion = 0
        filemode = true
        bare = true
        sharedrepository = 2
[receive]
        denyNonFastforwards = true

Also, anytime you make a git repository as sharedrepository for group using the above command, it will also set the receive.denyNonFastforwards to true automatically as shown above.

Now I copied a folder into current repo, but I could not add the new folder into the repo. Then I tried using this command(git version 2.26.3):

[dolphin@MiWiFi-R4CM-srv]~/Documents/GitHub/retire% git add zuul-service 
[dolphin@MiWiFi-R4CM-srv]~/Documents/GitHub/retire% git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean

seems did not add success, I tried using this command to force add to the repo:

[dolphin@MiWiFi-R4CM-srv]~/Documents/GitHub/retire% git add --force zuul-service 
[dolphin@MiWiFi-R4CM-srv]~/Documents/GitHub/retire% git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean

still not work. the next I tried to modify the folder zuul-service file, no file change tips when using git status to check. I also check the root folder’s .gitignore and did not find ignore the zuul-service folder. This is my first time to encount this strange problem and I have no clue about this problem. Where is going wrong and what should I do to add the zuul-service folder into current repo? This is the project structure:

this is my .gitignore files content:

# Compiled class file
*.class

# Log file
*.log
log

# BlueJ files
*.ctxt

# Mobile Tools for Java (J2ME)
.mtj.tmp/

# Package Files #
*.jar
*.war
*.nar
*.ear
*.zip
*.tar.gz
*.rar
*.icloud
*.bin
*.lock

.idea

*.tmp

# virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
hs_err_pid*

# dolphin-music
dolphin-music/dolphin-music-api/build/
dolphin-music/dolphin-music-service/build/
dolphin-music/dolphin-music-service/testngOutput
dolphin-music/dolphin-music-service/out

# dolphin-post
dolphin-post/dolphin-post-api/build/
dolphin-post/dolphin-post-service/build/
dolphin-post/dolphin-post-service/testngOutput
dolphin-post/dolphin-post-service/out

dolphin-acientbay/dolphin-acientbay-api/build
dolphin-acientbay/dolphin-acientbay-service/build
dolphin-acientbay/dolphin-acientbay-service/testngOutput
dolphin-acientbay/dolphin-acientbay-service/out

dolphin-common/build/
dolphin-common-biz/build/

dolphin-manage/dolphin-manage-service/out

eureka-service/out/

.gradle

.DS_Store

.gradle/buildOutputCleanup/buildOutputCleanup.lock
.idea/workspace.xml

dolphin-manage/dolphin-manage-service/out

dolphin-template/dolphin-template-service/out

dolphin-acientbay/dolphin-acientbay-service/out

the first time, the folder zuul-service contains a .git dir. then I removed it using this command:git rm -rf .git. now the dir did not contains .git folder.

Now I copied a folder into current repo, but I could not add the new folder into the repo. Then I tried using this command(git version 2.26.3):

[dolphin@MiWiFi-R4CM-srv]~/Documents/GitHub/retire% git add zuul-service 
[dolphin@MiWiFi-R4CM-srv]~/Documents/GitHub/retire% git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean

seems did not add success, I tried using this command to force add to the repo:

[dolphin@MiWiFi-R4CM-srv]~/Documents/GitHub/retire% git add --force zuul-service 
[dolphin@MiWiFi-R4CM-srv]~/Documents/GitHub/retire% git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean

still not work. the next I tried to modify the folder zuul-service file, no file change tips when using git status to check. I also check the root folder’s .gitignore and did not find ignore the zuul-service folder. This is my first time to encount this strange problem and I have no clue about this problem. Where is going wrong and what should I do to add the zuul-service folder into current repo? This is the project structure:

this is my .gitignore files content:

# Compiled class file
*.class

# Log file
*.log
log

# BlueJ files
*.ctxt

# Mobile Tools for Java (J2ME)
.mtj.tmp/

# Package Files #
*.jar
*.war
*.nar
*.ear
*.zip
*.tar.gz
*.rar
*.icloud
*.bin
*.lock

.idea

*.tmp

# virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
hs_err_pid*

# dolphin-music
dolphin-music/dolphin-music-api/build/
dolphin-music/dolphin-music-service/build/
dolphin-music/dolphin-music-service/testngOutput
dolphin-music/dolphin-music-service/out

# dolphin-post
dolphin-post/dolphin-post-api/build/
dolphin-post/dolphin-post-service/build/
dolphin-post/dolphin-post-service/testngOutput
dolphin-post/dolphin-post-service/out

dolphin-acientbay/dolphin-acientbay-api/build
dolphin-acientbay/dolphin-acientbay-service/build
dolphin-acientbay/dolphin-acientbay-service/testngOutput
dolphin-acientbay/dolphin-acientbay-service/out

dolphin-common/build/
dolphin-common-biz/build/

dolphin-manage/dolphin-manage-service/out

eureka-service/out/

.gradle

.DS_Store

.gradle/buildOutputCleanup/buildOutputCleanup.lock
.idea/workspace.xml

dolphin-manage/dolphin-manage-service/out

dolphin-template/dolphin-template-service/out

dolphin-acientbay/dolphin-acientbay-service/out

the first time, the folder zuul-service contains a .git dir. then I removed it using this command:git rm -rf .git. now the dir did not contains .git folder.

После того, как вы добавите какой-нибудь материал… скопируйте их и, после всего этого, нажмите его! BANG!! Начните все проблемы… Как вы заметили, есть некоторые различия в том, как были определены как новые, так и существующие проекты. Если какой-либо другой человек пытается добавить/зафиксировать/нажать те же файлы или содержимое (git сохранить оба как одни и те же объекты), мы столкнемся со следующей ошибкой:

$ git push
Counting objects: 31, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (17/17), done.
Writing objects: 100% (21/21), 2.07 KiB | 0 bytes/s, done.
Total 21 (delta 12), reused 0 (delta 0)
remote: error: insufficient permission for adding an object to repository database ./objects  remote: fatal: failed to write object

Чтобы решить эту проблему, вам нужно иметь в виду систему системных разрешений, поскольку в этом случае вы ограничены ею. Tu лучше поймите проблему, идите в свою папку объектов git (.git/objects). Вероятно, вы увидите что-то подобное:

<your user_name>@<the machine name> objects]$ ls -la
total 200
drwxr-xr-x 25 <your user_name> <group_name> 2048 Feb 10 09:28 .
drwxr-xr-x  3 <his user_name> <group_name> 1024 Feb  3 15:06 ..
drwxr-xr-x  2 <his user_name> <group_name> 1024 Jan 31 13:39 02
drwxr-xr-x  2 <his user_name> <group_name> 1024 Feb  3 13:24 08

* Обратите внимание, что эти разрешения для файлов были предоставлены только для ваших пользователей, никто никогда не сможет его изменить… *

Level       u   g   o
Permission rwx r-x ---
Binary     111 101 000
Octal       7   5   0

РЕШЕНИЕ ПРОБЛЕМЫ

Если у вас есть права суперпользователя, вы можете перейти и изменить все разрешения самостоятельно, используя второй шаг, в любом другом случае вам нужно будет спросить всех пользователей о объектах, созданных с их пользователями, используйте следующую команду, чтобы знать кто они:

$ ls -la | awk '{print $3}' | sort -u 
<your user_name>
<his user_name>

Теперь вам и всем владельцам файлов необходимо будет изменить разрешение этих файлов:

$ chmod -R 774 .

После этого вам нужно будет добавить новое свойство, эквивалентное —shared = group done для нового репозитория, в соответствии с документацией, это сделает репозиторий доступным для группы, выполнив его:

$ git config core.sharedRepository group

https://coderwall.com/p/8b3ksg