Error unable to index file git

Dhananjay Kumar

Unable to index file: Permission Denied error in git add command

While working on an application, I had to commit changes to local Git Repository. It was usual task and I started with following command,

To surprise git add command gave me error as shown in image below. Error message was clear that to a particular file there was Permission denied.

Note: I was working on a MVC application which had local database attached. Name of database was MoviesRTM.mdf.

I tried to commit using Visual Studio 2013 as well. Here also I got same error as shown in image below,

This can be solved by two ways either shutting down IIS Express or restarting Visual Studio. I was using IIS Express to host MVC application. You can shut down IIS Express by right click on IIS Express and click on Exit from context menu.

If this option is not working then try restarting Visual Studio.

Note: Restarting Visual Studio or Shutting down IIS Express may worked in this scenario because permission denies error was on a database file (extension mdf). And database was locally created.

After shutting down I was able to run git add command successfully.

Источник

Unable to commit changes — Temp/Unitylockfile error #1039

Prerequisites

• Be sure to run with tracing enabled to capture runtime details in the log file
• Include the log file in the PR.
  • On Windows, the extension log file is at %LOCALAPPDATA%GitHubUnitygithub-unity.log
  • On macOS, the extension log file is at

  /Library/Logs/GitHubUnity/github-unity.log
  On linux, the extension log file is at

  Description

  Unable to commit changes.

  Steps to Reproduce

  1. Select files to commit and add description
  2. click commit

  Expected behavior:
  I expect the changes to be commited

  Actual behavior:
  After processing, the list of files under changes does not change and nothing is actually commited.

  Reproduces how often:
  100%

  Additional Information

  Any additional information, configuration or data that might be necessary to reproduce the issue.

  The text was updated successfully, but these errors were encountered:

  This file is not locked by any external process, so it looks like Github Unity is getting in its own way (unless this is a standard Unity file?)

  This is a standard Unity file, I don’t know why you’re getting this error, as the Temp folder should not be getting scanned, but I can’t tell what’s really going on without the full log :/

  @jwvanderbeck If you’re still around, let me know!

  Find Temp/UnityLockfile in the changed files on the left in Github Desktop.
  Right-click -> ignore file

  For anyone else having this problem, my solution was to change my .gitignore file to have a wild card before all the unity folders. My git directory was one folder above my unity project(so like «Gitfolder/UnityProject/Temp»), and as it looks like the .gitignore was expecting to be at the same level as the Temp folder(and other folders) it was not excluding the folders. Not sure if this will break anything, if not I would suggest GitHub change their default unity ignore file.

  Uhm, also does someone know how to post their gitignore file? I tried code, which as you can see bellow didn’t work out well.

  `# This .gitignore file should be placed at the root of your Unity project directory

  TextMesh Pro files

  Autogenerated Jetbrains Rider plugin

  Visual Studio cache directory

  Gradle cache directory

  Autogenerated VS/MD/Consulo solution and project files

  *ExportedObj/
  .consulo/
  *.csproj
  *.unityproj
  *.sln
  *.suo
  *.tmp
  *.user
  *.userprefs
  *.pidb
  *.booproj
  *.svd
  *.pdb
  *.mdb
  *.opendb
  *.VC.db

  *.pidb.meta
  *.pdb.meta
  *.mdb.meta

  Unity3D generated file on crash reports

  Builds

  Crashlytics generated file

  @78Star If you’ll note the comment at the very top of the file, it is intended to be placed in the root of your Unity project. If you choose to put it somewhere else then yeah it won’r work right an you will need to adjust accordingly. That isn’t GitHub’s responsibility really.

  Hello.
  I solved this problem with the instruction:
  echo «Temp/*» >> .gitignore

  For me, closing Unity just to add the objects and commit worked.

  For me, closing Unity just to add the objects and commit worked.

  Yes, this worked for me too 🙂

  @vicentselfa HI, i know temp file are unnecessary but did it cause any unpredictable errors?

  Don’t forget to change the .gitignore in the repository folder:

  It should have something like this:
  /[Ll]ibrary/
  /[Tt]emp/
  /[Oo]bj/
  /[Bb]uild/
  /[Bb]uilds/
  /[Ll]ogs/
  /[Mm]emoryCaptures/

  Remove the first slashes:
  [Ll]ibrary/
  [Tt]emp/
  [Oo]bj/
  [Bb]uild/
  [Bb]uilds/
  [Ll]ogs/
  [Mm]emoryCaptures/

  For anyone else having this problem, my solution was to change my .gitignore file to have a wild card before all the unity folders. My git directory was one folder above my unity project(so like «Gitfolder/UnityProject/Temp»), and as it looks like the .gitignore was expecting to be at the same level as the Temp folder(and other folders) it was not excluding the folders. Not sure if this will break anything, if not I would suggest GitHub change their default unity ignore file.

  Uhm, also does someone know how to post their gitignore file? I tried code, which as you can see bellow didn’t work out well.

  `# This .gitignore file should be placed at the root of your Unity project directory

  @78Star Alexander. I’m liking your explanation of the issue. but I’m way confused by the labeling of the /[Aa]ssets/TextMeshPro/ The rest of the folders in your code have */[Ff]older name , but not the Assets stuff. Huh? Is that intentional or just a miss? This doesn’t make sense to me. thanks,

  Источник

  Git: невозможно индексировать файл – разрешено отклонение

  Только для одного файла возникает следующая ошибка:

  Я проверил свои разрешения на соответствующий файл, .git каталог объектов и .git. Я могу добавить любые другие файлы, кроме этого. Я мог бы stat/r/w/touch файл, и прикосновение не помогло. Разрешения верны.

  Это какая-то сумасшедшая ошибка?

  Глядя на исходный код Git ( sha1_file.c , function move_temp_to_file() ), похоже, что Git не может переименовать временный файл с именем /opt/www/.git/objects/3f/tmp_obj_XXXXXX (где XXXXXX – шесть случайных символов) до /opt/www/.git/objects/3f/ce3587c54a8be14c69b08c6b01f94949b11b47 . Это может произойти, если у вас нет разрешения на удаление файлов в /opt/www/.git/objects/3f .

  Некоторые вещи, которые нужно попробовать:

  • Если несколько пользователей обращаются к репозиторию Git, вам может потребоваться выполнить что-то вроде git config core.sharedRepository 0664 (подробнее см. git help config ), чтобы убедиться, что вновь созданные каталоги и файлы имеют соответствующие разрешения для всех пользователей репозитория.
  • Попробуйте запустить rm -f /opt/www/.git/objects/3f/tmp_obj_* и убедитесь, что проблема устранена.

  Посмотрите, можете ли вы воспроизвести проблему за пределами Git, выполнив следующие действия:

  Обязательно запустите указанные выше команды тем же пользователем, у кого возникла ошибка.

• Попробуйте рекурсивно chown ing и chmod в каталоге объектов.

Если вы используете Visual Studio или что-то подобное, генерирующее файл mdf, просто закройте VS и повторите команду git снова. На этот раз это должно сработать.

Чтобы сохранить закрытие и повторное открытие, вы должны добавить ссылки в файл .gitignore в корне проекта. Например, если это база данных, вызывающая проблему, добавьте следующее:

У вас нет разрешения на запись в /opt/www/.git/objects/3f .

Самое быстрое решение – использовать команду sudo для выполнения вашей команды с правами root.

Решил это для меня.

Что-то пошло не так в вашем git-репозитории, вероятно, из-за того, что внешний процесс создал файл или каталог, принадлежащий другому пользователю, а не текущему.

Эта ошибка часто встречается при использовании Docker, а служба в вашем файле docker-compose.yml имеет локально смонтированный том, который был создан с использованием пользователя, отличного от пользователя локального компьютера.

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

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

Безусловно, самое быстрое решение – выполнить следующее из корневого каталога проекта, в котором находится ваш git-репозиторий:

Чтобы проверить, что все исправлено, выполните следующее:

Быстро с последующим выполнением:

Вы увидите, что все было добавлено в репозиторий git без необходимости что-либо тестировать/возиться.

Просто закройте Visual Studio (или Unity) и попробуйте добавить эти файлы снова.

У меня была эта проблема в моем репозитории с исходным кодом, когда права были root: git 770, по-видимому, мне пришлось изменить его на 771, даже если мой пользователь находится в группе git. Я подозреваю, что, возможно, git, возможно, либо не знает ACL, либо не совместим со вторичными группами, так как в этом случае группа Git была одной из моих вторичных групп.

Источник

6 Common Git Errors and How to Avoid Them

Exploring some of the most common errors in Git

A Version Control System (VCS) is an essential tool for almost any development team that needs to keep track of the changes in the source code.

Git has been developed back in 2005 and today is by far the most commonly used VCS that is used by almost all development teams that require to version and archive their source code. In today’s article, we are going to cover a few of the most common Git errors and discuss how you can potentially avoid or fix them.

fatal: not a git repository (or any of the parent directories)

This is one of the most common errors, especially for newcomers to Git. Let’s suppose that you want to run git status in a particular directory:

The error indicates that the command cannot be executed because the current directory is not a Git directory. Usually, there are two main reasons why you might be getting the error.

• You either forgot to initialize the repository as a Git repository using git init
• or you are probably in the wrong directory. You can check your current work directory using pwd . It’s quite common for people to forget to change the directory when cloning a Git repository.

Another very common error after git pull or git merge is the one shown below:

This usually can happen mainly for two reasons;

• The .git directory got corrupted. This hidden directory contains information relevant to your project that is being version controlled (for example, information about commits, remote repositories, etc.). If the directory is corrupted, git is unaware of the local history and thus the error will be reported when trying to push or pull to/from a remote repository.
• You are trying to pull from a remote repository that already has commits while you have also created a new repository locally and added commits as well. In this case, the error will be reported since Git is unaware of how these two are related (they are pretty much interpreted as two distinct projects).

If this is the case, then you need to provide the —allow-unrelated-histories flag. For example,

There’s also a chance of getting this error when trying to rebase and requires different treatment.

The process of combining commits to a new base commit is called rebasing. In other words, rebasing simply changes the base of the branch to a different commit so that it appears as if you have created the branch from that particular commit. The diagram below illustrates accurately the way rebasing works in Git.

When git rebase fails with this error rebase does not get aborted but is still in progress. Instead, you can actually intervene manually.

To solve the issue you first need to merge and commit , and finally force rebase to continue:

xcrun: error: invalid active developer path

This is a common error for OSX users that is even more frequent when a new major OSX release is made. The error is reported when you attempt to run any git command. For example,

The issue is related to Xcode Command Line Tools version that needs to be updated so that the error is resolved. To do so, open the terminal and run

The response should be

while a pop-up window will appear on your screen asking you to confirm that you want to install command line developer tools.

Simply click install, wait for the installation to complete and open a new terminal session. Git commands should now work as expected.

fatal: Unable to create ‘.git/index.lock’: File exists

When a git process crashes in one of your Git repositories you may see the error shown below when you attempt to run a git command:

If no other git process is running, you can quickly fix this by manually removing the file:

error: pathspec did not match any file(s) known to git

Usually, when you create a new branch using say the web UI of GitHub and go back to your local terminal to checkout to the branch using

you may get this error

This usually means that your local repository is not up to date with the latest information for the remote Git repository. To fix the issue you simply need to fetch the information for the newly created branch:

Now git checkout should work fine.

permission denied (publickey)

In order to clone remote repositories to your local machine you need to ensure that you have properly configured authentication.

If you attempt to clone a repo and the response is

Now there are potentially a couple of ways to resolve this issue. The easiest way is probably to instead use HTTPS to clone the repository to your local machine that requires no public key validation:

Alternatively, if you still need to use SSH to clone the repository you’ll have to generate SSH public and private keys in order to configure proper authentication. To do so, make sure to follow the steps below.

• Navigate to your local .ssh directory and run ssh-keygen to generate keys

• Now you need to copy the content of the generated file id_rsa.pub

• Add the key to the appropriate section on GitHub website
• Make sure your git configuration is correct

And you should now be able to clone the remote repository using SSH. For more details, you may refer to GitHub documentation.

Final Thoughts

In today’s article, we explored a few of the most common errors in Git. For each of them, we discussed potential reasons that may be triggering these errors as well as how to fix them.

Git is definitely a very powerful tool and is way more complicated than it may sometimes look like. The community is great though and the Internet is full of resources to help you resolve any issue you may be having with Git.

Источник

Вопрос:

error: unable to write sha1 filename /opt/www/.git/objects/3f/ce3587c54a8be14c69b08c6b01f94949b11b47: Permission denied

error: wp/wp-admin/css/theme-install.dev.css: failed to insert into database
fatal: unable to index file wp/wp-admin/css/theme-install.dev.css

Лучший ответ:

Ответ №1

# SQL Server files
*.mdf
*.ldf

Ответ №2

Ответ №3

sudo chown -R ${USER}:${USER} .

sudo chown -R ${USER}:${USER} .git/objects

git add .

git status

Ответ №4

Просто закройте Visual Studio (или Unity) и попробуйте добавить эти файлы снова.

Ответ №5

У меня была эта проблема в моем репозитории с исходным кодом, когда права были root: git 770, по-видимому, мне пришлось изменить его на 771, даже если мой пользователь находится в группе git. Я подозреваю, что, возможно, git, возможно, либо не знает ACL, либо не совместим со вторичными группами, так как в этом случае группа Git была одной из моих вторичных групп.

26 Answers

rm -f ./.git/index.lock

The previous cherry-pick is now empty, possibly due to conflict resolution.
If you wish to commit it anyway, use:

    git commit --allow-empty