Closed baelter closed 1 year ago
@baelter Thank you for report this, I'll try to reproduce it :+1:
Have you tried scry as well? :sweat_smile: See: https://github.com/crystal-lang-tools/scry/ and https://github.com/crystal-lang-tools/vscode-crystal-lang/wiki/Settings#server
No yet. But I will if that is what's getting most developer attention.
Hi @baelter Do you still have this issue? I'm trying to reproduce it :sweat_smile:
I am having the same issue right now (macOS 10.14.6)
Also tested scry (followed installation instructions). Having this one line in main.cr
puts "Hello"
scry gave me this error
[Info - 3:46:34 PM] Scry is looking into your code...
[Error - 3:46:37 PM] An error was found while searching diagnostics
Unexpected char 'U' at 1:1
Unable to get file info: '/Users/pavestru/code/crystal-test/Users/pavestru/.cache/crysta/Users-pavestru-code-crystal-test-Users-pavestru-.cache-crysta-Users-pavestru-code-crystal-test-Users-pavestru-.cache-crysta-Users-pavestru-code-crystal-test-Users-pavestru-.cache-crysta-Users-pavestru-code-crystal-test-Users-pavestru-.cache-crysta-Users-pavestru-code-crystal-test-Users-pavestru-.cache-crysta-Users-pavestru-code-crystal-test-main.cr': File name too long (File::Error)
from raise<File::Error+>:NoReturn
from Crystal::System::File::info?<String, Bool>:(Crystal::System::FileInfo | Nil)
from Dir::mkdir_p<String>:Nil
from Crystal::CacheDir#directory_for<String>:String
from Crystal::Compiler#new_program<Array(Crystal::Compiler::Source)>:Crystal::Program
from Crystal::Compiler#compile<Array(Crystal::Compiler::Source), String>:Crystal::Compiler::Result
from Crystal::Command#run:(Bool | Crystal::Compiler::Result | Nil)
from __crystal_main
from main
Error: you've found a bug in the Crystal compiler. Please open an issue, including source code that will allow us to reproduce the bug: https://github.com/crystal-lang/crystal/issues
I'm having this issue on debian-buster, ubuntu and when using crystal-docker-image.
I can see that the issue is solved by f3667c8, I actually cloned master and built the extension and it works fine.
I'm just wondering why it hasn't been published to the vscode marketplace? ^^
This fix has been published for some time.
macOS 10.14.1 (18B75)
Settings:
Error: