youngmon/atlassian-qna huggingface dataset:
Fisheye can't read ssh key
Asked by Trevan Richins:

A few days ago, fisheye stopped indexing our repositories. When I run test connection, it gives a wierd message about it not being able to create the .ssh directory and that the identity file is not accessible. I've gone through the UI and recreated the ssh key and it can read and write it. The .ssh directory was originally created by fisheye and it hasn't changed. Any idea what's wrong?  
Fisheye is using 'C:\\Git\\bin\\ssh.exe' to authenticate with SSH authenticated repositories.

Error testing connection.  
Error talking to repository:   

Warning: Identity file c:\\FISHEYE_INST\\data\\auth\\Repo not accessible: No such file or directory.  
Could not create directory 'u/.ssh'.   
Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).   
fatal: The remote end hung up unexpectedly  

at com.atlassian.fisheye.git.GitScmConfig.testConnection(GitScmConfig.java:143)  
at com.cenqua.fisheye.RepositoryConfig.testConnection(RepositoryConfig.java:444)  
at com.atlassian.fisheye.spi.admin.impl.DefaultRepositoryAdminService.testConnectionFor(DefaultRepositoryAdminService.java:553)  
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

Connection failed.


Answers:
author: Trevan Richins
body: Updating Git actually didn't fix it. It happened a few hours after the update. The reason why it looked like it fixed it was because there was a long running ssh command going that had to be killed to update Git. When the error occurred again, I just killed that long running ssh command and it worked again.

I believe what actually happened was I had changed the number of "Incremental Indexing Threads" from 1 to 3 a few days earlier. I changed that back to 1 and I've never seen the longing running ssh command or this error since.


author: Piotr Swiecicki
body: Hi Trevan,

The error
> Warning: Identity file c:\\FISHEYE_INST\\data\\auth\\Repo not accessible: No such file or directory.

clearly explains the file c:\\FISHEYE_INST\\data\\auth\\Repo was not readable to the user running FishEye. I'm guessing that there were wrong permissions that were fixed when key pair was recreated. Can you let me know what FishEye version are you using? Just curious as the issue was fixed recently in FishEye 3.2.1 release: <https://jira.atlassian.com/browse/FE-4984>

Cheers,

comments: author: Trevan Richins
body: No, that didn't seem to be what is happening. I actually deleted that old identity file and let Fisheye regenerate it. So it should have been able to read/write the file. Also, this error occurred over a weekend and the file had previously been working.


author: Trevan Richins
body: I updated Git for Windows and it is working now.


Tags: fisheye-crucible-administration
Crucible tried to anchor your patch, but there was conflicting content
Asked by John Henckel:

I'm trying to use Crucible with CVS for precommit review. When I upload the patch, it says

    Crucible tried to anchor your patch, but there was conflicting content 

All my files have keyword tag $Log: NameOfTheFile.java,v $ and this seems to be the culprit. If I remove the tag and commit, the problem goes away -- I can upload precommit patches to Crucible. However I do not want to remove all the keyword tags from my files.

