Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#2 Missing data on some branches

pending
nobody
None
5
2012-10-09
2012-10-03
Scott
No

Sorry I posted this in the forums looking for help:

Some branches (ie master) appear to be quite functional. However, if we go to the index we see the majority of branches have their last change as "1970-01-01", and browsing into these shows no details (commits, messages, authors, anything). The Branches look fine in a Git client so can't work out what's going wrong here. Any help would be appreciated.

Discussion

  • You could try enabling some debug options:

    $conf['debug'] = true;
    $conf['debug_command_trace'] = true;

    Then see if you can run all of the commands on a problematic page manually.

    If after that you can't figure the problem out:
    - is the repository public? Can you provide me the URL?
    - Or can you reproduce the issues by creating a dummy git repository with similar structure?

     
    • status: open --> pending
     
  • Scott
    Scott
    2012-10-10

    Thanks for the reply, I'll try the debug.

    Its located on an internal server so can't grant you access unfortunately. It looks like all the branches migrated from SVN are OK and the problem affects only some of the branches created since the migration.

    We'll see what the debug comes up with.

    Thanks

     
  • Scott
    Scott
    2012-10-10

    Interestingly the affected branches exit with a code 128 - viewgit/inc/functions.php:555 [1]$ git --git-dir='/var/www/vhosts/code.avaaz.org/branches/2676/.git' rev-list --header --max-count=1 HEAD [exit 128] [1024]

    Unaffected branches look like this - viewgit/inc/functions.php:555 [2]$ git --git-dir='/var/www/vhosts/code.avaaz.org/branches/3001/.git' rev-list --header --max-count=1 HEAD [exit 0] [1024]

    I'm a bit of a noob when it comes to php so have no idea where that leads me.....

     
  • You ahould run the failing command manually, as the same user your web server is running under.

    These issues are typically plain unix permission problems or git repository issues.