-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Index was outside the bounds of the array.
in SignatureHelp.getSignatureHelpFor
#950
Comments
I'm seeing this from time to time too, in Neovim on windows, and I'm completely unsure what it's even referring to. |
I believe @Booksbaum has fixed this in one of his more recent contributions, but we haven't released a version of FSAC that contains it yet. I'm busy the next few days with personal things, but I'm hoping to release it over the weekend. |
Same issue in Emacs Can't reproduce this on my i9 desktop setup. The tests fail reproducibly on an i3 Intel NUC: Seems to be a timing/race-condition. |
#947 -- which is already in current FSAC & ionide But this here is a similar issue: Again line comparison of FCS Position with I'll submit a PR later today |
Reason: Comparison with line 0 instead of line 1 Note: While Exception with stack trace was shown, there was no impact on actual FSAC usage (-> FSAC didn't crash). Exception was just shown in log Note: Request still fails because no prev char, but it fails as expected. Previously failure was unwanted failure
In PmaBolero, I was seeing VSCode crash after about 10-30 minutes of coding 5 or 6 times yesterday. Taking a look at the logs, I was seeing a lot of:
Before each crash, the final log in
exthost.log
would be something akin to:The exception occurred for various files in
PmaBolero\src\PmaBolero.Client\Pages
that I was editing yesterday.I've been able to reproduce the error (by taking a look at the logs) in other repos, but far less frequently and it didn't cause VSCode to crash.
The text was updated successfully, but these errors were encountered: