-
Bug
-
Resolution: Fixed
-
Medium
-
4.6.2
-
None
Summary
When accessing files under "subtree" in a repository from the UI, 500 error is shown.
This problem only happened immediately after adding "subtree", however, if we changed the problematic files even once, the files were shown correctly.
Steps to Reproduce
- Create a repository which is named "main"
- Clone "main" repository on local, commit some changes and push the changes to the repository
- Create a repository which is named "sub"
- Clone "sub" repository on local, and execute the following commands
$ touch test.txt $ git add test.txt $ git commit -a -m "added test.txt $ git push
- Go to the directory where "main" repository" locates on your local
- Execute the following commands
$ git remote add sub <BBS_BASE_DIR>/scm/<PROJECT_NAME OR USER_NAME>/sub.git $ git subtree add --prefix=sub/ sub master $ git push
- Go to sub/test.txt in "main" repository on the UI
Expected Results
sub/test.txt should be shown correctly on the UI.
Actual Results
500 error was shown.
Notes
- This problem didn't happen on Stash 3.6.1 at least
- After committing some changes to the problematic files, they were shown correctly
Workaround
As I mentioned above, reflecting some changes to the files solve this problem.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|