Hi,

I am using GitLab 6.5.1. My project has the following hierarchy:

------
examples/
    control/
    memory/
README
-----

When I click on the 'README' file, I get the 500 error. Even when I go into 
the 'control' sub-dir and click on a file there, I get the same 500 error. 
However, when I go to the "Commit" tab and click on a commit, i can see the 
contents of the files that were committed.

Here is what I see in the log file:
 
Started GET 
"/js/examples/blob/a6b1c682c60fbe9170ad4c820505ea553f2361f6/README" for 
127.0.0.1 at 2014-02-13 17:07:53 -0800
Processing by Projects::BlobController#show as HTML
  Parameters: {"project_id"=>"js/verilog-examples", 
"id"=>"a6b1c682c60fbe9170ad4c820505ea553f2361f6/README"}
  Rendered shared/_ref_switcher.html.haml (1.9ms)
  Rendered projects/blob/_actions.html.haml (1.5ms)
  Rendered projects/blob/_text.html.haml (11.4ms)
  Rendered projects/blob/_blob.html.haml (14.5ms)
  Rendered projects/blob/show.html.haml within layouts/projects (16.9ms)
Completed 500 Internal Server Error in 177ms

ActionView::Template::Error (EPIPE):
     9:   .file-content.code
    10:     - unless blob.empty?
    11:       %div{class: user_color_scheme_class}
    12:         = raw blob.colorize(formatter: :gitlab)
    13:     - else
    14:       %p.nothing_here_message Empty file
  app/views/projects/blob/_text.html.haml:12:in 
`_app_views_projects_blob__text_html_haml__459456715517612597_23798774510980'
  app/views/projects/blob/_blob.html.haml:27:in 
`_app_views_projects_blob__blob_html_haml__2186621586649798360_23798748355560'
  app/views/projects/blob/show.html.haml:4:in 
`_app_views_projects_blob_show_html_haml__4163958741292105041_23798748031060'
  app/controllers/application_controller.rb:57:in 
`set_current_user_for_thread'
-------

Any suggestions?


-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to