Skip to content
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

Debug Console ignores logging of empty lines #52028

Closed
kayahr opened this issue Jun 15, 2018 · 3 comments
Closed

Debug Console ignores logging of empty lines #52028

kayahr opened this issue Jun 15, 2018 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@kayahr
Copy link

kayahr commented Jun 15, 2018

  • VSCode Version: 1.24.1
  • OS Version: Debian GNU/Linux 9.4

Steps to Reproduce:

  1. Write a small Node application like this:
console.log("Line 1");
console.log();
console.log("Line 3");
console.log("");
console.log("Line 5");
console.log(" ");
console.log("Line 7");

2.Launch it in the terminal and see the correct output:

console

  1. Launch it in the debugger and see the wrong output:

debug

So when running in the debugger then console.log() without parameters and console.log("") with an empty string parameter does not generate an empty output line. But logging a single space character works.

Does this issue occur when all extensions are disabled?: Yes

This problem is similar to #24308 I reported last year. In this issue I reported that empty lines where sometimes ignored. Now they are always ignored. So looks like the bug wasn't fixed properly.

@vscodebot
Copy link

vscodebot bot commented Jun 15, 2018

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@isidorn
Copy link
Contributor

isidorn commented Jun 22, 2018

The issue here is that I am not getting an output event from the debug adapter for those empty outputs -> forwarind first to @roblourens to investigate
There might be something that we are doing wrong on the ui end on top of that, but this is the initial issue, so it would be great if @roblourens could check on the adapter side. Thanks

@isidorn isidorn assigned roblourens and unassigned isidorn Jun 22, 2018
@isidorn isidorn removed this from the June 2018 milestone Jun 22, 2018
@roblourens roblourens added the bug Issue identified by VS Code Team member as probable bug label Jun 24, 2018
@roblourens roblourens added this to the June 2018 milestone Jun 24, 2018
@roblourens
Copy link
Member

Indeed an adapter bug

@RMacfarlane RMacfarlane added the verified Verification succeeded label Jun 28, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Aug 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants