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

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

  • Report abuse

  • New issue

  • Report abuse

500 error when creating merge request with 5.1: NoMethodError (undefined method `to_hash' for "--broken-diff":String)

Closed

500 error when creating merge request with 5.1: NoMethodError (undefined method `to_hash' for "--broken-diff":String)

Created by: dan-blanchard

When trying to create a merge in Gitlab 5.1, we get a 500 error and see the following error message in production.log:

NoMethodError (undefined method `to_hash' for "--broken-diff":String):
app/models/merge_request.rb:217:in `map'
app/models/merge_request.rb:217:in `dump_diffs'
app/models/merge_request.rb:115:in `reloaded_diffs'
app/models/merge_request.rb:98:in `reload_code'
app/controllers/merge_requests_controller.rb:54:in `create'

The merge request can then subsequently be viewed, but the diff tab is blank (which I'd imagine is what the "--broken-diff" part is about).

Linked issues
...

    Related merge requests

    • 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
    1
    Labels
    Crashes - 500 errors
    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: