Ninja output not always flushed to terminal

Open
#21 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

No source file or test is named. Start by reproducing a slow-system build with a missing semicolon and inspect how the extension handles Ninja's terminal output, using the linked VS Code issue for context. Done means compiler errors appear reliably in the terminal.

Written by the indexing model from the issue text.

Description

bug

When compiling a project with errors (eg missing semi-colons), the actual error is not always shown in the terminal output. This is intermittent, and appears to only occur on slower systems

This is probably related to https://github.com/microsoft/vscode/issues/92868

Dominant language
TypeScript
Stars
297
Forks
45
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from raspberrypi/pico-vscode

All issues in raspberrypi/pico-vscode

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.