Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-5148

indexing empty git/hg repositories results in logged warnings and fake errors/warnings in UI

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 3.5.0
    • None
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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

            [FE-5148] indexing empty git/hg repositories results in logged warnings and fake errors/warnings in UI

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3338599 ] New: JAC Suggestion Workflow 3 [ 3642894 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Marek Parfianowicz made changes -
            Workflow Original: Simple Restricted [ 2952045 ] New: JAC Suggestion Workflow [ 3338599 ]
            Assignee Original: Conor [ cmacneill ]
            Issue Type Original: Task [ 3 ] New: Suggestion [ 10000 ]
            Owen made changes -
            Workflow Original: FECRU Development Workflow - Triage - Restricted [ 1518177 ] New: Simple Restricted [ 2952045 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Owen made changes -
            Workflow Original: FECRU Development Workflow - Triage [ 944739 ] New: FECRU Development Workflow - Triage - Restricted [ 1518177 ]
            Piotr Swiecicki made changes -
            Workflow Original: FECRU Development Workflow (Triage) [ 680249 ] New: FECRU Development Workflow - Triage [ 944739 ]
            Conor (Inactive) made changes -
            Fix Version/s New: 3.5.0 [ 40008 ]
            Fix Version/s Original: 3.6.0 [ 44209 ]
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]
            Conor (Inactive) made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Conor (Inactive) made changes -
            Global Rank New: Ranked higher
            Conor (Inactive) made changes -
            Sprint Original: 3.6.0-m2, 3.6.0-m3 [ 1553, 1583 ] New: 3.6.0-m2, 3.6.0-m3, 3.6.0-m4 [ 1553, 1583, 1618 ]
            Piotr Swiecicki made changes -
            Global Rank New: Ranked higher

              Unassigned Unassigned
              pswiecicki Piotr Swiecicki
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: