Large log file

[glibsm]

Moving tbodt/deoplete-tabnine#18 to the appropriate place.

The log appears to be out of control:

~/.config/nvim/plugged/deoplete-tabnine master*
❯ ll tabnine.log
-rw-r--r--  1   941M Jan 31 13:27 tabnine.log

It seems to be mostly polluted by the following message:

~/.config/nvim/plugged/deoplete-tabnine master* 27s
❯ tail tabnine.log
[2019-01-31][13:27:12][server::pipeline::walk][ERROR] Walk error: No such file or directory (os error 2)
[2019-01-31][13:27:12][server::pipeline::walk][ERROR] Walk error: No such file or directory (os error 2)
[2019-01-31][13:27:12][server::pipeline::walk][ERROR] Walk error: No such file or directory (os error 2)
[2019-01-31][13:27:12][server::pipeline::walk][ERROR] Walk error: No such file or directory (os error 2)
[2019-01-31][13:27:12][server::pipeline::walk][ERROR] Walk error: No such file or directory (os error 2)
[2019-01-31][13:27:12][server::pipeline::walk][ERROR] Walk error: No such file or directory (os error 2)
[2019-01-31][13:27:12][server::pipeline::walk][ERROR] Walk error: No such file or directory (os error 2)
[2019-01-31][13:27:12][server::pipeline::walk][ERROR] Walk error: No such file or directory (os error 2)
[2019-01-31][13:27:12][server::pipeline::walk][ERROR] Walk error: No such file or directory (os error 2)
[2019-01-31][13:27:12][server::pipeline::walk][ERROR] Walk error: No such file or directory (os error 2)

I'm not sure if it's related to the CPU usage problems, but TabNine has been spiking to 200-300% cpu util without any apparent need (in fact often vim is actually suspended through C-Z).

Potentially related to #24?

[zxqfl]

I'm not sure what could be causing this error. In the next release, I'll make this error log the file/directory that TabNIne was looking for.

I don't support TabNine was indexing the log file? This can easily lead to log file blowup.

[glibsm]

@zxqfl I'm not sure. Is it possible that opening the said file in vim would cause it to be indexed? I don't think I ever looked at the log, and the first time I went to seek it out it was already ~1GB.

Including file/directory in the log statement sounds like a good idea so next time this has some extra context.

[oolongtea]

I'm seeing the same log messages being spammed, as well as CPUs being maxed out for minutes at a time.

$ ./TabNine --version
TabNine 2.1.5 (x86_64-unknown-linux-musl)
Jacob Jackson <jacob@tabnine.com>

$ nvim --version
NVIM v0.3.8
Build type: RelWithDebInfo
LuaJIT 2.0.5

# using github.com/tbodt/deoplete-tabnine, git hash 5ba086d08f1da93ec9bbe9276dbc62fcb301aeed

[amircodota]

Does it still reproduce?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.