Project

General

Profile

Actions

Defect #26843

closed

Commits ignored in large(ish) git repository

Added by Jean-Michel C. about 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
SCM
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

Hi there,
I am investigating a long overdue issue in my setup and at the moment, I think it is a defect in Redmine.

I do have a fairly large repo (though not huge) with 1,500 commits.

About a year ago, the processing commit messages stopped working and new commits stopped appearing in my Redmine (the code is up to date though).

When issuing git log --all --pretty=format:"%cd %cn %s" in the repository (the bare used by Redmine) I do have all the last commits, but they are missing in Redmine.

The repo has 1587 commits, but only 1276 (give or take 1) are known to Redmine.

Environment

Environment:
  Redmine version                3.4.2.stable
  Ruby version                   2.3.4-p301 (2017-03-30) [x86_64-linux-gnu]
  Rails version                  4.2.8
  Environment                    production
  Database adapter               Mysql2
SCM:
  Filesystem                     
Redmine plugins:
  redmine_github_hook            2.2.0

Note: This is not new to 3.4.2, I upgraded today to make sure, but I was on 3.2.6 before that and it was the same.

Actions #1

Updated by Jean-Michel C. about 7 years ago

It is to note that the output of git log --no-color --encoding=UTF-8 --raw --date=iso --pretty=fuller --parents --no-renames --reverse (as guessed from git_adapter.rb) is consistent with the issue -it does not contain all commits).

Actions #2

Updated by Jean-Michel C. about 7 years ago

I cannot guess everything that git_adapter.rb does, but it seems that adding --all to git log would fix the issue (it does in the command line at least)

Actions #3

Updated by Toshi MARUYAMA about 7 years ago

  • Status changed from New to Needs feedback
Actions #4

Updated by Jean-Michel C. about 7 years ago

Hi Toshi,

The rails command did not work but I nulled the field in the DB and it did the trick, thank you very much!

Actions #5

Updated by Toshi MARUYAMA about 7 years ago

  • Status changed from Needs feedback to Closed

Sorry, I did not note you need to change 18 of "Repsotiry.find(18).clear_extra_info_of_changesets" to your repository id.

Anyway, thank you for your feedback.

Actions

Also available in: Atom PDF