Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #3781

Closed
Open
Created 12 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

Cannot view file source for some projects

Closed

Cannot view file source for some projects

Created by: hannes-brt

After I upgraded to 5.1 from 5.0, I cannot view the source of any files in some of my projects (i.e. some projects work fine, but for those ones that have problems I can't view any files).

If the source view fails, I can only see the header, filepath and filename. In production.log I get the following:

Started GET "/hannes/neural_nets/blob/master/neural_nets/cluster_train.py?_=1367294660779" for 128.100.241.58 at 2013-04-30 00:04:20 -0400
Processing by BlobController#show as JS
Parameters: {"_"=>"1367294660779", "project_id"=>"hannes/neural_nets", "id"=>"master/neural_nets/cluster_train.py"}
Rendered errors/not_found.html.haml within layouts/errors (0.1ms)
Rendered layouts/_head.html.haml (1.2ms)
Rendered layouts/_search.html.haml (37.5ms)
Rendered layouts/_init_auto_complete.html.haml (5.0ms)
Rendered layouts/_head_panel.html.haml (46.0ms)
Rendered layouts/_flash.html.haml (0.1ms)
Filter chain halted as :assign_ref_vars rendered or redirected
Completed 404 Not Found in 60ms (Views: 48.2ms | ActiveRecord: 0.9ms)
Started GET "/admin/logs" for 128.100.241.58 at 2013-04-30 00:05:27 -0400
Processing by Admin::LogsController#show as HTML

As far as I can see, it is older repositories that fail, while new ones work fine. I have upgraded my installation with every release from 3.x (don't remember the exact version I originally installed) through 5.1.

Linked issues
...

    Related merge requests

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: hannes-brt

      So I figured out that I had the same issue as #3666 and that when I revert b1a8fdd8, everything suddenly works fine.

      This bug broke my Gitlab for several days and what actually shocks me a little is that this commit was allowed into 5-1-stable even though several people pointed out specifically that it breaks the app, but @randx overruled them and insisted it was correct.

      I love Gitlab dearly and I am extremely thankful for the head developers to give us this wonderful piece of software, but I have to note that 5.1 update was anything but smooth.

      By Administrator on 2013-05-01T00:21:57 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: podenski

      Updating to git 1.8.2.2 totally solved this problem. Built it from source:

      <https://git-core.googlecode.com/files/git-1.8.2.2.tar.gz>
      
      <http://icnerd.com/2013/02/25/install-git-source-centos-6/>

      By Administrator on 2013-05-19T18:12:39 (imported from GitLab project)

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    0 Assignees
    Assign to
    Milestone
    No milestone
    None
    None
    Time tracking
    Due date
    None
    None
    0
    Labels
    None
    Assign labels
    • No matching results
    • Manage project labels
    Confidentiality
    Not confidential

    You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

    Lock issue
    Unlocked
    participants
    Reference: