Commits can't be found that exist on both remote and sidecar mesh

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 8.0.0
    • Component/s: Mesh
    • None
    • Severity 3 - Minor

      Issue Summary

      When searching for commits that exist on both a sidecar mesh node and also a remote meshnode, the commits can't be found when searching for them.

      Steps to Reproduce

      1. Create a repo on a mesh sidecar (Repo A)
      2. Create a repo on remote mesh nodes (Repo B)
      3. Splice commits from Repo A, to Repo B, so the commits exist on both repos
      4. Search for one of the shared commits using the searchbar

      Expected Results

      The commit is returned

      Actual Results

      The following exception is thrown:

          "errors": [
              {
                  "message": "There is no repository with ID ds/0/h/1b19d240aacb4e78f92d/r/8526",
                  "exceptionName": "com.atlassian.bitbucket.repository.NoSuchRepositoryException"
              }
          ] 

      Workaround

      Migrate repo A to remote mesh.

            Assignee:
            Unassigned
            Reporter:
            David Jansons
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: