From: Mingun <alexander_sergey@mail.ru>
To: sergiodj@sergiodj.net
Cc: git@vger.kernel.org, newren@gmail.com, pclouds@gmail.com,
peff@peff.net, phillip.wood123@gmail.com,
phillip.wood@dunelm.org.uk, Mingun <alexander_sergey@mail.ru>
Subject: Re: Possible race condition with git-rebase + .git/index.lock - probably a gettext issue
Date: Fri, 28 Oct 2022 21:04:51 +0500 [thread overview]
Message-ID: <20221028160451.2040-1-alexander_sergey@mail.ru> (raw)
In-Reply-To: <87lg1i4h6g.fsf@sergiodj.net>
---
It seems that this bug is related to localization library, similar to this diesel issue: https://github.com/diesel-rs/diesel/discussions/2947#discussioncomment-2025857.
Also, this bug is highly depend on the free space capacity on a drive where working copy is located. I encounter this bug each time when my ssd is nearly full (about 6 GB of free space on 120 GB drive).
About 90% of time, when I try to use `git svn rebase` in such conditions, the operation failed:
```
$ git svn rebase
warning: пропущен уже применённый коммит ef0998895a6
warning: пропущен уже применённый коммит d1dbbd6ef8b
подсказка: use --reapply-cherry-picks to include skipped commits
подсказка: Disable this message with "git config advice.skippedCherryPicks false"
fatal: Не удалось создать «/path/to/my/git/repo/.git/index.lock»: Файл существует.
Похоже, что другой процесс git запущен в этом репозитории,
например редактор открыт из «git commit». Пожалуйста, убедитесь,
что все процессы были завершены и потом попробуйте снова.
Если это не поможет, то возможно процесс git был ранее завершен
с ошибкой в этом репозитории:
удалите файл вручную для продолжения.
rebase refs/remotes/origin/trunk: command returned error: 128
Ветка push удалена (была 5c2212d372e).
$ git rebase --continue
fatal: не удалось прочитать файл журнала «.git/rebase-merge/message»: Нет такого файла или каталога
```
At the same time, when after I free space on my drive or set "C" locale, the operation is completed from first attempt.
I hope this will help to localize and fix the issue.
prev parent reply other threads:[~2022-10-28 17:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 21:38 Possible race condition with git-rebase + .git/index.lock Sergio Durigan Junior
2019-03-11 22:50 ` Eric Sunshine
2019-03-11 22:53 ` Sergio Durigan Junior
2019-03-12 10:28 ` Duy Nguyen
2019-03-12 16:45 ` Sergio Durigan Junior
2019-03-12 19:23 ` Elijah Newren
2019-03-12 19:32 ` Sergio Durigan Junior
2019-03-12 19:39 ` Elijah Newren
2019-03-12 19:58 ` Sergio Durigan Junior
2019-03-13 20:40 ` Phillip Wood
2019-03-13 20:48 ` Sergio Durigan Junior
2019-03-13 20:59 ` Jeff King
2019-03-13 21:07 ` Sergio Durigan Junior
2022-10-28 16:04 ` Mingun [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221028160451.2040-1-alexander_sergey@mail.ru \
--to=alexander_sergey@mail.ru \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=phillip.wood123@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=sergiodj@sergiodj.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).