Problem processing revisions from repo <REPO_NAME>... fatal: no such path <REPO_NAME> in <COMMIT_HASH>
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
The following entry appears on the fisheye-debug-<DATE>.log:
1
2
2012-05-23 15:09:13,220 ERROR - Problem processing revisions from repo <REPO_NAME> due to class com.cenqua.fisheye.rep.DbException - com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while communicating with VCS: error: unable to find <COMMIT_HASH>
fatal: no such path <REPO_NAME> in <COMMIT_HASH>Cause
This is caused due a known bug. Please see: https://jira.atlassian.com/browse/FE-3122
Resolution
As a workaround, disable the "Store Diff Info" functionality for the affected repository: Store diff info
Related
Git repository indexing fails because it cannot delete the branch which you are currently on
Was this helpful?