-
Notifications
You must be signed in to change notification settings - Fork 178
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
Error while indexing: undefined method `file_path' for nil:NilClass #2295
Comments
I'm also seeing this show up after launching VS code from the terminal using It looks like it occurs during ruby-lsp indexing and reaches around half way before showing the Ruby LSP error:
Ruby-LSP v0.7.11 VS Code extension: https://marketplace.visualstudio.com/items?itemName=Shopify.ruby-lsp Version: 1.91.1 |
Hi, can you please run |
This is the same issue as #2287. Let's please centralize the discussions in one place. |
@andyw8 I ran |
Note: The |
@andyw8 I ran your suggestion using raise TypeError.new("Passed `nil` into T.must")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
from /Users/[USERNAME]/.rbenv/versions/3.3.1/lib/ruby/gems/3.3.0/gems/ruby-lsp-0.17.7/lib/ruby_indexer/lib/ruby_indexer/index.rb:526:in `existing_or_new_singleton_class' It turned out that the indexing was failing due to an older version of Thank you for your advice to help resolve this. I see you have created #2296, and that seems a good idea to support users diagnose their local causes of indexing errors. |
@andyw8 Yes, it was Ruby After upgrading |
Thanks, I verified that |
Brilliant, good to hear you have verified that was the fix for the indexing. |
Description
I keep randomly seeing this error message pop up:
![image](https://private-user-images.githubusercontent.com/171603704/348129862-09f5bb0d-6a6f-43bc-877f-91973fa1eb0c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5MDQ1MzMsIm5iZiI6MTczODkwNDIzMywicGF0aCI6Ii8xNzE2MDM3MDQvMzQ4MTI5ODYyLTA5ZjViYjBkLTZhNmYtNDNiYy04NzdmLTkxOTczZmExZWIwYy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjA3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIwN1QwNDU3MTNaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iYjJlOTFiMTBmYzIwNzA3YTgxODBjMDA1ZmMzNDA3YmM2MGE0NWI0MmMwOGJhMTc5NWEwZWU3ZmY5MjVlZjg4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.VuWaw3iTLahY7GJ8bbUdidSqUH6f82YdN4npnM_jIXs)
I don't see anything listed in the Ruby LSP VSCode extension output related to the error message.
VSCode
Version: 1.91.1 (Universal)
Ruby LSP extension
v0.7.11
The text was updated successfully, but these errors were encountered: