any idea to solve this?
Hey @linger ,
Welcome to our community board.
Did you upgrade from version 2.43 to 3.7.1? Can you provide some server logs? They may help us to understand the root of your error.
Regards
Philipp
Hello @pahrendt ,
I get the same error on all of our HG repos when I try to access the //<Sources//> tab. We just upgraded to 3.7.3 from 2.x
Git and SVN repos still show up just fine. And it seems that we can still pull and push everything, so this looks like a GUI error.
Was there any solution to this problem?
–Maxim
Hi @maxim.serebrennik ,
do you also run SCM-Manager on Windows? In the server logs, you should find details regarding the error when you look for the transaction id. We cannot do much without these details. Can you give us these logs?
Thank you very much!
René
Hi @pfeuffer
Yes, I’m running it on windows.
I’m thinking the problem is this:
2025-03-17 07:17:59.274 [qtp1288354730-1758] [2HUfhQmVa1DB] ERROR org.javahg.internals.Server - stderr from Mercurial: *** failed to import extension fileview from D:\SCMRepos\lib\python\fileview.py: No module named builtins
2025-03-17 07:17:59.367 [qtp1288354730-1758] [2HUfhQmVa1DB] ERROR com.cloudogu.scm.readme.RepositoryLinkEnricher - Could not append readme link to repository
org.javahg.UnknownCommandException: Mercurial command ‘fileview’ is not supported by Mercurial version: 5.9.1
Not sure how to solve that though…through the normal GUI
@pfeuffer Updating my local HG install to 6.3 from 5.9 did the trick…for that error, and now I see:
This happens when I click on the Branches tab in HG repos
@pahrendt I think I solved it.
Mercurial naming convention lets the user commit branch names with spaces and ( ) which is what some users have done. SCM Manager does not understand them, which seems to be a bug, since the underlying mercurial system handles them just fine. Creating a mercurial branch with a space or a ( ), and maybe other symbols as well, will create the above error. The branch will then need to be closed to resolve the problem. Note, it does not need to be deleted, just closed so it does not show up in the SCM GUI.
Hi @maxim.serebrennik could you please share the naming conventions for mercurial? I had no luck to find anything regarding branch naming in hg/mercurial.
Thanks in advance!
Hi @christoph.loose
I only found this:
Looking at the Tag convention, anything other than
:”)\r”)\n”)\0”)is acceptable in a branch name/tag.
Thank you! We will make a change soon.
Note that we will not support the use of ( ) for branch creation in the SCM-Manager GUI. The reason is that we want to keep the validation of branch names consistent across all supported repository types.
However we will implement ( ) and others characters in a way, that they will be support in the GUI. So you would have to create them locally and push them afterwards.
Awesome! Thank you! I didn’t check, but the same problem might be in Git repos. I know they also have certain chars they allow and don’t.