Mercurial missing changesets

FECRU: v3.3.1

Mercurial: v2.2

For some mercurial repositories I am missing changesets in fisheye/crucible. Hence, no reviews can be created for them.

In the log I have found following lines:

fisheye CommonChangeSetDAO-loadAttributes - Cannot resolve changeset parent id f514e84a38a51e025c16ea0bcc3e72f84a62f91d for changeset d497933a8aefca7765f60afc5f6f333faa0c5f81

fisheye HgClientManifestDAO$1-processLine - While resolving manifest d497933a8aefca7765f60afc5f6f333faa0c5f81.Cannot find file revision in index: path = [some-path], revision = f514e84a38a51e025c16ea0bcc3e72f84a62f91d

but the changeset is available in hg log

changeset:   8330:d497933a8aef
branch:      Release-XXX
parent:      8324:13cb09feaf86
parent:      8329:f514e84a38a5
user:        [user]
date:        Mon Mar 10 09:58:07 2014 +0100
summary:     [summary]

changeset:   8329:f514e84a38a5
branch:      XXX-1212
parent:      8324:13cb09feaf86
user:        [user]
date:        Mon Mar 10 09:57:19 2014 +0100
summary:     [summary]

Have found some issues which may be related but no solution was provided there

Any solution for this?


2 answers

1 accepted

The problem was solved by changing OS language to english and using locale en_US.UTF-8 in OS and on fisheye startup.

0 votes
Tom Davies Atlassian Team Mar 11, 2014

Do you have any commits on your default branch? There is also this bug FE-5087 which affects Mercurial repositories.

There is a commit on default branch about two weeks ago

changeset:   8268:e3d2b799d798
user:        [user]
date:        Tue Feb 25 22:10:25 2014 +0100
summary:     [summary]

I have taken a closer look which changesets are not availabel but I do not see what they have in common

  • different users
  • different files and file types where touched
  • different commit count to the branch

The work flow is like that

  1. create a branch for the task
  2. do work (some commits) and test
  3. merge created branch back to the release branch

A fisheye screenshot with example can be found here

have now created a repo with which this error can be reproduced on our fisheye installation

Repo was imported in fisheye and the branches Test-1 to Test-24 are missing. branch default and Release-14.3 are available

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

627 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot