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
  • #8732

Closed
Open
Created Feb 04, 2015 by Administrator@rootOwner

Update from 6.0 to 7.7, showing old merge requests cause 500 errors

Created by: coconut30

Hi,

After an update of my gitlab from 6.0 to 7.7 following the doc https://github.com/gitlabhq/gitlabhq/blob/master/doc/update/6.x-or-7.x-to-7.7.md, when I try to view existing merge requests, gitlab fail to display with a 500 error. In production.log I can see that :

Started GET "/namespace/project/merge_requests" for 127.0.0.1 at 2015-02-03 16:34:13 +0100 Processing by Projects::MergeRequestsController#index as HTML Parameters: {"project_id"=>"namespace/project"} Completed 500 Internal Server Error in 56ms

ActionView::Template::Error (Invalid raw commit type: Commit): 22: - if merge_request.notes.any? 23: %span 24: %i.fa.fa-comments 25: = merge_request.mr_and_commit_notes.count 26: - if merge_request.milestone_id? 27: %span 28: %i.fa.fa-clock-o app/models/merge_request_diff.rb:68:in new' app/models/merge_request_diff.rb:68:inblock in load_commits' app/models/merge_request_diff.rb:68:in map' app/models/merge_request_diff.rb:68:inload_commits' app/models/merge_request_diff.rb:50:in commits' app/models/merge_request.rb:39:incommits' app/models/merge_request.rb:204:in mr_and_commit_notes' app/views/projects/merge_requests/_merge_request.html.haml:25:in_app_views_projects_merge_requests__merge_request_html_haml___4251378593434022744_59353120' app/views/projects/merge_requests/index.html.haml:8:in `_app_views_projects_merge_requests_index_html_haml__336017911220533031_25376180'

No problem with new merge requests. If you need more info, I will be happy to post it. Thanks

Assignee
Assign to
Time tracking