Details
-
Suggestion
-
Resolution: Fixed
-
None
-
None
Description
When indexing empty git repository warnings like this are logged:
[2014-04-10 01:34:20,744] WARN fisheye Empty remote heads list returned, which makes no sense. Skipping this fetch.
This is perfectly valid scenario when someone creates an empty repo in stash or bitbucket and starts indexing it before first changes are pushed. Especially with stash integration introduced in 3.4.
Also, see the comment below, indexing empty hg repository results in red error logged in the Admin / Repositories screen:
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: "hg --config extensions.felog=/Users/piotrs/dev/fe/output/dist/python/hg/hgfelog/hgfelog.py --config ui.verbose=false felog 0000000000000000000000000000000000000000 -p -m" in [/Users/piotrs/dev/fe/output/dist_inst/var/cache/bb-empty-hg/clone] com.atlassian.utils.process.ProcessException: java.lang.RuntimeException: Match failed: string [R:-1], pattern [R:([0-9]*)] java.lang.RuntimeException: Match failed: string [R:-1], pattern [R:([0-9]*)]
Also noticed on the search /qsearch page I get the following message:
Results might be incomplete The following repository is still indexing, and might therefore deliver incomplete results: DOX-virtual
for repositories which are empty