-
Notifications
You must be signed in to change notification settings - Fork 86
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
Cannot read anaconda-mode server response #360
Comments
You could try the fork by @falloutphil referenced in #335 (recently merged then reverted). |
Hi @ziyangli - can you explain exact steps on how to recreate this issue? It's strange that you're getting a timeout error rather than a concrete refusal, but I'd need more details on the remote connection and the operation you are doing before I can comment. Can you also confirm if you experience problems on the current version in MELPA (which does not contain my latest merge)? |
@falloutphil ,thank you for your reply. I am running the latest Emacs and anaconda-mode on a newly installed ubuntu18.04 in Vmware. No special steps. I just open a python file and then get this error message. In fact I guess the reason could be related to my proxy settings, which looks like this:
|
I comment out the proxy settings above and now anaconda mode works. So indeed the reason is my proxy setting. Does anybody know how to correctly use the proxy since I still need the proxy to update packages. |
Thanks for the extra info @ziyangli. First thing when you say you open a Python file - so I'm 100% clear - this is a remote Python file, opened using Tramp, from an emacs session running on your vmware Ubuntu 18.04 server, and not a local Python file stored locally on your vmware Ubuntu server? Sorry it's an obvious question - but essential to be certain what is happening! Assuming you are opening a remote file as I describe above, I have a good idea what this might be:
So the reason it originally worked with your HTTP proxy, was actually a bug in the code that I have fixed! Although this doesn't help you much! Nevertheless, I think it's possible to support both. Outside of emacs - i.e. from the Ubuntu vmware terminal, exactly how would you SSH onto your remote server where the Python files are stored? Are you using a proxy for this, for example? If you don't mind giving me the command line and/or any relevant bits from your SSH config file that will help me better understand the problem I have a much better chance of offering a good solution The problem probably is that the HTTP RPC request will no longer go through your HTTP Proxy, and instead is traveling through the SSH tunnel to the remote server. Either the tunnel is not being created, or the remote server is not routing the HTTP traffic correctly, but it's hard to know exactly what. The most straightforward, but insecure fix is have a "No Proxy For Remote RPC" custom setting, which simply doesn't create an SSH tunnel at all, and attempts a direct HTTP connection - mimicking exactly what the old code was doing. I can implement this easy enough, but like I said it's not secure and packets will travel in cleartext across the internet. A better solution is to diagnose exactly what is the problem in your case and perhaps add further configuration to handle more complicated proxy cases. |
@ziyangli is this issue still present? |
@ziyangli I just fixed a very similar issue. IME, proxy settings work better in emacs if you set the |
@haystack-ia commented on Mar 12, 2020, 5:21 PM GMT+3:30:
What exactly do you set |
@NightMachinary |
I have checked there are similar issues, but no solutions are given. Hope somebody can help me fix this problem.
The text was updated successfully, but these errors were encountered: