Community
Participate
Working Groups
I've been having trouble cloning the git orion client repo on the latest code. I get the progress message saying it's cloning, and some git directories get created in my workspace, but nothing happens and the progress message never comes back. Thinking I may have mistyped my credentials, I tried again with a known-to-be-bogus set of credentials. Same symptom. The error should return to the progress area saying that the credentials failed. (and ideally the files that were created get cleaned up). I think I've seen a bug like this go by, but couldn't find it. Sorry if this is a dup.
I think I'm wrong about the original problem. I think that the clone is simply taking a long time. I tried a smaller repo (with what I thought were bogus credentials) and it worked, which makes sense because I assume the clone itself can happen without credentials. So, I'll rename this bug and suggest that we actually try to report some kind of progress back from the server, even it's just a "still transferring" files and some timestamp that would show me that it's still working.
The clone took 32 minutes. I followed progress by going to the .git/objects directory in the cloned folder and periodically checking its size...
(In reply to comment #2) > The clone took 32 minutes. > I followed progress by going to the .git/objects directory in the cloned folder > and periodically checking its size... That sounds awful, but could you post the clone time when using the command line or eGit, for reference? You are a good test case because the remote git repository is in Ottawa, which is close for me but far for you. If we are significantly worse than eGit or command line we might need to dig into that.
I should also mention that jgit API has no facility for progress reporting, so I'm not sure we can give accurate progress update messages or % completion from the server. I suppose we could send something like elapsed time so you know we're not dead.
(In reply to comment #4) > I should also mention that jgit API has no facility for progress reporting, so > I'm not sure we can give accurate progress update messages or % completion from > the server. I suppose we could send something like elapsed time so you know > we're not dead. Yes, exactly, elapsed time would have been great. In bug 344012 when I had multiple clones updating the progress area, that was the first significant clue that my clone was still working. Since the same message gets posted right now during a clone, you can't tell that it's still doing anything.
(In reply to comment #3) > (In reply to comment #2) > > The clone took 32 minutes. > > I followed progress by going to the .git/objects directory in the cloned folder > > and periodically checking its size... > > That sounds awful, but could you post the clone time when using the command > line or eGit, for reference? You are a good test case because the remote git > repository is in Ottawa, which is close for me but far for you. If we are > significantly worse than eGit or command line we might need to dig into that. I will try this today. The same clone later in the day was 25 min or so. Eclipse.org seemed very slow in general during that time.
opened bug 344143 for performance discussion. (and for the record, git gui has no progress during a clone either....)
Susan, is this bug still present? The new progress service keeps the task in the list as long as it's running and a little longer. For old tasks you can go to operations page and see what was their result.
yes, this is fixed by the new operations task list. The problem before was just seeing that static message and not knowing if anything was happening. Now I can look at the time started and status in the ops list.
