[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.)
[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.
[x] 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.
Issue Details
[If filing a bug report, please include a list of steps that describe how to
reproduce the bug you are experiencing. Also include test code if relevant.]
Problem:
Errors pop up on the first entry to insert mode when editing a file large enough to trigger ycm_disable_for_files_larger_than_kb in vim
Minimal recreation:
Create a text file larger than the trigger value (default: 1000k). For instance: openssl rand 1024000 -base64 -out ycm-test.txt
Open this file in vim (optionally with a minimal
vimrc.txt with YCM installed and compiled, etc: vim -u vimrc.txt ycm-test.txt N.B. this vimrc doesn't contain the two ycm debugging options, but they are set in my testing and reflected in the stderr log output below)
and observe the message as expected:
YouCompleteMe is disabled in this buffer; the file exceeded the max size (see YCM op
tions).
Enter insert mode ('i') and observe the error message:
Error detected while processing function 194_SetOmnicompleteFunc[1]..194_P
yeval:
And a moderate collection of further error messages show up. The full :messages output is attached:
messages.txt
A bit of poking about suggests that the server is returning a 413 during a request in NativeFiletypeCompletionUsable, which is called from SetOmnicompleteFunc. Other things check ycm_largefile and bail if it's true, but that code path doesn't.
Printing YouCompleteMe debug information...
-- Server has Clang support compiled in: False
-- Server running at: http://127.0.0.1:54392
-- Server process ID: 111195
-- Server logfiles:
-- /tmp/ycm_temp/server_54392_stdout.log
-- /tmp/ycm_temp/server_54392_stderr.log
Press ENTER or type command to continue
:YcmToggleLogs stderr output (yes, it seems very minimal):
2016-04-22 12:48:17,459 - DEBUG - No global extra conf, not calling method YcmCorePreload
2016-04-22 12:48:17,688 - INFO - Received health request
2016-04-22 12:48:17,694 - INFO - Received debug info request
OS info: Linux 3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux (Trusty)
Issue Prelude
Please complete these steps and check these boxes (by putting an
x
inside the brackets) before filing your issue:vim --version
.:YcmDebugInfo
.:YcmToggleLogs stderr
.Thank you for adhering to this process! It ensures your issue is resolved quickly and that neither your nor our time is needlessly wasted.
Issue Details
[If filing a bug report, please include a list of steps that describe how to reproduce the bug you are experiencing. Also include test code if relevant.]
Problem:
Errors pop up on the first entry to insert mode when editing a file large enough to trigger ycm_disable_for_files_larger_than_kb in vim
Minimal recreation:
openssl rand 1024000 -base64 -out ycm-test.txt
Open this file in vim (optionally with a minimal vimrc.txt with YCM installed and compiled, etc:
vim -u vimrc.txt ycm-test.txt
N.B. this vimrc doesn't contain the two ycm debugging options, but they are set in my testing and reflected in the stderr log output below)and observe the message as expected:
And a moderate collection of further error messages show up. The full :messages output is attached: messages.txt
A bit of poking about suggests that the server is returning a 413 during a request in
NativeFiletypeCompletionUsable
, which is called fromSetOmnicompleteFunc
. Other things checkycm_largefile
and bail if it's true, but that code path doesn't.Requested debugging data