-
Bug
-
Resolution: Fixed
-
Low
-
3.10.2
-
Linux standalone, JDK 1.8.0_31
Summary
Trying to clone a repo within a project with the SCM or REST slug fails.
Steps to Reproduce
- Set up a Stash instance with a project key SCM or REST
- 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.
- duplicates
-
BSERV-7594 Accessing repositories in a project with key SCM fails
-
- Closed
-
- is duplicated by
-
BSERV-7687 When setting Project key to SCM, HTTPS access is broken.
-
- Closed
-
- is blocked by
-
PLUG-1148 DelegatingPluginFilter consumes part of PathInfo when it shouldn't
- Done
(1 mentioned in)
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.