Bug#1019188: vim-youcompleteme makes vim show many error messages on start and while using
Hi, On Tue, Sep 06, 2022 at 10:34:46AM +0200, Emmanuel Thomé wrote: > On the other hand, enabling youcompleteme via :packadd youcompleteme > seems to work without error. Thanks for looking into it! The problem seems indeed to effect vim-addon-manager only: Upstream added/split out two new files which I had not recorded for install by v-a-m, so it could indeed not be found. Me fixing the registry entry doesn't resolve the problem completely through as you will have to then reinstall the plugin with v-a-m (that is inherent in its design). Looks like this patch would resolve it: diff --git a/debian/vim-youcompleteme.yaml b/debian/vim-youcompleteme.yaml index 57d1c6f..b00ebad 100644 --- a/debian/vim-youcompleteme.yaml +++ b/debian/vim-youcompleteme.yaml @@ -3,5 +3,7 @@ description: fast, as-you-type, fuzzy-search code completion engine basedir: /usr/share/vim-youcompleteme files: - autoload/youcompleteme.vim + - autoload/youcompleteme/finder.vim + - autoload/youcompleteme/filetypes.vim - doc/youcompleteme.txt - plugin/youcompleteme.vim On your system the file is installed as /usr/share/vim/registry/vim-youcompleteme.yaml I will see if I can come up with a little autopkgtest to ensure not breaking that too often in the future. I suggest looking into transitioning away from v-a-m through as Debian seems to slowly do this as a whole (#1015149). Best regards David Kalnischkies signature.asc Description: PGP signature
Bug#1019188: vim-youcompleteme makes vim show many error messages on start and while using
The log of docker build, with all package versions, is attached. @Frank: to remove youcompleteme from your vim-addon-manager config, you can do "vam remove youcompleteme". It seems that using packadd instead of vim-addon-manager works better, no idea why. E. On Tue, Sep 06, 2022 at 10:34:47AM +0200, Emmanuel Thomé wrote: > Hi, > > I'm affected by this bug too. > > After some hit and miss, I'm able to reproduce it in a docker container. > > mkdir /tmp/bug1019188 > cd /tmp/bug10109188 > cat > Dockerfile < FROM debian:testing > RUN apt-get update && DEBIAN_FRONTEND=noninteractive apt-get -y install > vim-nox vim-addon-manager vim-youcompleteme locales > RUN perl -pe 's/^# (en_US.UTF-8)/$1/;' -i /etc/locale.gen && locale-gen -a > RUN vam install youcompleteme > EOF > docker build -t bug10109188 . > docker run --rm -it bug10109188 env LANG=en_US.UTF-8 vim > > > On the other hand, enabling youcompleteme via :packadd youcompleteme > seems to work without error. > > > Best, > > E. $ docker build -t bug1019188 . Sending build context to Docker daemon 2.048kB Step 1/4 : FROM debian:testing ---> 8cda960ae552 Step 2/4 : RUN apt-get update && DEBIAN_FRONTEND=noninteractive apt-get -y install vim-nox vim-addon-manager vim-youcompleteme locales ---> Running in caa85c9b559d Get:1 http://deb.debian.org/debian testing InRelease [157 kB] Get:2 http://deb.debian.org/debian testing/main amd64 Packages [8459 kB] Fetched 8616 kB in 2s (3776 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: ca-certificates fonts-lato gcc-12-base javascript-common lib32gcc-s1 lib32stdc++6 libabsl20220623 libbsd0 libc-bin libc-l10n libc6 libc6-i386 libclang-common-14-dev libclang1-14 libedit2 libexpat1 libgcc-s1 libgdbm-compat4 libgdbm6 libgpm2 libicu71 libjs-jquery libjs-sphinxdoc libjs-underscore libllvm14 liblua5.2-0 libmd0 libmpdec3 libncurses6 libncursesw6 libperl5.34 libpython3-stdlib libpython3.10 libpython3.10-minimal libpython3.10-stdlib libreadline8 libruby3.0 libsodium23 libsqlite3-0 libssl3 libstdc++6 libtcl8.6 libtinfo6 libxml2 libyaml-0-2 libz3-4 media-types netbase openssl perl perl-base perl-modules-5.34 python3 python3-bottle python3-frozendict python3-future python3-jedi python3-lib2to3 python3-minimal python3-parso python3-watchdog python3-yaml python3.10 python3.10-minimal rake readline-common ruby ruby-net-telnet ruby-rubygems ruby-webrick ruby-xmlrpc ruby3.0 rubygems-integration unzip vim-common vim-runtime xxd ycmd zip Suggested packages: apache2 | lighttpd | httpd glibc-doc libnss-nis libnss-nisplus gdbm-l10n gpm sensible-utils tcl8.6 perl-doc libterm-readline-gnu-perl | libterm-readline-perl-perl make libtap-harness-archive-perl python3-doc python3-tk python3-venv python-future-doc python3.10-venv python3.10-doc binutils binfmt-support readline-doc ri ruby-dev bundler cscope vim-doc ccls clangd fortran-language-server gopls node-typescript Recommended packages: manpages The following NEW packages will be installed: ca-certificates fonts-lato javascript-common lib32gcc-s1 lib32stdc++6 libabsl20220623 libbsd0 libc-l10n libc6-i386 libclang-common-14-dev libclang1-14 libedit2 libexpat1 libgdbm-compat4 libgdbm6 libgpm2 libicu71 libjs-jquery libjs-sphinxdoc libjs-underscore libllvm14 liblua5.2-0 libmd0 libmpdec3 libncurses6 libncursesw6 libperl5.34 libpython3-stdlib libpython3.10 libpython3.10-minimal libpython3.10-stdlib libreadline8 libruby3.0 libsodium23 libsqlite3-0 libssl3 libtcl8.6 libxml2 libyaml-0-2 libz3-4 locales media-types netbase openssl perl perl-modules-5.34 python3 python3-bottle python3-frozendict python3-future python3-jedi python3-lib2to3 python3-minimal python3-parso python3-watchdog python3-yaml python3.10 python3.10-minimal rake readline-common ruby ruby-net-telnet ruby-rubygems ruby-webrick ruby-xmlrpc ruby3.0 rubygems-integration unzip vim-addon-manager vim-common vim-nox vim-runtime vim-youcompleteme xxd ycmd zip The following packages will be upgraded: gcc-12-base libc-bin libc6 libgcc-s1 libstdc++6 libtinfo6 perl-base 7 upgraded, 76 newly installed, 0 to remove and 62 not upgraded. Need to get 109 MB of archives. After this operation, 510 MB of additional disk space will be used. Get:1 http://deb.debian.org/debian testing/main amd64 perl-base amd64 5.34.0-5 [1640 kB] Get:2 http://deb.debian.org/debian testing/main amd64 libc6 amd64 2.34-7 [2766 kB] Get:3 http://deb.debian.org/debian testing/main amd64 libc-bin amd64 2.34-7 [898 kB] Get:4 http://deb.debian.org/debian testing/main amd64 gcc-12-base amd64 12.2.0-1 [208 kB] Get:5 http://deb.debian.org/debian testing/main amd64 libgcc-s1 amd64 12.2.0-1 [50.3 kB] Get:6 http://deb.debian.org/debian testing/main amd64 libstdc++6 amd64 12.2.0-1 [613 kB] Get:7 http://deb.debian.org/debian testing/main amd64 perl-modules-5.34 all 5.34.0-5 [2850 kB] Get:8 h
Bug#1019188: vim-youcompleteme makes vim show many error messages on start and while using
Hi, I'm affected by this bug too. After some hit and miss, I'm able to reproduce it in a docker container. mkdir /tmp/bug1019188 cd /tmp/bug10109188 cat > Dockerfile <
Bug#1019188: vim-youcompleteme makes vim show many error messages on start and while using
Hi, On Mon, Sep 05, 2022 at 08:02:20PM +0200, David Kalnischkies wrote: > Hi, > > On Mon, Sep 05, 2022 at 09:47:33AM +0200, Frank Scherrer wrote: > > ... > > Mhhh. Which filetype (vim tells you if you type ":set filetype?") has > this buffer? Can you perhaps attach a file triggering these error for > you? Perhaps its a problem with a specific filetype/syntax file > (recently there was e.g. a bug in vims typescript syntax file, but you > have a fixed version installed already). I just open vi, no file specified, and still get the errors. So no filetype set at all. > > How are you enabling vim-youcompleteme? I recently switched the package > away from vim-addon-manager, even if it should still be technically > supported (and that was already done before your "good" -3) but perhaps > it broke in a later version. I note that the "bad" versions added a few > experimental features and with it a bit of refactoring and new files. I use vim-addon-manager > > … > > Now, I wanted to ask you to run 'vim -Nu NONE' (starting vim without any > configuration) and then run ':packadd youcompleteme' to see if it is > dependent on your local configuration, but I forgot the 'N' flag and as > a result got similar errors as you got… > Could it be that you run vim in vi compatible mode? (:set compatible?) No, it sais nocompatible. Starting vim in the way you suggested does not result in error messages, even when I add youcompleteme next. So it is my configuration, right? > > Ideally this plugin should really work regardless of compatible mode or > not, but I am not sure upstream agrees and will probably need some time > to dig into what is going on here. > Just wanting to confirm now that I am not following a red herring and > this is indeed the cause of the issue (or if I found another). > > If you are in compatible mode I suppose it is a deliberate choice as > I think it is not Debians default, but on the off chance that it is not > feel free to join the nocompatible side as a possible fix/workaround. > We have cookies. ;) I am nocompatible already ... regarding vim-configuration :-D.. So as I described above I think this is something with my vim-configuration and I digged a bit. This is, what I came up with: I can make the Errors vanish by adding a link: ~/.vim/autoload/youcompleteme -> /usr/share/vim-youcompleteme/autoload/youcompleteme If I understand https://salsa.debian.org/debian/vim-youcompleteme/-/compare/48b92f5f...master?from_project_id=26053#aa93b379d38d836d0026e27ca5e01c0bba4ac1b9_512_576 correct, then s:AllowedToCompleteInBuffer in autoload/youcompleteme.vim of the new version calls another function youcompleteme#filetypes#AllowedForFiletype( filetype ) which is in autoload/youcompleteme/filetypes So my question now is: How should I (un)configure vim-youcompleteme correctly? Thanks again in advance. > > > Best regards > > David Kalnischkies BR Frank signature.asc Description: PGP signature
Bug#1019188: vim-youcompleteme makes vim show many error messages on start and while using
Hi, On Mon, Sep 05, 2022 at 09:47:33AM +0200, Frank Scherrer wrote: > Version: 0+20220824+git7c3a88f+ds-2 > >* What led up to the situation? >An update from version 0+20220402+git3ededae+ds-3, if >snapshot.debian.org is right, there was a version in between. (Nitpick: There were two versions in between, a -4 revision of your "good" version and a -1 revision of the "bad" one, but that is easy to miss with the version number that large and unwieldy.) >* What exactly did you do (or not do) that was effective (or > ineffective)? >I started vi and tried to move around in a file after pressing return >to all the error messages. That looks indeed bad, but sadly I can't reproduce this manually nor in the automatic tests so far. :( > Here come the error messages: > Error detected while processing CursorMoved Autocommands for "*"..function > 45_OnCursorMovedNormalMode[1]..45_AllowedToCompleteInCurrentBuffer[1]..45_AllowedToCompleteInBuffer: > line 12: > E117: Unknown function: youcompleteme#filetypes#AllowedForFiletype Mhhh. Which filetype (vim tells you if you type ":set filetype?") has this buffer? Can you perhaps attach a file triggering these error for you? Perhaps its a problem with a specific filetype/syntax file (recently there was e.g. a bug in vims typescript syntax file, but you have a fixed version installed already). How are you enabling vim-youcompleteme? I recently switched the package away from vim-addon-manager, even if it should still be technically supported (and that was already done before your "good" -3) but perhaps it broke in a later version. I note that the "bad" versions added a few experimental features and with it a bit of refactoring and new files. … Now, I wanted to ask you to run 'vim -Nu NONE' (starting vim without any configuration) and then run ':packadd youcompleteme' to see if it is dependent on your local configuration, but I forgot the 'N' flag and as a result got similar errors as you got… Could it be that you run vim in vi compatible mode? (:set compatible?) Ideally this plugin should really work regardless of compatible mode or not, but I am not sure upstream agrees and will probably need some time to dig into what is going on here. Just wanting to confirm now that I am not following a red herring and this is indeed the cause of the issue (or if I found another). If you are in compatible mode I suppose it is a deliberate choice as I think it is not Debians default, but on the off chance that it is not feel free to join the nocompatible side as a possible fix/workaround. We have cookies. ;) Best regards David Kalnischkies signature.asc Description: PGP signature
Bug#1019188: vim-youcompleteme makes vim show many error messages on start and while using
Package: vim-youcompleteme Version: 0+20220824+git7c3a88f+ds-2 Severity: normal Dear Maintainer, I think I have discovered an Issue with the latest version of vim-youcompleteme: * What led up to the situation? An update from version 0+20220402+git3ededae+ds-3, if snapshot.debian.org is right, there was a version in between. * What exactly did you do (or not do) that was effective (or ineffective)? I started vi and tried to move around in a file after pressing return to all the error messages. * What was the outcome of this action? The error messages occurred and reoccurred. * What outcome did you expect instead? No errors. Here come the error messages: Error detected while processing CursorMoved Autocommands for "*"..function 45_OnCursorMovedNormalMode[1]..45_AllowedToCompleteInCurrentBuffer[1]..45_AllowedToCompleteInBuffer: line 12: E117: Unknown function: youcompleteme#filetypes#AllowedForFiletype Press ENTER or type command to continue E117: Unknown function: youcompleteme#filetypes#AllowedForFiletype Press ENTER or type command to continue Error detected while processing CursorMoved Autocommands for "*"..function 45_OnCursorMovedNormalMode[1]..45_AllowedToCompleteInCurrentBuffer[1]..45_AllowedToCompleteInBuffer[12]..45_PollServerReady[14]..45_OnFileTypeSet[8]..45_AllowedToComplet eInCurrentBuffer[1]..45_AllowedToCompleteInBuffer: line 14: E121: Undefined variable: allowed Press ENTER or type command to continue Error detected while processing CursorMoved Autocommands for "*"..function 45_OnCursorMovedNormalMode[1]..45_AllowedToCompleteInCurrentBuffer[1]..45_AllowedToCompleteInBuffer[12]..45_PollServerReady[14]..45_OnFileTypeSet[8]..45_AllowedToComplet eInCurrentBuffer[1]..45_AllowedToCompleteInBuffer: line 19: E121: Undefined variable: allowed Press ENTER or type command to continue Error detected while processing CursorMoved Autocommands for "*"..function 45_OnCursorMovedNormalMode[1]..45_AllowedToCompleteInCurrentBuffer[1]..45_AllowedToCompleteInBuffer: line 14: E121: Undefined variable: allowed Press ENTER or type command to continue Error detected while processing CursorMoved Autocommands for "*"..function 45_OnCursorMovedNormalMode[1]..45_AllowedToCompleteInCurrentBuffer[1]..45_AllowedToCompleteInBuffer: line 19: E121: Undefined variable: allowed Press ENTER or type command to continue Pressing ENTER afterwards makes vim look normal until you try to move around or do something else. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vim-youcompleteme depends on: ii python3 3.10.6-1 ii python3-future0.18.2-6 ii vim-nox [vim-python3] 2:9.0.0242-1 ii ycmd [ycmd-core-version] 0+20220824+git2ee4100+ds-1+b1 Versions of packages vim-youcompleteme recommends: ii ycmd 0+20220824+git2ee4100+ds-1+b1 vim-youcompleteme suggests no packages. -- no debconf information Thank you for using reportbug I have now downgraded to version 0+20220402+git3ededae+ds-3 from snapshot.debian.org which resolves my situation for now. Let me know if I can help resolving this and many thanks in advance. Bear with me, this is my first bugreport. cheers Frank signature.asc Description: PGP signature
