500 error when the filename is on two lines

I get a 500 error when my file name is on two lines. I know I shouldn't have my filename on two lines. However, it was a typo when renaming the file in sublime and it introduced a newline character which broke GitLab at some point. The commit goes through. However, when I try to view it, I get a 500 page. Here is the error_log:

"ActionView::Template::Error (No route matches {:action=>"diff", :controller=>"projects/blob", :format=>nil, :id=>"af069e838b994300aa70b5c252594767ca16c169/pages/Portrait Beauty Akt\nportrait_beauty_akt.yml", :namespace_id=>#<Namespace id: 7, name: "", path: "", owner_id: 6, created_at: "2015-03-09 15:07:34", updated_at: "2015-03-09 15:07:34", type: nil, description: "", avatar: nil>, :project_id=>#<Project id: 55, name: "", path: "", description: "", created_at: "2015-03-18 19:49:45", updated_at: "2015-06-02 16:53:05", creator_id: 6, issues_enabled: true, wall_enabled: false, merge_requests_enabled: true, wiki_enabled: true, namespace_id: 7, issues_tracker: "gitlab", issues_tracker_id: nil, snippets_enabled: false, last_activity_at: "2015-06-02 16:53:05", import_url: "", visibility_level: 10, archived: false, import_status: "none", repository_size: 9.59, star_count: 0, import_type: nil, import_source: nil, avatar: nil>} missing required keys: [:id]):"

What version of GitLab are you running? This seems to work fine in GitLab v7.11.4.

Thanks for your reply. We are actually on the same version. v7.11.4.

That's odd. This is what I see when I view a file with newlines:

Are you using another Web server in front of GitLab?

We're running gitlab in a docker container on CoreOS based on the following image: https://github.com/sameersbn/docker-gitlab

What is the URL that you see in your browser when you get that error?

http://10.0.20.24:10080/maahd/david-static-landing-pages-parallax/commit/af069e838b994300aa70b5c252594767ca16c169

That's very odd. I looked at the Rails routing constraints, and the newline should be allowed. Can you push this filename to a repository on GitLab.com to see if we can reproduce the issue there?

It's been at least 2 weeks (and a new release) since we heard from you. I'm closing this issue but if you still experience this problem, please open a new issue (but also reference the old issue(s)). Make sure to also include the necessary debugging information conforming to the issue tracker guidelines found in our contributing guidelines.

Status changed to closed

mentioned in merge request !14785