Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-7553

Accessing repositories in a project with key SCM fails

      Summary

      Trying to clone a repo within a project with the SCM or REST slug fails.

      Steps to Reproduce

      1. Set up a Stash instance with a project key SCM or REST
      2. Try to clone a repo from that project

      Expected Results

      It should work (i.e. Stash 3.4.0)

      $ git clone http://admin@localhost:7990/stash/scm/scm/rep_1.git
      Cloning into 'rep_1'...
      remote: Counting objects: 79, done.
      remote: Compressing objects: 100% (47/47), done.
      remote: Total 79 (delta 14), reused 0 (delta 0)
      Unpacking objects: 100% (79/79), done.
      Checking connectivity... done.
      

      Actual Results

      On Stash 3.10.2 it doesn't and the following output is shown:

      $ git clone http://admin@localhost:7990/stash/scm/scm/rep_1.git
      Cloning into 'rep_1'...
      fatal: remote error: Repository does not exist
      The requested repository does not exist, or you do not have permission to
      access it.
      

      Solution / Workaround

      Disable the "Stream Guard" plugin and perform a new clone.

            [BSERV-7553] Accessing repositories in a project with key SCM fails

            Summary

            Stash 3.10.0 introduced a bug where projects with the key scm or rest cannot be used by git over HTTP.

            If you encounter this issue before a fix has been released you can workaround this issue by disabling the "Stream Guard" plugin. The plugin was added to suppress errors the client disconnects before the operation is complete, Stash will still function correctly with this plugin disabled.

            Scott Goodhew (Inactive) added a comment - Summary Stash 3.10.0 introduced a bug where projects with the key scm or rest cannot be used by git over HTTP. If you encounter this issue before a fix has been released you can workaround this issue by disabling the "Stream Guard" plugin. The plugin was added to suppress errors the client disconnects before the operation is complete, Stash will still function correctly with this plugin disabled.

            Adam Brokes added a comment - - edited

            Reproducible with this error message:

            # ~ » git clone http://admin@host:7990/stash/scm/scm/scm.git
            Cloning into 'scm'...
            Password for 'http://admin@host:7990':
            fatal: remote error: Repository does not exist
            The requested repository does not exist, or you do not have permission to
            access it.
            

            This is happening only if the project key = scm.

            Adam Brokes added a comment - - edited Reproducible with this error message: # ~ » git clone http: //admin@host:7990/stash/scm/scm/scm.git Cloning into 'scm' ... Password for 'http: //admin@host:7990' : fatal: remote error: Repository does not exist The requested repository does not exist, or you do not have permission to access it. This is happening only if the project key = scm .

            Nick added a comment -

            Thanks, snappleguy for letting us know. We will be looking into this and try and get a fix out soon.

            Nick added a comment - Thanks, snappleguy for letting us know. We will be looking into this and try and get a fix out soon.

              rfriend rikf
              d206c1afa64f Jeff Koss
              Affected customers:
              2 This affects my team
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: