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

Test output was be blocked and no longer display to debug console when testing extension #273

Closed
qwas368 opened this issue Jun 14, 2019 · 1 comment

Comments

2 participants
@qwas368
Copy link

commented Jun 14, 2019

Describe the bug
As title. I developed my vs code extension and found that test output was blocked by SQLTools extension.

To Reproduce
Steps to reproduce the behavior:

  1. Install SQLTools extension
  2. create any extension by yo code (ref: https://code.visualstudio.com/api/get-started/your-first-extension)
  3. Testing Extension (ref: https://code.visualstudio.com/api/working-with-extensions/testing-extension)
  4. Debug console can't print any message.

Expected behavior
image

Screenshots
image

Desktop (please complete the following information):

  • SQLTools Version v0.19.5
  • VSCode Version: 1.35.0
  • Dialect Used: n/a
  • OS: Windows 10

Additional context
No

@qwas368 qwas368 added the bug label Jun 14, 2019

@project-bot project-bot bot added this to To do in Kanban Jun 14, 2019

@qwas368 qwas368 changed the title Test output wasn't be blocked and no longer display to debug console where testing extension Test output was be blocked and no longer display to debug console when testing extension Jun 14, 2019

@mtxr mtxr self-assigned this Jun 15, 2019

@project-bot project-bot bot moved this from To do to In progress in Kanban Jun 15, 2019

@mtxr

This comment has been minimized.

Copy link
Owner

commented Jun 19, 2019

Hi,

sorry for the late reply, I had to deal with some stuff here in the past week, I'll take a look at this within this week.

Thanks!

@mtxr mtxr closed this in 572e703 Jun 26, 2019

Kanban automation moved this from In progress to To be released Jun 26, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.