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

Pullrequest are declined because of a gap in the PR history

    XMLWordPrintable

    Details

      Description

      Atlassian status as of November 2020

      Hi everyone,

      Thanks for voting and commenting on this bug. Your input in the comments helps us understand how this affects you and how to reproduce this issue.

      We fixed numerous subtle bugs in the rescoping process and this has resulted in a significant reduction of this problem in our internal environments. We encourage to upgrade to any of the fix versions mentioned in this ticket and provide feedback if the issues have been resolved.

      In addition, take a look at BSERV-Howtoself-serviceanddebugrescopingproblems-051120-0256.pdf for more information about what exactly has been fixed and ways to further diagnose and fix this class of problems.

      Cheers,
      Wolfgang Kritzinger

      Senior Developer - Bitbucket Server

      Important information

      Bitbucket < 5.10
      If you are facing this issue and running a version of Bitbucket earlier than 5.10, please upgrade to a newer version as discussed in this comment

      Shared filesystem
      If using a shared filesystem, make sure that the mount options match the ones described on the Install Bitbucket Data Center - Provision the shared database, filesystem, and Elasticsearch nodes page:

      bitbucket-san:/bitbucket-shared /var/atlassian/application-data/bitbucket/shared nfs lookupcache=pos,noatime,intr,rsize=32768,wsize=32768 0 0
      

      Pull requests get declined because of a gap in the pullrequest history

      [bitbucket-server] 2018-08-07 09:29:54,097 WARN [pull-request-rescoping:thread-1] c.a.s.i.p.r.PullRequestRescopeChain Project/repository[2262]#12862: A gap was detected in the pull request history: ({user: <unknown>, date: <unknown>, from-ref: {old-hash: 6161ef159de80e5a649c903d59a4c4aa8584f678, new-hash: deleted-ref}, to-ref: <unchanged>}). Attributing the scope change to user userNAme and setting the rescope date to Tue Aug 07 09:29:52 MSK 2018 based on known changes
      

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              tkenis tomas
              Votes:
              25 Vote for this issue
              Watchers:
              40 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Backbone Issue Sync

                  • Synchronized with BBSJAC
                    Synced with:
                    BBSJAC-275
                    Issue sync status:
                    UP TO DATE
                    Last received:
                    Last sent: