Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

error code 255 in Catalina

I tried to open my pre-existing repo in SourceTree (running macOS Catalina) and get the error "hg status failed with code 255....repository requires features unknown to this Mercurial: sparserevlog". My version of Mercurial (hg --version) is vdersion 5.3.

The repo works find and can be managed fine from the command line (for years). My hope was to transition away from the command line.

Any ideas?

1 answer

Further to my original query, I note that my system version of mercurial is newer than the one embedded in mercurial. I attempted to "use system mercurial" (in the Python.framework directory) but sourcetree greyed out the executable........

Well I managed to switch to the system version which was located at

mine is located at /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/mercurial


However....I now get error code 255 again but this time with "failed to import extension hgext.hgflow....module has no attribute." 

Something of a can of worms it seems......

I got things working - just about - I needed to uncheck hgsubversion and hgflow, whilst using system mercurial. Is there a more elegant solution that doesn't reduce functionality?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events