Is there any other work-around? [One page](https://jira.atlassian.com/browse/CRUC-6235) says I can manually edit the diff. How??


Answers:
author: John Henckel
body: see [answer here](http://stackoverflow.com/questions/20333351/crucible-tried-to-anchor-your-patch-but-there-was-conflicting-content/20521057)


author: John Henckel
body: Note, I found another work-around. I can create the patch with "cvs diff -u10000 \[files\] \>patch" and that will upload the entire source file instead of just 3 lines context. The anchor still fails, but at least I can view the entire file. However, I would still like to know how to "edit the diff" to avoid the anchor failure.
Error with GIT repository
Asked by Rumceisz:

Dear Support Team,  

we have configured a GIT repository couple of months ago and the repository still has not started scanning.   
When testing the connection we get the following error message:  
"Fisheye is using '/usr/bin/ssh' to authenticate with SSH authenticated repositories.  

Error testing connection.  
Error talking to repository:  

ssh: Could not resolve hostname git-upload-pack: Name or service not known  
fatal: The remote end hung up unexpectedly  

at com.atlassian.fisheye.git.GitScmConfig.testConnection(GitScmConfig.java:143)  
at com.cenqua.fisheye.RepositoryConfig.testConnection(RepositoryConfig.java:444)  
at com.atlassian.fisheye.spi.admin.impl.DefaultRepositoryAdminService.testConnectionFor(DefaultRepositoryAdminService.java:553)  
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)  

Connection failed."  

<br />

Could you please explain us the error message?   

Thanks in advance,  
Rumi


Answers:
author: Timothy
body: What URL are you using to talk to you Git? Are you sure that the hostname is correct? Does IP address work?


Tags: fisheye-crucible-administration
Do FishEye 3.1.5 support managed repository?
Asked by ArunK:

Hi,

We have managed repositories in our Fisheye 2.7.8. We are now upgrading to FishEye 3.1.5.

I know fisheye do not have provision to take backup of managed repositories.

But I recently heard that Fisheye version 3.x do not support managed repository.

Is that true?

Best Regards,

Arun Kumar


Answers:
author: Nick
body: FishEye 3.1.5 does not officially support Managed Repositories, though they can still be accessed, however if anything goes wrong there is no support provided by Atlassian.

FishEye 3.2.0 will not start by default if you still have any managed repositories. You can pass FishEye a flag on startup however, to force it to start and the managed repositories will be converted to normal repositories. You will need to update the location of the repository with the new location to where you moved the source of the repo to.


author: Piotr Swiecicki
body: Arun, if you consider migrating your managed repositories elsewhere, there is a migration guide provided: <https://confluence.atlassian.com/display/FISHEYE/Migration+guide+for+Git+internally+managed+repositories>

Hope that helps


author: Norman Abramovitz
body: Here is the url to the notice

<https://confluence.atlassian.com/display/FISHEYE/End+of+Support+Announcement+for+Internally+Managed+Repositories>

It looks like 3.1.x will support the current managed respository interface, but 3.2 will not.


author: ArunK
body: \>\> It looks like 3.1.x will support the current managed respository interface, but 3.2 will not.

Yes, that is what my understanding is. Managed repository is deprecated on August 14, 2013.

Statement is: "From 14 August 2013, Atlassian support for internally managed repositories in FishEye will end."

I wondering whether I should continue upgrade from Fisheye 2.7.8 to FishEye 3.1.5 especially since we have managed repositories.

I don't know what it really means Atlassian support will end?

Is that if something goes wrong, Atlassian support will not help us?


Tags: repository
Why are sources.seinlet.com committers' e-mails public?
Asked by Andrzej:

Hi,

I can't find any solution to remove my e-mail address from [sources.seinlet.com](http://sources.seinlet.com) so I'm asking this question and looking for clear answer.

Few years ago I've been participating in creation of small script on [github.com](http://github.com). Now I see that that repository was moved to [sources.seinlet.com](http://sources.seinlet.com) and all e-mails were publicized. My mailbox is now visible for wider range of spammers.

Can anyone explain me how can I remove my e-mail address from this repository <http://sources.seinlet.com/changelog/jquery-week-calendar>? It seems that I don't have account there (I've tried to use request new password form).

Thanks for any help.

Cheers, A.


Answers:
author: Nick
body: It looks like somone at [seinlet.com](http://seinlet.com) has indexed that github repository and made it publicly accesible.

Your email address is visible, because the repo you contributed to <https://github.com/themouette/jquery-week-calendar/> is a public repository and your git username with which you made the comit using, contained your email address.

If you sign-up for an account on <http://sources.seinlet.com/login/signup.do> using the same email address, then FishEye will map your committer name to your username and wont render an email address next to those commits.

comments: author: Andrzej
body: Thank you for your response. I registered in that site and my e-mail address disappeared from some pages but then appeared in other ones. For example when I hover my nickname or open my profile I can see my e-mail. It's privacy policy violation so I want to remove that content if you don't know how to solve my problem.
Fisheye: SVN error in source tab
Asked by hgierer:

When viewing the source tab of a file in FishEye (3.1.1) I am getting this error message:

**java.io.IOException - Exception getting SVN blame for trunk/...@374: org.apache.subversion.javahl.ClientException: svn: E200007: Retrieval of mergeinfo unsupported by ...**

The svn server uses a rather old svn 1.4.3.

Fisheye admin says:

The bundled Subversion client, SVNKit, is being used for Subversion operations.

The JavaHL client version is SVNKit v1.7.10.9848.

**Is there a way to make the source tab available?**


Answers:
author: Nick
body: Can you please try the latest version of FishEye 3.2.0.

This bug was in fact fixed in that version: <https://jira.atlassian.com/browse/FE-4971>

Cheers,

Nick

comments: author: hgierer
body: Yes - after upgrading the error does not occur anymore. Thank you !


author: Peter Van de Voorde
body: Hi Heiko,

I think mergeinfo isn't supported by any subversion repo older than version 1.5.

So you'll probably need to upgrade the repository.

Best regards,

Peter

comments: author: hgierer
body: Not only the repository but also the subversion server itself.

From what I read FishEye supports SVN from 1.3 so I thought there would be a solution on the FishEye-side.


author: Peter Van de Voorde
body: Maybe you can raise a ticket about it here : <https://jira.atlassian.com> ?

Best regards,

Peter
See comments on file from previous reviews
Asked by Andrew Leech:

I've recently compiled a number of old outdated reviews that had overlapping coverage into one new review covering a module more cleanly.

Is there any way to bring comments on files from the previous reviews into the new review?

I know I can browse each file in fisheye, see which reviews cover it and look in each review separately, but this is very slow and tedious.

I really just want to import old comments into the new review, or at least have some view that will show all comments for each file from any review.

Cheers,

Andrew


Answers:
author: Andrew Leech
body: Can this be put in as a feature request?

There's two separate desired features here:

\* have a way to import comments from linked reviews

\* have a way to view all comments in a file from any review

Everyone I've mentioned these limitations to here at work seem shocked that it can't be done.


author: Nick
body: Hi Andrew,

Linked Review functionality is to indicate that one review has been re-issued because it contains a lot of rework from the previous review.

I am afraid you will need to re-add the comments from the old reviews onto the new review manually.

Cheers,

Nick


author: Andrew Leech
body: Hi Nick,

Thanks for the reply. We still want to keep the previous reviews, so taking one of them and expanding it (dramatically) is not a viable option.

Is there definitely no way to do with with the "Linked Review" function? Is there any purpose to this function?

Would is be possible to add an option to Linked Reviews to have their comments show up on the new review?


author: Nick
body: Unfortunately there is no way to do this.

The best option is possibly to use on of the old reviews (the one with the most comments) as the basis for the new review. Edit this review, by adding all the files from the other reviews you need and copy the comments across too.
sourcetree freezes and consuming a lot of memory and CPU
Asked by Guathan Medeiros:

My sourcetree freezes and appears consuming a lot of memory and CPU, I need to kill the application to open again, I don't have a .git folder in my c :, what should I do?


Answers:
author: Gonchik Tsymzhitov
body: hi !

Did you set the point as logical volume?

Looks like is indexing or searching issue
I got a trial for Crucible/Fisheye but adding users is disabled under Application Access
Asked by Alexander Farennikov:

I thought starting a trial adds at least a few users but under Application Access all checkboxes are disabled and it says that I have exceeded available licences by 1 (it said it even before I started the trial as well).


Answers:
author: JolyonKB
body: There is an open issue for this on AOD: [AOD-5952](https://jira.atlassian.com/browse/AOD-5952) which says this is a 'harmless error.' Apparently it can only be removed by issuing a request to atlassian support.


author: Alexander Farennikov
body: It's an evaluation licence.

We only have 2 repos and under 7 committers now so this is not a problem.


author: Felipe Kraemer
body: Hi Alexander,

Are you by chance using a FishEye Starter license? I am asking this because this type of license has some restrictions:

<https://confluence.atlassian.com/display/FISHEYE/Restrictions+on+FishEye+Starter+Licenses>

You can have:

* Up to 10 historic committers in FishEye
* Up to 10 committers per repository
* Up to 5 repositories

I am not sure what you mean by "under Application Access all checkboxes are disabled". Can you please clarify this further? Are you using FishEye / Crucible Standalone? What version are you running?
Using Sourcetree with GitHub: Having Trouble Adding an SSH Key to My GitHub Account
Asked by Tom Bluewater:

![sourceTree.jpg](/t5/image/serverpage/image-id/115002iB34C0205FEA777BF/image-size/large?v=v2&px=999 "sourceTree.jpg")

I'm trying to use **Sourcetree** (for **macOS** ) with **GitHub** . The followings are the steps that I have taken many times after visiting a dozen websites include this [Japanese article](https://qiita.com/evitch/items/5d87b8aab5cd72695d2b). I thought it's well-written. But it doesn't work for me.

1. ssh-keygen -t rsa -C xxx where xxx is my e-mail address as a comment

2. Location: /Users/yyy/.ssh/id_rsa where yyy is my user account name

3. I enter a pass phrase twice.

4. cd \~/.ssh

5. chmod 600 id_rsa

6. I edit the config file in the .ssh folder as follows.

Host github.com

HostName github.com

IdentityFile \~/.ssh/id_rsa

User git

7. ssh-add -K

8. pbcopy \< \~/.ssh/id_rsa.pub

9. I go to github.com and enter the key that I copied into the clipboard under the SSH and GPG keys section of the sidebar.

10.Switching Sourcetree, I create a new account. The host is GitHub. Auth Type is OAuth. I then click on Connect Account. The protocol is set to SSH.

And Sourcetree says Upload Failed There was a problem adding your new SSH key to your GitHub account. Please add this manually via their website. Does anybody know what I'm doing wrong? I've followed the steps with two different computers. And I can't go any further.

Lastly, I do have my private and public keys in the .ssh folder. My macOS version is 10.15.4. And the Sourcetree is 4.0.2 (236), which is installed on a brand-new iMac and as well as on a 7-year-old iMac.

Thanks.


Answers:
author: Tom Bluewater
body: I've solved the problem for myself. I need to select **Basic** as Auth Type.


author: cilhao
body: The problem has nothing to do with SSH!

The problem is that you have enabled your two factor authentication and Sourcetree is not able to connect. You must go to your GitHub account and create a Personal Access Token in Developer Settings, after that you go to you Sourcetree and edit the Auth Type of your GitHub account to Basic, fill your username and paste your newly created Access Token instead of your password, this will bypass the second factor of authentication.

comments: author: Allan Dowdeswell
body: This helped me, thanks!


author: binla
body: Thanks!! my problem has been solved by your solution.


author: TheKingArthas
body: Thanks cilhao, this solved my issue!


Tags: git

github

mac

ssh
Source Tree branch push only show master branch
Asked by Janaka Prasad Wijesena:

I am new to using source tree. This is what I have done;

I created a branch from the master.

made some changes

commit the changes

Now when I want to push the changes of the branch the dialog only show the master branch.

![unnamed.png](/t5/image/serverpage/image-id/114961i6328D52C916A2391/image-size/large?v=v2&px=999 "unnamed.png")

I am clearly in the branch when I commit and click push button.

How do I push to remote branch. Does it not get created when I branch from master?

I checked with other developers in my team and after they commit their changes the push button shows the push count in red. In my case it does not.

![Capture.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/115053iBA953B2D78F0398D/image-size/large?v=v2&px=999 "Capture.PNG")

In my case I don't see this.

If I use the command line I can push it without any problem. I assume there is some sort of a setting to get this working?

in the command line I get following message

fatal: The current branch feature/reservation_3 has no upstream branch.  
To push the current branch and set the remote as upstream, use

git push --set-upstream origin feature/reservation_3

I think when I create the branch if I know how to do this part from source tree that would fix this issue


Answers:
author: Shrake, James
body: In Source Tree, Check Tools -\> Options -\> Git -\> Push branches. If it is set to current, it may cause this issue. Change it to simple. If that doesn't work, change to none.


author: Jacob Lucas
body: I am experiencing this same issue.

This only appears to happen when my local branch is tracking the remote. In other words, I can create a new branch from a specified commit, then when I commit changes to that local branch and click push, the local branch will appear in the list as long as it is not tracking the remote. From there I can select which branch to push to manually.

However, this is less than ideal and needs to be addressed.


author: rxbudian
body: I have the same problem.

I've updated to the latest version of sourcetree (3.4.2)

made sure SSH Agent has started.

tried pulling and fetching with SourceTree

even tried creating a branch with SourceTree

Still only have the master branch on the push, no joy
Review translation of sourcetree
Asked by malte.schlueter:

Hii,

there are over 3100 unreviewed translations for german and many existing are nonsense.

I also add some replacements but i have no permissions to review it.

Is transifex up to date or is there a new tool for the translations?  
Is it possible that some people or the community can review the german translation?

Best regards


Answers:
author: greiler_at_glue
body: Since Version 3.4.16 there is a new translation error:

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/301949i8EFB57635D92D413/image-size/large?v=v2&px=999 "image.png")

There used to be "Verwerfen":

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/301950i50A924D29AFDADA4/image-size/large?v=v2&px=999 "image.png")

This is the context menu for a file in the "unstaged files" list.
Can not clone DevOps repo
Asked by Kaare Kjeldsen:

A very basic question, I hope :)

