youngmon/atlassian-qna huggingface dataset:
Unable to login Bitbucket - We couldn?t log you in
Asked by timofte.radu:

Hello,

I am getting following error when login to bitbucket account.

"You may run into this issue when you use specific browsers or add-ons that hide the referer header for id.atlassian.com and other Atlassian sites. Check for these and then try logging in again."

I suspect that my account is marked as inactive and needs reactivation.

Could anyone please help?

Thanks,

Radu


Answers:
author: Patrik S
body: Hey [@timofte.radu](/t5/user/viewprofilepage/user-id/5402129) and welcome to the Community!

Your account was indeed inactive on Bitbucket Cloud due to a long period of inactivity. I went ahead and set it to Active again.

If you are still facing issues to login, please let us know.

Thank you, [@timofte.radu](/t5/user/viewprofilepage/user-id/5402129) !

Patrik S


author: Laurie Sciutti
body: Hello [@timofte.radu](/t5/user/viewprofilepage/user-id/5402129) and welcome to the Community! [@Patrik S](/t5/user/viewprofilepage/user-id/4603309) may be able to assist.


Tags: bitbucket-cloud

cloud
Fisheye Commit Graph
Asked by Travis Hamer:

Fisheye's Commit Graph reflects the check-in comments in the Subversion repository -- or more correctly it doesn't reflect the **edited** check-in comments. The application was restarted, but the query retained the aged check-in comments.

We would prefer that Fisheye Commit Graph draw a fresh view of the repository's check-in comments with each fresh instance.


Answers:
author: lpater
body: Hi Travis,

FishEye caches and indexes the history of your repository to enable fast browsing and searching. If you edit your check-in comment FishEye will still see the cached one, that was retrieved when scanning the commit.

To manually update your check-in comments, you'll need to do a SVN non-versioned properties rescan. You can find the option in the repository admin screen, as described here: <https://confluence.atlassian.com/display/FISHEYE/Indexer>.

If your usecase requires you to do this often, you might be interesetd in automating it using the rescan-metadata REST resource: <https://docs.atlassian.com/fisheye-crucible/latest/wadl/fecru.html#d2e505>


Tags: fisheye-crucible-administration
Getting an error indexing Git repo in Fisheye when I have a .mailmap
Asked by Chris Kirkham:

I have a repository (i have created a fresh new clone to do this) with a .mailmap file. Constantly getting the error below.

If I remove the mailmap file the repository indexes but I have multiple "committers/authors" for users who have commited using different emails. (We are also on a starter license at the moment and it stops full indexing of the repo - no chance of upgrading at the moment).

I have removed the file and added mailmap.file in the gitconfig and still no luck (this doesn't use the file at all). Restarted the server, created fresh clones numorous times - nothing.

On 3.1.5, git 1.8.3 and windows server 2008.

Anyone else hit a similar issue and have another avenue of investigation I can go down?

Thanks,

Chris

\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

Repository index failed due to error com.cenqua.fisheye.rep.RepositoryClientException: com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while communicating with VCS: com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while communicating with VCS: com.atlassian.utils.process.ProcessException: While executing: "c:\\Program Files (x86)\\git\\bin\\git.exe whatchanged --always --reverse --date-order -m --no-abbrev --no-renames a4275f035929684c1089a05d4459827a5c351e9c --pretty=format:C:%H%nP:%P%nA:%aN%nE:%aE%nR:%cN%nF:%cE%nD:%at%nS:%s%nB:%b%n@@fe_body_end@@ " in \[E:\\Crucible-CreditSolve\\var\\cache\\CKTest\\clone\] com.atlassian.utils.process.ProcessException: Non-zero exit code: 255


Answers:
author: Chris Kirkham
body: After some additional investigation - <https://jira.atlassian.com/browse/STASH-3891>

Mailmap needs a blank line at the end of the file


Tags: fisheye-crucible-administration
Fisheye - Reclaim used disk space?
Asked by NathanG:

My fisheye server ran out of disk space. I'm going to change the "Start Revision" for one of my repos... but how do I reclaim the used disk space?

Do I have to delete the repo (in Fisheye) and start over?

Thanks!  
--

Nathan


Answers:
author: NathanG
body: This became somewhat urgent so I ended up going into the largest repository in fisheye, changing the start revision at setting, going to maintenance and clicking "re-index".

It seems to have cleared up many, many GBs of space.


Tags: fisheye-crucible-administration
FishEye indexes commits multiple times
Asked by Wouter de Vries:

It seems FishEye sometimes indexes commits multiple times. Could this be a bug related to #resolving multiple issues in a single commit?


Answers:
author: Wouter de Vries
body: I found out what's going wrong. I have several SVN repositories with relative paths for products and an all encompassing SVN repository. Smart commits cannot be enabled/disabled per repository and thus all smart commits are picked up twice. Once in the all encompassing SVN repository and once in the relative repository.

I voted on <https://jira.atlassian.com/browse/FE-4301> : Ability to opt a single repository or #pattern out of smart commits


author: Rahul Aich [Nagra]
body: In that case, Iam not aware on how this can be resolved. Lets wait for others to join in to the discussion.

Raul


author: Wouter de Vries
body: We are using FishEye and Crucible 3.1.5 with a SVN repository (used for multiple projects).


author: Rahul Aich [Nagra]
body: Hi Wouter

Which version of fisheye are you on?

This seems to be a bug on the old fisheye versions (earlier than 2.7.4) and was fixed in 2.7.4.

If you are on an earlier version, upgrade to 2.7.4 should fix your issue.

Have a look at the link below, this was discussed in answers before

[https://answers.atlassian.com/questions/16734/fisheye-seems-to-be-indexing-commits-multiple-times](/questions/16734/fisheye-seems-to-be-indexing-commits-multiple-times)

Rahul


Tags: fisheye-crucible-administration
Is Fisheye:FishEye 3.1.5 is compatible with Crucible:Crucible 3.1.5?
Asked by ArunK:

Hi,

I am about to upgrade Crucible from 2.7.8 to 3.1.5.

I found that we have different installer for both Crucible and Fisheye (I thought those as single product).

<https://www.atlassian.com/software/fisheye/download>

<https://www.atlassian.com/software/crucible/download>

So I have couple of questions before I start upgrade.

1. What could be the order of instalaltion (First Fisheye then crucible?)

2. Is there any compatibility issue between two. Suppose I upgrade Fisheye to 3.1.5 and keep Crucible to still 2.7.8 for some time. Will that work?

Best Regards,

Arun Kumar


Answers:
author: Nick
body: FishEye and Crucible are the same binary, just each has a different name since either can run standalone or with the other.

To answer your questions:

1. What could be the order of instalaltion (First Fisheye then crucible?)

Only install one. It doesn't matter which one, as they are the same. Once installed, your licenses will be detected and the appropriate products will be enabled.

2. Is there any compatibility issue between two. Suppose I upgrade Fisheye to 3.1.5 and keep Crucible to still 2.7.8 for some time. Will that work?

You should not be running two separate instances. You should only have a single instance running which will have both FishEye and Crucible enabled. The product detects your license(s) and enables the appropriate product(s). This means that you when you upgrade both FishEye and Crucible will be at the same version.


author: Piotr Swiecicki
body: Hi Arun,

Do you have a single instance of FishEye and Crucible or do you have them separated? FishEye and Crucible is technically the same application, appropriate parts of it are logically enabled or disabled depending which licences did you entered. So most likely you are using single instance and then it doesn't really matter wich product you download - crucible or fisheye. You need to upgrade it only once.

By the way you may notice the FishEye and Crucible application bundles differ slightly, but the only difference between them is the branding on the setup wizard.

Also, I would advice you backup your instance before the upgrade, just in case. So if anything goes wrong you can always revert back.

Kind regards,

comments: author: ArunK
body: We have single instance of both FishEye and Crucible.


author: ArunK
body: Hi,

Thanks Piotr and Nick for clarifying the things.


Tags: compatibility

upgrade
No activity, no committers in stash-fisheye crucible connection ...
Asked by Rodrigo Aleluya:

In stash proyect, i see auhtor ... but in fisheye:

![](../../upfiles/1_43.png)

NO ACTIVITY

![](../../upfiles/2_15.png)

NO FILES IN REPO PRE !!!

Products in evaluations ...


Answers:
author: Rodrigo Aleluya
body: resolved:

In git connection details, path field in blank ...... voila.

Thanks Atlassian.-


author: Rodrigo Aleluya
body: hummmmm .... I tried everything:

I have the latest versions of git, stash, fisheye/crucible and nothing ...

This should be trivial ... I still can not see anything from the repos stash's in fisheye / crucible ...

someone can give me some email or link to raise a bug? ...  


author: Erik Saline [BlackPearl PDM]
body: I had this issue previously and was able to fix the issue by installing the latest Git client on Stash. Once Git was updated to the latest everything worked, hope that helps.


author: Rodrigo Aleluya
body: To bring the repository from stash, you should bring the commits that already exist?, It should bring the files that already exist? ... Well, something is wrong because I do not bring anything ...
Fisheye and SQL server 2008 R2
Asked by Bill Mariasoosai:

All:

As per the documentation on Fisheye (3.1) and Migrating to SQL server

**An existing Java bug prevents connection with Java 1.6.0_29 and above (including Java 1.7.0). Read more about the issue and possible workarounds here.**

**Cause**

In Java 6u29, there was a bug introduced which prevents SSL connections to SQL Server 2008 R2. This bug was logged with Oracle as Bug [ID: 7103725](http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7103725).

**Resolution**

Oracle delivered a fix in 6u30, although for at least one affected client not even Java 1.7 worked. Users can get around this bug by downgrading their version of Java (version 1.6.0_24 is confirmed to work) or by passing Java the following property and value:

I am planning to use FishEye 3.1.4. with Java1.7.0 . Is this fixed in this release 3.1.4?

Should I downgrade my Java to 1.6.0_24?

Could some one confirm it, please.

Thanks for your help.

Bzoo


Answers:
author: Bill Mariasoosai
body: ### Resolution {#toc-hId-1509177826}

As per the Fisheye (3.1.x) documentation, the following is the resolution to the above problem:

-----------------------------------

Oracle delivered a fix in 6u30, although for at least one affected client not even Java 1.7 worked. Users can get around this bug by downgrading their version of Java (version 1.6.0_24 is confirmed to work) or by passing Java the following property and value:  

```
-Djsse.enableCBCProtection=false
```

```
---------------------------------------
```

```
1) Could any body ( java expert ) tell me which java file in fisheye  I should modify to test this option
```

```
-Djsse.enableCBCProtection=false so that I can connect to SQL server 2008
```

```
or 
```

```
2) Can I use one version of jdk _1.7.0 for Jira/Confluence and another version jdk_1.6.0_24
```

```
for fisheye/crucible.
```

```

```

```

```

```
Thanks for your help.
```

```
Regards,
```

```
Bzoo
```

```
?
```
Fisheye Update Error
Asked by Yavuz Selim ?ZBEK:

After updating FishEye plugin the following error occurs

This add-on couldn't be loaded. It has one or more errors that prevent it from being enabled.


Answers:
author: Jobin Kuruvilla [Adaptavist]
body: You have to check your logs to find the actual error. Was the plugin compatible for your version of Fisheye?


Tags: fisheye-crucible-administration
Can't see commits on Activity tab
Asked by Philippe Robichaud:

For some repositories, I can see almost in real-time the commits that are executed by the team. For other repositories (with exact same parameters except the path to the right SVN folder), we only see the source files that have been indexed by Fisheye but can't see any commit in the Activity tab while tons were done through SVN. What are the possible reasons for this to happen?


Answers:
author: Felipe Kraemer
body: Hi Phillippe,

This could be happening because:

1. The user logged in FishEye is not associated with the groups [permitted](https://confluence.atlassian.com/display/FISHEYE/Permissions) by the repository.
2. The most recent commits might be huge (in terms of number of files, files sizes, etc) and FishEye is taking more than the usual time to index them.
3. You might be using an older version of FishEye in which [this major improvement request](https://jira.atlassian.com/browse/FE-4450) was still not implemented, and in this case you need to [upgrade](https://confluence.atlassian.com/display/FISHEYE/FishEye+upgrade+guide) your instance.

These are the things I can think about at the moment.

comments: author: Philippe Robichaud
body: Thanks Felipe. Here is a little bit more details on your assumptions:

1. All logged-in users is checked in the Permissions for the repositories I was referring to.
2. What can be done to accelerate the indexing engine? Can we restrict the initial indexing to a limited period of time in the past?
3. We currently use FishEye and Crucible 3.0.2


Tags: fisheye-crucible-administration
Fisheye service on Linux server
Asked by Bill Mariasoosai:

All:

I plan to install Fisheye/Crucible on Linux server(Suse 11)

I already have a user **"fishuser"**on the server (with read only access to SVN repos)

that communicates with the SVN repositories.

Can I use this user **" fishuser"**to run fisheye service on the linux server.

Thanks for your help

Bzoo


Answers:
author: Bill Mariasoosai
body: Hi Sergey:

Thanks a lot for your response. Makes perfect sense.

Regards,

Bzoo


author: Sergey Svishchev
body: If you can log on as 'fishuser' to Linux server, then likely yes. If it is only a Subversion account, then likely no.
Slowly clone by git in FishEye
Asked by ghiyasimehr:

I have a git repository which now it has 100MB code size. When I clone it, it goes until 61% well but after that it will be very slowly. It taskes 1-2 minutes to reach 100%. I want to profile FishEye while cloning.

How can I do that?


Answers:
author: ghiyasimehr
body: Based on [monitoring resources](slowly-clone-by-git-in-fisheye/235833) and thrown exceptions(above comments), I think it is a bug in threads scheduling.

It may be fixed by <https://jira.atlassian.com/browse/FE-3461> as @Felipe Kraemer said.

Solution to resolve this bug is waiting for furute releases!


author: Felipe Kraemer
body: Hello Hossein,

I've discussed this issue further with the Atlassian Development team, and they told me that unfortunately <https://jira.atlassian.com/browse/FE-3461> won't be shipped with FishEye 3.2. It wasn't implemented on time. Please accept our apologies for that.

Our suggestion is to add <https://jira.atlassian.com/browse/FE-3461> to your watch list in order to receive any updates on it.


author: Felipe Kraemer
body: Hello Hossein,

Slowness while indexing Git repositories is a known issue which is being tracked here:

<https://jira.atlassian.com/browse/FE-3461>

This major improvement will be released in FishEye 3.2.

In the meantime, there are some suggestions in the description of the above issue that you can consider trying.

comments: author: ghiyasimehr
body: I monitor CPU, memory and disk usage by nmon in Linux. it shows me these resources are not bottleneck. So slowness should have another reason!

What's your idea?


author: ghiyasimehr
body: I debuged it. In 61% time, fisheye gives exception:

```
fisheye GitServlet-processErrors - git-http-backend process caused exceptioncom.atlassian.utils.process.ProcessTimeoutException: process timed out        at com.atlassian.utils.process.ExternalProcessImpl.wrapUpProcess(ExternalProcessImpl.java:440)        at com.atlassian.utils.process.ExternalProcessImpl.finish(ExternalProcessImpl.java:306)        at com.atlassian.utils.process.ExternalProcessImpl.execute(ExternalProcessImpl.java:351)        at com.atlassian.fisheye.repomgmt.servlet.GitServlet.service(GitServlet.java:136)        at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
```

```
I can send complete stack trace on request.
```


author: ghiyasimehr
body: I set initial scan thread and incremental scan thread to 1 and 10 respectively. It was a little better and server responses to ping request. Already when I clone, server did not response to ping request. But still it is slow and it stops in 61% for 2 minutes.

In thread dump, there is a message but I do not know what does it meaning:

```
qtp1002735346-447: TIMED_WAITING (Waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@453d052f )
```


Tags: clone

fisheye-crucible-administration

monitor
The Curious Case of the Disappearing Defect
Asked by Tini Good:

Interesting possible bug?

A file was added to the review as a diff. I moved the sliders to only select the latest revision so I could see all lines of code, and added a defect on line 8 (which doesn't appear in the diff).

When the diff is displayed, my defect appears at the top of the page. If I click "Edit" on the Defect, it disappears. The replies to my defect are still displayed. I have to change my selection so that I am looking at the whole file and the applicable line of code with the Defect on it in order to edit my Defect. It doesn't matter which revision I look at, as long as Line 8 is identical to the Line 8 I made the Defect against.

This also happens on when I have multiple revisions/commits added to a single review. As lines are changed, often in response to a defect, over the various commits, my Defects/Comments will disppear when I try to edit them unless I go to the specific revions/commit with the original/unchanged line of code that the Defect was made against.

I don't understand this "feature". What is the purpose for requiring me to change my selected revision/diff in order to edit an existing defect/comment? Is there somewhere that gets into the "nitty gritty" of how specific lines of code and defects/comments relate when it comes to display and edit, because this is not intuitive.


Answers:
author: Tini Good
body: What I finally figured out is that when I have more than one set of revisions on my diff, this will happen. Apparently the defect is tied to the particular revision/diff that it was made against. I still haven't figured out how to pinpoint which revision/diff owns the defect, but usually we can play with it until it stays when edit is clicked.

However, this is painful.


author: Tini Good
body: Please note that we edit Defects to change Defect Classifications, which is why displaying the specific line of code isn't necessary.
FishEye is using an old jira URL
Asked by Andrew Sumner:

FishEye is using an old jira URL when clicking on a Jira number even though the application links have been updated. How do I force FishEye to point to my actual Jira instance?


Answers:
author: Felipe Kraemer
body: Hi Andrew,

I am afraid updating the "Display URL" in the Application Link is not enough, because the one which is indeed used is the one from "Application URL", which you cannot edit.

So, I think your best option is to delete the current application link and create a new one using the new JIRA URL as Application URL.
fisheye eclipse connector
Asked by Baboon:

Hello.It seems that i cant find the connector of fisheye for eclipse. I have downloaded the atlassian connector following the guide but in mylyn i don't find the fisheye connector. Where can i get this connector for my team? It seems it's a nice tool and we don't want to lose it. Thanks in advance.


Answers:
author: Felipe Kraemer
body: Hello,

According to [this page](https://confluence.atlassian.com/display/IDEPLUGIN/Installing+the+Eclipse+Connector) the Eclipse Connector is only compatible with FishEye 2.0.x, 2.1.x and 2.2.x, and with MyLin 3.8.4 and 3.9.x.

That's probably why you cannot find the connector of FishEye for Eclipse.
Search for strings with @ character
Asked by Jeff Thomas:

I'm trying to do a quick search for a string with an @ character, for example "@prod". The @ character seems to be removed from the query and only results with "prod" are included. Is there a way to escape or quote the "@prod" query to find results for that exact string?

I've tried:

* "@prod"
* '@prod'
* \\@prod


Answers:
author: Nick
body: The @ characters are currently stripped out of content and diff text in FishEye search indices.

I have created <https://jira.atlassian.com/browse/FE-4949> to change this behaviour however, since the @ character is commonly used now in languages such as java for annotations etc.

comments: author: Jeff Thomas
body: Thanks, Nick!
Fisheye/Crucible startup has become very slow
Asked by David Stallard:

We've been using F/C for years and it typically takes 2-3 minutes to start up. At some point in recent months, the startup became noticeably slower. For instance, when the log says "Starting plugin system...", it now takes about 10 minutes before moving on to the next step. Now we seem to have an additional long delay after getting the message telling us that we are not running the latest version (3.1.5 is the latest as I write this; we are currently running 3.0.1). The log has been sitting on this message for over 30 minutes, I'm not confident that it will ever complete the startup process.

I have verified that there is lots of disk space and memory available, and the CPU on the machine is mostly idle.

Any idea why startup times would have degraded, and what we can do to improve/fix it?


Answers:
author: Nick
body: The fix for <https://confluence.atlassian.com/display/FISHKB/Web+interface+does+not+load+after+upgrade+from+2.10.x+to+3.0> should definitely be in 3.1 and you shouldn't see the old plugin OSGi Caches getting in the way of the new plugin versions anymore.

When you see a slow FishEye/Crucible startup, please ensure you are starting with the --debug flag and take some thread dumps:

kill -3 \<PID\>

and create a support ticket at [support.atlassian.com](http://support.atlassian.com) to have the thread dumps and DEBUG logs investigated. Seeing what the threads are doing will make it easier for us to diagnose the exact cause of the issue.

Cheers,

Nick


author: David Stallard
body: When I first followed the procedure in the link from my first comment, I only renamed the osgi-cache directory since our FISHEYE_INST directory is external to the F/C install directory. I didn't think a complete reinstall was necessary in that case. When that didn't work, I went ahead with a complete reinstall (which took hours due to the amount of data to be copied over). Now F/C is working again, and it starts up much more quickly than we had become used to.

Another user comment says that this fix only works temporarily, but we'll keep our fingers crossed.


author: David Stallard
body: It seems that we are now running into the following issue, which explains a lot of our slow startup (it takes a long time to timeout initializing the wrong plugin versions), although the suggested course of action doesn't seem to fix it:

<https://confluence.atlassian.com/display/FISHKB/Web+interface+does+not+load+after+upgrade+from+2.10.x+to+3.0>