tortoisehg 4.5.2 graph view is broken

Issue #5057 new
Anonymous created an issue

all templates in mercurial\templates have missing file graphentry.tmpl; json template have missing graph.tmpl;

issues was resolved by copying missing files from source code distribution into templates folders

installers need to be fixed. it might be long standing issue as similar defect was observed in 4.1.1

Comments (4)

  1. MORISSEAU Vincent

    Hi,

    I have the same issue. Can't access the graph view on the hg web server.

    Below is the error in the server log when trying to access graph page of a repository on the web interface. Tortoise HG v4.5.2, windows installer.

    127.0.0.1 - - [27/Mar/2018 09:16:42] Exception happened during processing request '/graph/tip':
    Traceback (most recent call last):
      File "mercurial\hgweb\server.pyo", line 101, in do_POST
      File "mercurial\hgweb\server.pyo", line 94, in do_write
      File "mercurial\hgweb\server.pyo", line 173, in do_hgweb
      File "mercurial\hgweb\hgweb_mod.pyo", line 318, in run_wsgi
      File "mercurial\hgweb\hgweb_mod.pyo", line 446, in _runwsgi
      File "mercurial\hgweb\webcommands.pyo", line 1318, in graph
      File "mercurial\templater.pyo", line 1517, in __call__
      File "mercurial\templater.pyo", line 1365, in process
      File "mercurial\templater.pyo", line 1355, in _load
      File "mercurial\templater.pyo", line 266, in compileexp
      File "mercurial\templater.pyo", line 408, in buildtemplate
      File "mercurial\templater.pyo", line 266, in compileexp
      File "mercurial\templater.pyo", line 444, in buildmap
      File "mercurial\templater.pyo", line 292, in gettemplate
      File "mercurial\templater.pyo", line 1352, in _load
      File "mercurial\templater.pyo", line 1497, in load
    IOError: [Errno 2] template file C:\Program Files\TortoiseHg\templates\paper\graphentry.tmpl: No such file or directory
    

    Regards,

  2. Phil

    Seeing the same thing in 4.5.3 using the x64 MSI installer.

    I'm going to try the workaround mentioned by the OP, if I can find the appropriate files.

  3. Log in to comment