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

Fisheye should handle this specific git error - blame::find_origin (D)- more gracefully

XMLWordPrintable

    • 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.

      Problem Definition

      • During indexing of a repo Fisheye will use git to calculate blame
      • If git is unable to find blame origin for a commit it may return the following fatal: internal error in blame::find_origin (D)
      • The index of the repo will not complete if this error is encountered

      Suggested Solution

      • Fisheye should be able to handle this error more gracefully with perhaps a clear call to action to disable blame calculation at the appropriate level ie. per repo by disabling "store diff info" setting or system wide via a system property - fisheye.blame.calc.enable

      Workaround

      • Disabling blame calculation should allow the repo to index successfully with the caveat that LoC will also be disabled

            [FE-7269] Fisheye should handle this specific git error - blame::find_origin (D)- more gracefully

            Marek Parfianowicz added a comment -
            Atlassian Update – 10 January 2022

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not Being Considered.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Kind regards
            Marek Parfianowicz
            Development Team Lead

            Marek Parfianowicz added a comment - Atlassian Update – 10 January 2022 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not Being Considered . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Kind regards Marek Parfianowicz Development Team Lead

              Unassigned Unassigned
              nhansberry Nate Hansberry
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: