Failed to import project after clean workspace cache

Open
#1,285 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, typescript
Domain
build-system, devtools

Research direction

Reproduce the failure in the spring-petclinic project using the listed VS Code, extension, JDK, and Windows environment. Start by reviewing client.log.txt and server.log.txt alongside the clean workspace cache and reload sequence. Done means the project imports successfully after cache cleaning and the third error message identifies the failure more specifically.

Written by the indexing model from the issue text.

Description

ai-triaged bug codespace

Environment:

  • VS Code Version: Github Codespace
  • Extension Version: 1.27.0
  • JDK Type & Version: java 21
  • OS Type & Version: windows

Step to Reproduce:

  1. Clone and open https://github.com/spring-projects/spring-petclinic > Import as Gradle > Can import successfully
  2. Java status menu > Clean workspace cache > Reload and delete > It aways fails to import the project

Expected Behavior:

  1. After clean workspace, project can be imported again successfully.
  2. For 3rd error, it should be more specific.

Actual Behavior:

  1. First time, it failed with first error.
  2. After then, it always failed with second error. (tried clean workspace 3-4 times, all failed.)
  3. During the importing, sometimes there are automatically canceled and activated as third error. The error message is not clear.
    client log.txt
    server log.txt

image
image
image

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.