I am new into DevOps, and have created a new project, Test2, with a few files for testing.

Now, I try to hook Sourcetree up to this project / Clone it.

I have succeeded to make a DevOps account with PAT authentication, using the "companyname.visualstudio.com" address.

So far so good.

Now I want to clone the project:

- From DevOps project, I go to "Repo" and hit "Clone". https://Companyname@dev.azure.com/companyname/Test2/_git/Test2

- Then I paste the URL to Sourcetree "Clone" URL.

- Error message: "This is not a valid sourcepath / URL

I have tried with different URL's, using the "visualstudio" address in different combinations, but nothing works.

Cloning with command line / GIT bash works fine.

Can anyone give me a hint, how I can clone my DevOps repo in Sourcetree?

Thanks in advance!


Answers:
author: Kaare Kjeldsen
body: Additional info:

When I add a GIT project in DevOps, it shows up i Sourcetree "Remote repositories". So connection/account seems OK.

If I hit the "Clone" button right next to this project, it inserts this URL into the Clone tab:  
<https://companyname.visualstudio.com/Test3/_git/Test3>

And I get this error "Output:  
Error: fatal: Authentication failed for '<https://companyname.visualstudio.com/Test3/_git/Test3/>'

comments: author: Liam Parker
body: I'm having a similar problem, did you get your problem resolved? Also are you using Windows or Mac?


