Cannot view Commits through web interface

[Jake Sindelir]

I have done some searching, but so far have not been able to find any information that has been helpful.

I am getting the "Could not load items. Server returned status: 500" when I click the link to view Commits, however, the Source button works fine and able to browse without issue. I may be overlooking something, but any help would be appreciated.

[Sebastian Sdorra]

Could you post the log output after getting the error?

2015-05-11 2:37 GMT+02:00 Jake Sindelir <jakesi...@gmail.com>:

I have done some searching, but so far have not been able to find any information that has been helpful.

I am getting the "Could not load items. Server returned status: 500" when I click the link to view Commits, however, the Source button works fine and able to browse without issue. I may be overlooking something, but any help would be appreciated.

--
You received this message because you are subscribed to the Google Groups "scmmanager" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scmmanager+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jake Sindelir]

Sorry this is REALLY late, had other projects I have been working on. I have updated to version 1.46 and still getting the same error, and here is the log.

http://pastebin.com/NfK5g84m 

[Sebastian Sdorra]

It is possible that you upgrade your mercurial installation?

Sebastian

2015-10-03 2:41 GMT+02:00 Jake Sindelir <jakesi...@gmail.com>:

Sorry this is REALLY late, had other projects I have been working on. I have updated to version 1.46 and still getting the same error, and here is the log.

http://pastebin.com/NfK5g84m 

--

[Jake Sindelir]

It is very possible that I upgraded mercurial automatically at one point without noticing.

I have 2.2.2 currently installed on my server (using 'hg version')

If this is not the right version, what version (range) is required/recommended?

[Sebastian Sdorra]

It should work with version 2.2.2, but it is quite old. I just asked for an update, to exclude a bug in mercurial. Did you get this error for all repositories? Or only for specific ones?

Sebastian

--

[Jake Sindelir]

Oh wow, I honestly did not know my Debian/Mercurial installation was that far behind! So I added backports and installed Mercurial 3.1.2 and all works now!

So it does seem to be a compatibility issue between SCM-Manager and Mercurial 2.2.2.