Uploaded image for project: 'Bitbucket Server'
  1. Bitbucket Server
  2. BSERV-11791

Git 2.21+: Ref sync produces verbose logging when requested ref cannot be found

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Low
    • Resolution: Fixed
    • Affects Version/s: 6.2.0, 6.3.0
    • Fix Version/s: 6.4.0, 6.2.3, 6.3.2
    • Component/s: None
    • Labels:
      None

      Description

      Issue Summary

      When ref sync (fork syncing) applies upstream changes to forks, if any refs are updated and then quickly deleted the fetch can fail because the ref no longer exists. The ref sync code includes handling for this case, to log a clear message without spamming the logs with unnecessary stack traces. Git 2.21+ include textual changes which break that handling, however.

      Functionality is not impacted by this issue. Ref sync produces identical results with Git 2.21+ to Git 2.20 and earlier. The difference is that update-then-delete scenarios on Git 2.21+ will produce more verbose logging.

      Environment

      • Git 2.21

      Workaround

      No workaround is available or necessary. There is no functional impact from this issue; it's purely cosmetic (logging).

        Attachments

          Activity

            People

            Assignee:
            bturner Bryan Turner
            Reporter:
            mdiberardino@atlassian.com Matthieu Di Berardino
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: