Details
-
Bug
-
Resolution: Fixed
-
Low
-
3.3.0
-
None
Description
With stacks like
com.cenqua.fisheye.infinitydb.InfinityDbWrapper.exists(InfinityDbWrapper.java:75) com.cenqua.fisheye.infinitydb.EavEntityCu.deleteLong(EavEntityCu.java:276) com.cenqua.fisheye.rep.impl.CommonChangeSetDAO.unmarkAllAsAncestorOfBranch(CommonChangeSetDAO.java:886) com.atlassian.fisheye.git.GitScanner.onBranchHeadUpdated(GitScanner.java:624) com.atlassian.fisheye.git.GitScanner.updateRemovedBranches(GitScanner.java:311) com.atlassian.fisheye.git.GitScanner.fetchLatest(GitScanner.java:238) com.atlassian.fisheye.dvcs.DvcsScanner.updateLocalRepoClone(DvcsScanner.java:143) com.cenqua.fisheye.rep.BaseRepositoryScanner.ping(BaseRepositoryScanner.java:69) com.cenqua.fisheye.rep.BaseRepositoryEngine.doSlurp(BaseRepositoryEngine.java:86) com.cenqua.fisheye.rep.RepositoryEngine.slurp(RepositoryEngine.java:414) com.cenqua.fisheye.rep.ping.IndexingPingRequest.doRequest(IndexingPingRequest.java:27) com.cenqua.fisheye.rep.ping.OneOffPingRequest.doRequest(OneOffPingRequest.java:18) com.cenqua.fisheye.rep.ping.PingRequest$1.run(PingRequest.java:55)
This is caused by updating the repository cache to mark (or unmark) changesets as belonging to the specified branch.