Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Bug

Open
#1,346 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the attached 1.log and screenshots, then reproduce the failure in VS Code 1.90.0-insider on macOS after restarting the Java project. Compare the compilation error with the reported Java extension versions; done means debug compilation succeeds and debugging starts normally after restart.

Written by the indexing model from the issue text.

Description

ai-triaged area/project-management bug debug

Environment:

  • VS Code Version: 1.90.0-insider (Universal)
  • Extension Pack for Java Version: v0.26.0
  • Debugger for Java Version: v0.57.0
  • Maven for Java Version: v0.44.0
  • Project Manager for Java Version: v0.23.6
  • Test Runner for Java Version:v0.41.1
  • OS Type & Version: MacOS 11.7.10 (20G1427)

Step to Reproduce:
Click to execute debug to start
Expected Behavior:
Project executes debug to start compilation successfully. Executes and starts debugging
Actual Behavior:
Click to execute debug to start compilation. Errors reported

Everything was normal at the beginning of the project. After one day of use, vscode was restarted. After the restart was completed, debug was clicked and a compilation error was thrown.

I deleted all the files in ~/Library/Application\Support/Code-\Insiders and re-imported the project to solve this problem. However, the error message appeared again after one day of use and restart.

image image image

1.log

Dominant language
TypeScript
Stars
352
Forks
166
Avg merge
17h 47m
Merged PRs (30d)
32

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 microsoft/vscode-java-pack

All issues in microsoft/vscode-java-pack

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.