Skip Menu |

This queue is for tickets about the Perl-LanguageServer CPAN distribution.

Report information
The Basics
Id: 133689
Status: open
Priority: 0/
Queue: Perl-LanguageServer

People
Owner: Nobody in particular
Requestors: neuber [...] gmx.de
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Error: Connection to server got closed.
Date: Fri, 6 Nov 2020 10:02:21 +0100
To: bug-Perl-LanguageServer [...] rt.cpan.org
From: Neuber <neuber [...] gmx.de>
If I start Visual Studio Code with your Perl extension, I've got the output: tcp server start listen on port 13603 [Info - 09:13:30] Connection to server got closed. Server will restart. and a popup: The Perl Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted. I've the latest version of Strawberry Perl on Windows 10. I've installed Perl::LanguageServer and the latest version of Compiler::Lexer (0.23), and run "cpan -u" to upgrade all installed Perl modules. Any idea how to fix this issue?
Subject: Re: [rt.cpan.org #133689] AutoReply: Error: Connection to server got closed.
Date: Fri, 6 Nov 2020 10:53:40 +0100
To: bug-Perl-LanguageServer [...] rt.cpan.org
From: Neuber <neuber [...] gmx.de>
I made a one-liner to tokenize the file, to try to isolate the problems: perl -e "use Data::Dumper; use Compiler::Lexer; my $source; { open my $fh, '<', $ARGV[0]; local $/; $source=<$fh>; } my $lexer = Compiler::Lexer->new(); my $tokens = $lexer->tokenize($source); print Dumper($tokens);" D:\Perl\Okid\test.pl This does not crash and produces the expected output. I tried something similar to invoke parse_perl_source, like this: perl -e "use Data::Dumper; use Perl::LanguageServer::Parser; my $source; { open my $fh, '<', $ARGV[0]; local $/; $source=<$fh>; } my $vars = Perl::LanguageServer::Parser::parse_perl_source(undef, 'x', $source); print Dumper($vars);" D:\Perl\Okid\test.pl This also did not crash, and produced what looks like correct output.
Maybe it's https://rt.cpan.org/Public/Bug/Display.html?id=133349 ? I just can't remember right now which error messages I got in VSCode so it might still be something different in your case.