You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello!
Just created a brand new local repository. This happened immediately when the window for it opened:
Transcript:
[A dialogue-box on top of repository window]
'hg status' failed with code 255:'abort: Operation not permitted: '/Users/oscar/Library/Caches/com.apple.Safari.SafeBrowsing'
**
Ehm, wut? As I closed the dialogue box, it kept reopening for a few times. Should I be concerned?
Kind regards
/Oscar
Ok, it's human error.
Turns out I accidentally made my entire home folder into a repos, so obviously it tried to go through ALL my files, including files with special permissions. I guess the fact the safe browsing cache has special permissions is actually reassuring : )
Note: I thought the name of the repos would be added to the path, when creating a new repos. That's how it happened.
Cheers!
Hi @kraybit,
We haven't had any reports of this before. The 'status' command is used with Mercurial to get the current information about the repository. The error shown is coming directly from Mercurial. Does it still occur if you switch from "Embedded Mercurial" to "System Mercurial" in the preferences?
Brian Ganninger
Principal Developer, Sourcetree
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your reply Brian. I found the "bug", see other answer. Thanks again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@kraybit, glad to hear you found the root cause. Thanks for updating and sharing the solution!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.