Issue #95 resolved

failed to display commits of imported hg repo

Sven Ginka
created an issue

something seems to be strange when displaying imported hg repos. there is no display of commits and there is also no source-view available. strangely when creating a repo with scm-manager everything is fine.

any idea? can i supply more information?

Comments (20)

  1. Sven Ginka reporter

    I used this version

    © SCM Manager 1.13-SNAPSHOT
    

    (1) yes, there are special chars in the first 20 commits

    (2) it seems this is the right path because I found this here

    UnicodeDecodeError: 'ascii' codec can't decode byte 0xfc in position 14: ordinal not in range(128)
    

    The whole logfile is attached.

  2. Sebastian Sebastian repo owner

    Which os you are using?

    I've read a lot about python, encoding and unicode and it seems to be a little complicated. It looks like that python 2.x use ascii encoding for strings by default. I think we have to force UTF-8 as default encoding for python. Could you create a sitecustomize.py with the following content:

    import sys
    sys.setdefaultencoding('utf-8')
    

    Put the path to the folder containing that file to your python path, by editing the 'Python Module Search Path' at Config->Repository Types->Mercurial.

    Source: http://www.pycs.net/users/0000323/stories/14.html

  3. Sven Ginka reporter

    beginning with version "http://download.scm-manager.org/issues/95/scm-server-app-2012020901.zip" I noticed and error when starting the application

    2012-02-10 10:23:16.788:INFO:oejs.Server:jetty-7.6.0.v20120127
    2012-02-10 10:23:22.731:INFO:oejw.WebInfConfiguration:Extract jar:file:/C:/Users
    /ginka/Desktop/scm-server-app-2012020901/scm-server/var/webapp/scm-webapp.war!/
    to C:\TMP\jetty-0.0.0.0-8080-scm-webapp.war-_scm-any-\webapp
    2012-02-10 10:23:42.442:INFO:oejw.StandardDescriptorProcessor:NO JSP Support for
     /scm, did not find org.apache.jasper.servlet.JspServlet
    10:23:44.584 [main] INFO  sonia.scm.boot.BootstrapListener - start scm-manager i
    n stage: PRODUCTION
    

    what does this mean. has it anything to do with our problem here?

    I also can't browse the source any more. newly created repos are empty. however if pushed one changeset (without special chars) the repo is not browsable anymore, although its commits are viewable.

    I got comment 4 running!

    here is the result

    UnicodeDecodeError: 'utf8' codec can't decode bytes in position 14-19: unsupported Unicode code range
    
  4. Sven Ginka reporter

    Success! I got the "scm-server-app-2012020901" running with the comment 4.

    using Python/Lib/site-packages/sitecustomize.py

    import sys
    sys.setdefaultencoding('latin-1')
    

    it is definetly not running with (retried it twice)

    import sys
    sys.setdefaultencoding('utf-8')
    

    "scm-server-app-2012020902" is not running with both of them.

  5. Sebastian Sebastian repo owner

    Ok, i've installed a windows in a virtualbox to reproduce the error. I could reproduce the error by creating a commit with german umlaut in the description. And the good news, i think i can fix the error. I've forced all encoding's to utf-8 and i think this will fix the problem. I will provide a new test version in the next few hours.

  6. x y

    It is not resolved or reoccuring in our 1.34 version :-( I cannot see commits (505 error), browse the repo nor rebuild statistics.

    10:13:17.944 [qtp1891737766-18] ERROR sonia.scm.activity.collector.AbstractChangesetCollector - could retrieve changesets for repository ...ö...
    

    In the GUI it also displays some "ö" instead of an "ö".

    The .scm/config/repositories.xml name entry contains some "ö" (even changed it to ö, which is the same, did not fix it).

    On the console I can access the path properly and all other repos are fine as well.

    Thx Andreas :-)

    edit: created new bug for it: https://bitbucket.org/sdorra/scm-manager/issue/559/reoccuring-problem-with-umlauts-in-path-95

  7. x y

    sorry ... I just figured out it works due to two problems on my side ... created parallel process as another user (which could not open ports) and had the ö still in place which caused the server start to just hang up without any log message why.

  8. Log in to comment