-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Operations (fetch, push, etc) never complete, no error #68
Comments
check preferences>team>git>timeout. the default is 30 seconds for me, but I guess you have the same. besides that, we can only continue to investigate if provide us a stack dump: https://www.baeldung.com/java-thread-dump (the jstack option is the most simple one). that would show us where the code "hangs" when nothing happens anymore. |
Here you go, I do have the 30 seconds timeout setting. This is over 30 minutes hanging there. |
Looks like we need a jgit specialist here, maybe @tomaswolf . It is still fetching, and the TimeoutStream doesn't timeout, as it seems (lines 1359ff.):
|
There is also
If you look at the code in The javadoc on @castortech : A completely different question is why the read just hangs. I see that you are using SSH to fetch. Are you using an external SSH (environment variable GIT_SSH set)? Look at Help->About Eclipse, "Installation Details", "Configuration" tab. What is the value of environment variable GIT_SSH? Could there be any firewalls that affect the connection? You wrote this occurred on a new laptop. Do you still have your old laptop? If you install Eclipse 2024-12 on the old one, does fetching via SSH from that repository work? |
That the hang is in |
It is set indeed, both on the old and the new: GIT_SSH=C:\Windows\System32\OpenSSH\ssh.exe The old one, I did a fetch and no issue at all. Note that this is with 24-09, but on the new I had the issue on 24-09 and then updated to make sure that I reported on the current version if it persisted. There are no firewall. Both laptops are on the same network, and the new laptop works fine with Git Bash. Thanks |
So there are several things to examine:
|
Note that the fetch is hanging at very beginning. It did open the SSH channel and is waiting to read the very first line from the upstream git server. But somehow nothing is coming in, plus the timeout interrupt doesn't appear to be working. But the timeout not working is a secondary problem; your real problem is that no data is being received in the first place from that ssh.exe. If you can, also try to check which SSH executable command-line git in git bash is using. git bash comes with its own stock OpenSSH; perhaps it's using that. |
As mentioned the SSH executable for GitBash is different. If I switch to it, the it fails fast with: |
So, git bash with the SSH executable provided in git bash works, but Eclipse with the MS Window OpenSSH port hangs. Try running that SSH directly in a terminal. I wonder if it's something crazy such as https://bugs.eclipse.org/bugs/show_bug.cgi?id=515354 . (I.e., that it asks for some interactive confirmation the first time it's being run.) Try
Do you have the host key in your known_hosts file? (Probably, if all files under .ssh are identical.) |
Trying in terminal:
and looking at the mentioned issue, if I run it, I again get asked for the passphrase:
I am starting to think that it's related to the need to enter a passphrase. And maybe the old version had it "stored" somewhere. |
This is definitely the root cause of the hang. I don't know if anything can be done about the interrupt not interrupting the read. |
Version
7.1.0.202411261347-r
Operating System
Windows
Eclipse version
2024-12 (same with 2024-09)
Bug description
After moving to new laptop, Git operations like fetch, push that have to go over the network never complete (waited 30 minutes) and never report any error.
On the 2024-09 installation, I tried deleting the secure storage and got no changes.
Since there are no errors, I don't know where to start. I need to say that my GitBash works just fine and this is what I've been using for the last few weeks, but not the most convenient for most operations.
Actual behavior
No errors or stack trace
Expected behavior
Operation completes normally or at the very least reports an error
Relevant log output
Other information
No response
The text was updated successfully, but these errors were encountered: