Skip to content
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

Empty Port File #173

Open
sangaline opened this issue Jun 28, 2017 · 0 comments
Open

Empty Port File #173

sangaline opened this issue Jun 28, 2017 · 0 comments

Comments

@sangaline
Copy link

I've been frequently running into this error:

Error detected while processing function provider#python3#Call:                                                        
line   18:                                                                                                             
Traceback (most recent call last):                                                                                     
  File "<string>", line 1, in <module>                                                                                 
  File "/home/sangaline/.config/nvim/plugged/tern_for_vim/script/tern.py", line 246, in tern_sendBufferIfDirty         
    if curSeq > vim.eval("b:ternBufferSentAt") and tern_sendBuffer():                                                  
  File "/home/sangaline/.config/nvim/plugged/tern_for_vim/script/tern.py", line 234, in tern_sendBuffer                
    port, _portIsOld = tern_findServer()                                                                               
  File "/home/sangaline/.config/nvim/plugged/tern_for_vim/script/tern.py", line 98, in tern_findServer                 
    port = int(open(portFile, "r").read())                                                                             
ValueError: invalid literal for int() with base 10: ''  

where it appears that the port file is empty. The error is displayed when switching buffers.

Aside from how the port file gets empty in the first place, perhaps this is something that tern_for_vim should be able to recover from?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant