Community
Participate
Working Groups
- fresh workspace - linked to a subfolder of my git repo (folder org.eclipse.orion.client.core -> linked to c:\_git\orion\org.eclipse.orion.client\bundles\org.eclipse.orion.client.core) - select "Git Log" from org.eclipse.orion.client.core - success. - select "Git Log" from the subfolder "static" - empty log page. The server reports no children. (console screen snaps attached)
Created attachment 194204 [details] console showing successful get when doing gitlog on file/A/?page=1
Created attachment 194205 [details] no children from file/A/static/?page=1
marking M7 as this seems quite important. Libing and Szymon told me this morning that it was working for them. I started with a clean workspace to ensure that it wasn't something wrong on my end. Let me know if you need me to debug...
I cloned a github repo and in that repo, git log works for individual files that have changed. Is it possible that it only works if you cloned the repo from Orion? There is still something fishy about the self-hosting scenario, where you link to a repo that you cloned from a non-jgit repo. It smacks of a jgit bug somewhere to me. Reminds me of that autocrlf problem from before...people who use jgit repos don't see a problem, but I see it all the time (because my repo was cloned by a different tool.) Maybe the answer is "clone the repo with orion or jgit" for now, but I'd like to understand the problem.
I've just cloned the orion client repo from eclipse.org using Orion, and the git log works for the most part. (There are some timeouts, opened bug 344056 for that). So I believe that this bug is specific to git repositories that were not cloned by jgit. I have no idea what the specific difference in the repo would be. I'll be keeping my msysgit repo around if anyone wants to log into my Orion setup and see what's happening.
removing milestone since this is not a general problem and not present in the orion hub usage.
Created attachment 194523 [details] a zip file exported from Libing's server Git log is empty on the attached zip file , which represents a folder on my server. I created this git repo by cmd line and used it for the merge test last week. But today I found out that I was not able to us git log any more . I hope it can help on figuring out what happened behind the scene.
(In reply to comment #7) > Git log is empty on the attached zip file , which represents a folder on my > server. > I created this git repo by cmd line and used it for the merge test last week. > But today I found out that I was not able to us git log any more . > I hope it can help on figuring out what happened behind the scene. That sounds similar to my case, too. The command line repo seems to work at first, and at some point it stops working.
(In reply to comment #0) > - fresh workspace > - linked to a subfolder of my git repo (folder org.eclipse.orion.client.core -> > linked to > c:\_git\orion\org.eclipse.orion.client\bundles\org.eclipse.orion.client.core) > - select "Git Log" from org.eclipse.orion.client.core > - success. > - select "Git Log" from the subfolder "static" > - empty log page. > > The server reports no children. (console screen snaps attached) This works fine to me, as long as the change is somewhere under 'static' :) Here is what I see in the console: GET http://localhost:8080/git/status/file/r/static/ { "Added": [], "Changed": [], "CommitLocation": "/git/commit/HEAD/file/r/", "Conflicting": [], "IndexLocation": "/git/index/file/r/", "Missing": [], "Modified": [{ "Git": { "CommitLocation": "/git/commit/HEAD/file/r/bundles/org.eclipse.orion.client.core/static/js/auth.js", "DiffLocation": "/git/diff/Default/file/r/bundles/org.eclipse.orion.client.core/static/js/auth.js", "IndexLocation": "/git/index/file/r/bundles/org.eclipse.orion.client.core/static/js/auth.js" }, "Location": "/file/r/bundles/org.eclipse.orion.client.core/static/js/auth.js", "Name": "bundles/org.eclipse.orion.client.core/static/js/auth.js", "Path": "../bundles/org.eclipse.orion.client.core/static/js/auth.js" }], "Removed": [], "Untracked": [] } Please reopen the bug if you're able to change these statements "today I found out that I was not able to us git log any more ." (comment 7), "at some point it stops working." (comment 8) into a set of reproducible steps.
