microsoft / microsoft/TypeScript

Language service doesn't output neither errors nor crashes

Open
#33,631 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Needs Investigation
Dominant language
Go
Stars
111k
Forks
14.3k
Avg merge
2d 4h
Merged PRs (30d)
132

Description

Language service doesn't output errors even when it crashes in these months. So developers can't report neither bugs nor crashes of language service. And this behavior hides type errors.

TypeScript Version: 3.4.0-dev.20190926

Search Terms:

Code

  1. Reproduce #33617.
  2. VSCode must output crash logs of language service but actually doesn't output anywhere in the output panel.
  3. Make a type error like #33616.
  4. This type error must be reported on VSCode but actually not, because probably language service has crashed.
  5. VSCode must output errors of language service but actually doesn't output anywhere in the output panel.

Expected behavior:

Actual behavior:

Playground Link:

Related Issues:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing #33617 in VSCode with the TypeScript 3.4.0-dev.20190926 language service and inspect the output panel. The work is done when language-service crashes and type errors are surfaced so developers can see and report them.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
compilers, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.