author: Kaare Kjeldsen
body: Hi Liam

No, unfortunately, no response from this forum, and I have not succeeded my self either.

I am using Windows.


Tags: clone

devops
Github????????????????mac??????????????????????????
Asked by ????:

????????

Github??????windows?mac?????????????????????windows????????????mac???????????????????????????????????????

??????????????UAL????????????????????

?????SSH???????????SSH??????????

mac???????????????????


Answers:
author: Rick Li
body: ?????????????????????????

??????????????????????

<https://community.atlassian.com/t5/Sourcetree-questions/Cloning-repository-error-This-is-not-a-valid-source-path-URL-Mac/qaq-p/373372>

?????????????

* *Sourcetree \> Preferences \> Accounts* ??????
* ????????????Edit????????????????
* Auth Type??Basic???????Protocol??SSH?????????

????????????????????????????????Sourcetree Mac 2.7.1 ?v2.4 ?????????????v2.3????????????????????
Need option to force "Fetch and store tags locally"
Asked by Santacrab:

I would like to be able to pull from remotes a TAG even if it has been moved in the repository, instead of getting the "would clobber existing tag" error.  

It would be great to have an option to force it, instead of having to use the command line:

git fetch --tags -f


Answers:
author: rexmtorres
body: Any news on a fix for this? It's quite annoying to have to constantly execute \`git fetch --tags -f\` before you do any fetch/pull in the SourceTree application. Kind of defeats the purpose of having a UI.

comments: author: Mochnant
body: In my case I always know what the offending tag is so I can just delete it locally with the UI but it is still annoying!


author: BIF01
body: You can vote for [SRCTREE-7077](https://jira.atlassian.com/browse/SRCTREE-7077)!


author: Mochnant
body: It's a shame that it has been nearly 5 years of "Gathering Interest" on [SRCTREE-7077](https://jira.atlassian.com/browse/SRCTREE-7077) with no fix in sight for what seems like a very small amount of work. At least we're up to 24 votes.


Tags: git