Actions
Defect #8767
closed
Git: diff is a 404
Status:
Closed
Priority:
Low
Assignee:
-
Category:
SCM
Target version:
-
Start date:
2011-07-08
Due date:
% Done:
0%
Estimated time:
Resolution:
Invalid
Affected version:
Description
Here's an excerpt from my production.log. I can visit the revision just fine, but visiting its diff gives a 404 error.
Processing RepositoriesController#revision (for 207.172.223.249 at 2011-07-07 17:54:19) [GET]
Parameters: {"rev"=>"ab345492332bea411da869592a7d2a6fe13a3361", "action"=>"revision", "id"=>"embt", "controller"=>"repositories"}
Rendering template within layouts/base
Rendering repositories/revision
Completed in 69ms (View: 57, DB: 3) | 200 OK [https://hub.boostpro.com/projects/embt/repository/revisions/ab345492332bea411da869592a7d2a6fe13a3361]
Processing RepositoriesController#diff (for 207.172.223.249 at 2011-07-07 17:54:34) [GET]
Parameters: {"rev"=>"ab345492332bea411da869592a7d2a6fe13a3361", "action"=>"diff", "id"=>"embt", "controller"=>"repositories"}
Rendering template within layouts/base
Rendering common/error (404)
Completed in 82ms (View: 50, DB: 4) | 404 Not Found [https://hub.boostpro.com/projects/embt/repository/revisions/ab345492332bea411da869592a7d2a6fe13a3361/diff]
Updated by Toshi MARUYAMA almost 13 years ago
- Subject changed from /diff is a 404 to Git: diff is a 404
- Status changed from New to Closed
- Priority changed from High to Low
"revisions/hash_id" reads DB stored infos.
If you remove revisions from repository (eg. git push :delete_branch, git branch -D detele_branch, git gc), diff returns 404.
But, DB stored revisions remains.
Updated by Dave Abrahams almost 13 years ago
- Status changed from Closed to Reopened
I have not deleted any revisions from the repository. In fact, that revision is at the head of the repository's "work" branch.
Updated by Toshi MARUYAMA almost 13 years ago
- Status changed from Reopened to Closed
- Resolution set to Cant reproduce
I added unit adapter tests, and I can't reproduce.
Updated by Dave Abrahams almost 13 years ago
The problem was on our end: apache needed to restart after the path to git changed on the server. Sorry about the noise!
Updated by Toshi MARUYAMA almost 13 years ago
- Resolution changed from Cant reproduce to Invalid
Actions