Skip to content
This repository has been archived by the owner on Jul 6, 2021. It is now read-only.

Error executing vim.schedule lua callback: diagnostic-nvim/lua/diagnostic/util.lua:155: index out of range #46

Open
kdheepak opened this issue Jul 19, 2020 · 6 comments · May be fixed by #48

Comments

@kdheepak
Copy link

I get this error every now and then. I think it occurs when there's a large number of diagnostics in the same buffer from a language server. I'm now able to consistently reproduce this error in a Julia file.

Screen Shot 2020-07-19 at 1 27 31 AM

If I hit enter the error message continues popping up.

@haorenW1025
Copy link
Collaborator

Have you updated diagnostic-nvim? I think #38 fixes it.

@kdheepak
Copy link
Author

I just tried again with the latest commit, and I still get the same errors.

@haorenW1025 haorenW1025 linked a pull request Jul 21, 2020 that will close this issue
@haorenW1025
Copy link
Collaborator

I can't reproduce on my side, so let see if the PR fixes it.

@el-iot
Copy link
Contributor

el-iot commented Jul 21, 2020

I found I had the same issue while using the python-language-server. Specifically, one of my linters (pyflakes) would label the starting positions of particular errors as -1, which caused an index-out-of-bounds error. I added these lines at line 91 of diagnostic-nvim/lua/diagnostic.lua

  for _, diagnostic in ipairs(result['diagnostics']) do
    if diagnostic['range']['start']['character'] < 0 then diagnostic['range']['start']['character'] = 0 end
  end

and it has fixed my issues. @haorenW1025, if I can tidy up the implementation a little would you consider this a good pull-request? If so I can put it together (I'll also check to make sure the end-character doesn't exceed the length of the line in case some other language-servers do that).

@el-iot
Copy link
Contributor

el-iot commented Jul 21, 2020

Apologies - I'm not completely up-to-date so it may not be at line 91 of diagnostic-nvim/lua/diagnostic.lua (I was previously on f8b312d)

@el-iot
Copy link
Contributor

el-iot commented Jul 24, 2020

Made a pull-request for this issue (#51) that has fixed this for me (incase #48 doesn't work)

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

Successfully merging a pull request may close this issue.

3 participants