Youcompleteme: Error detected while processing function youcompleteme#Enable..<SNR>64_SetUpPython:

[SongGithub]

Issue Details

describe how to reproduce the bug you are experiencing
step: just turn on the vim, then I have the error msg!

Error Description:
Recently I installed pip3, lxml and its required libraries to compile the Lxml. Then the error happens every time I turn on VIM:

Error detected while processing function youcompleteme#Enable..64_SetUpPython:
line:33
/usr/local/lib/python2.7/dist-packages/cffi/model.py:526: UserWarning: 'point_conversion_form_t' has no values explicitly defined; next version will refuse to guess which integer type it is meant to be (unsigned/signed, int/long)
line 33:
% self._get_c_name())

The error msg can be skipped by hitting Enter, then I can use VIM as usual. So it is no more than annoying.

Issue Prelude

Please complete these steps and check these boxes (by putting an x inside
the brackets) _before_ filing your issue:

• [ x] I have read and understood YCM's [CONTRIBUTING][cont] document.
• [ x] I have read and understood YCM's [CODE_OF_CONDUCT][code] document.
• [ x] I have read and understood YCM's [README][readme], especially the
  [Frequently Asked Questions][faq] section.
• [ x] I have searched YCM's issue tracker to find issues similar to the one I'm
  about to report and couldn't find an answer to my problem. ([Example Google
  search.][search])
• [ x] If filing a bug report, I have included the output of vim --version.
• [ x] If filing a bug report, I have included the output of :YcmDebugInfo.
• [ DO NOT KNOW HOW TO GENERATE THE OUTPUT] If filing a bug report, I have included the output of
  :YcmToggleLogs stderr.
• [x ] If filing a bug report, I have included which OS (including specific OS
  version) I am using.
• [ x] If filing a bug report, I have included a minimal test case that reproduces
  my issue.
• [ x] I understand this is an open-source project staffed by volunteers and
  that any help I receive is a selfless, heartfelt _gift_ of their free time. I
  know I am not entitled to anything and will be polite and courteous.
• [ x] I understand my issue may be closed if it becomes obvious I didn't
  actually perform all of these steps.

Thank you for adhering to this process! It ensures your issue is resolved
quickly and that neither your nor our time is needlessly wasted.

System environment details

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Mar 31 2015 23:35:24)
Included patches: 1-488, 576
Modified by [email protected]
Compiled by [email protected]
Huge version without GUI. Features included (+) or not (-):
+acl +farsi +mouse_netterm +syntax
+arabic +file_in_path +mouse_sgr +tag_binary
+autocmd +find_in_path -mouse_sysmouse +tag_old_static
-balloon_eval +float +mouse_urxvt -tag_any_white
-browse +folding +mouse_xterm +tcl
++builtin_terms -footer +multi_byte +terminfo
+byte_offset +fork() +multi_lang +termresponse
+cindent +gettext -mzscheme +textobjects
-clientserver -hangul_input +netbeans_intg +title
-clipboard +iconv +path_extra -toolbar
+cmdline_compl +insert_expand +perl +user_commands
+cmdline_hist +jumplist +persistent_undo +vertsplit
+cmdline_info +keymap +postscript +virtualedit
+comments +langmap +printer +visual
+conceal +libcall +profile +visualextra
+cryptv +linebreak +python +viminfo
+cscope +lispindent -python3 +vreplace
+cursorbind +listcmds +quickfix +wildignore
+cursorshape +localmap +reltime +wildmenu
+dialog_con +lua +rightleft +windows
+diff +menu +ruby +writebackup
+digraphs +mksession +scrollbind -X11
-dnd +modify_fname +signs -xfontset
-ebcdic +mouse +smartindent -xim
+emacs_tags -mouseshape -sniff -xsmp
+eval +mouse_dec +startuptime -xterm_clipboard
+ex_extra +mouse_gpm +statusline -xterm_save
+extra_search -mouse_jsbterm -sun_workshop -xpm
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -I/usr/include/tcl8.6 -D_REENTRANT=1 -D_THREAD_SAFE=1 -D_LARGEFILE64_SOURCE=1
Linking: gcc -L. -Wl,-z,relro -L/build/ruby2.1-64qTCU/ruby2.1-2.1.5/debian/lib -fstack-protector -rdynamic -Wl,-export-dynamic -Wl,-E -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim -lm -ltinfo -lnsl -lselinux -lacl -lattr -lgpm -ldl -L/usr/lib -llua5.2 -Wl,-E -fstack-protector -L/usr/local/lib -L/usr/lib/x86_64-linux-gnu/perl/5.20/CORE -lperl -ldl -lm -lpthread -lcrypt -L/usr/lib/python2.7/config-x86_64-linux-gnu -lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions -L/usr/lib/x86_64-linux-gnu -ltcl8.6 -ldl -lz -lpthread -lieee -lm -lruby-2.1 -lpthread -lgmp -ldl -lcrypt -lm

Printing YouCompleteMe debug information...
-- Server has Clang support compiled in: False
-- Server running at: http://127.0.0.1:37722
-- Server process ID: 28838
-- Server logfiles:
-- /tmp/ycm_temp/server_37722_stdout.log
-- /tmp/ycm_temp/server_37722_stderr.log

OS=Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) x86_64 GNU/Linux

[puremourning]

I suspect this is an artefact of your python installation.

Try creating an empty virtualenv and running within that. If the problem goes away it is some python package you have installed. I don't believe that the package referenced in the traceback has anything to do with YCM.

The only think I can think of is if it is like https://github.com/Valloric/YouCompleteMe/issues/2024 and we should be using future.<something> where we aren't. Other than that it's not obvious how this can be caused by YCM (which relies on no external packages afaik).

[SongGithub]

@puremourning
Thanks for reply.
I tested it: Created 2 virtualenv with pip and Python3.4/2.7, and tried to start the VIM. Result: Same error and warning messages pop-up, which means it does not 'goes away'

[puremourning]

I still think this is an issue with the packages on your system, and not something directly related to YCM.

For example: https://github.com/pyca/pyopenssl/issues/392, https://bitbucket.org/cffi/cffi/issues/234/cffi-131-userwarning-about

[SongGithub]

@puremourning
Hi I double checked Python and it seems to be correct.
Then I removed the YCM files and restalled it. Error when compiling as follows:
[100%] Built target ycm_core
msbuild or xbuild is required to build Omnisharp
Traceback (most recent call last):
File "./install.py", line 32, in
Main()
File "./install.py", line 21, in Main
subprocess.check_call( [ python_binary, build_file ] + sys.argv[1:] )
File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python', '/home/song/.vim/bundle/YouCompleteMe/third_party/ycmd/build.py', '--all']' returned non-zero exit status 1

[puremourning]

msbuild or xbuild is required to build Omnisharp

If you want the c-sharp completer, you need mono. See the README for instructions

[SongGithub]

@puremourning
I don't need c#. It happens due to my selection on --all when running ./install.py

[puremourning]

@SongGithub don't pass --all unless you want _all_ the completers. Just select the ones you want. The README explains this. If you have further trouble with the installer, I suggest you take it to the ycm-users group.

[SongGithub]

@puremourning
I've compile YCM correctly this time! But the error msg still comes up when I turn on VIM.

Error detected while processing function youcompleteme#Enable..64_SetUpPython:

[SongGithub]

I have 'solved' the problem, by shovel the warnings 'underneath the carpet'.

Cause:

Cffi module from python2.7 package was called by YCM. And the CFFI module thinks it is clever to pop up a warning about future change in one of its implementation details. Then YCM will remind me the warning originated from CFFI every time I turn on the VIM which is annoying.

Solve:

plunge into CFFI/model.py file, and comment-out related warning. So that it won't bother me in a while.

Hope this helps whoever stuck here like me.

[arthurkiller]

Realy helps a lot . I prass --all and have the same mistake.
Is there any solutions if I BOTH NEED the c-lang and go-lang support with YCM??

[micbou]

Is there any solutions if I BOTH NEED the c-lang and go-lang support with YCM??

You need to run the script with the --clang-completer and --gocode-completer flags:

./install.py --clang-completer --gocode-completer

[unlessbamboo]

@arthurkiller
+1, same problem, waste a lot of time to compile code.......

[puremourning]

If you have a new problem please raise a new issue following the instructions in CONTRIBUTING.md

[tommyjcarpenter]

I come with the same issue on Centos 7.4.