Hacktoberfest 2026: những issue maintainer đã đánh dấu cho tháng Mười, đang mở và phù hợp người mới. Xem issue Hacktoberfest

"Trigger Suggest" and "Quick Fix..." commands, code navigation not responding

Đang mở
#948 10 bình luận 0 reaction 1 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Issue này chưa được đánh giá.

Mô tả

ai-triaged bug code-completion testing

Environment:

  • VS Code Version: 1.65.x (also tested in 1.64.2)
  • Extension Version: 0.22.1 (vscode-java 1.4.0, also tested with 1.3.0)
  • JDK Type & Version: Amazon Corretto JDK 11.0.11.9.1
  • OS Type & Version: Windows

Step to Reproduce:
Unknown, seemingly random.

However, restarting VS Code does seem to reset the issue but only temporarily, and the amount of time before the issue resurfaces varies, sometimes as short as a couple minutes, other times it lasts quite a while (hours, days).

Expected Behavior:

  • Triggering commands "Trigger Suggest" and "Quick Fix..." (i.e. Ctrl+Space, Alt+Enter) should consistently cause intellisense popup to be populated with suggestions/fixes
  • All code navigation (Ctrl+click, etc.)/"Go to ___"/"Find all references" commands should work
  • Tests can be executed

Actual Behavior:

  • Triggering mentioned commands manually using keybindings causes intellisense popup to appear, but says "Loading..." indefinitely. The following two entries are added to the LS log upon the Ctrl+Space ("Trigger Suggest") command:
    !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:08:00.387
    !MESSAGE >> workspace/executeCommand java.intellicode.completion
    
    !ENTRY com.microsoft.jdtls.intellicode.core 1 0 2022-03-28 10:08:00.401
    !MESSAGE Completion request completed
    
    • Upon certain context-sensitive keystrokes, such as . (period after a reference, to access a member) and @ to add an annotation, suggestions do populate as expected. The following log entries are added upon typing . (period) after a reference:

      View log entries

      [looks like only the first five entries are relevant, but figured I'd include all just in case]

      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.078
      !MESSAGE >> document/didChange
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.085
      !MESSAGE >> workspace/executeCommand java.intellicode.completion
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.090
      !MESSAGE Reconciled 1. Took 1 ms
      
      !ENTRY com.microsoft.jdtls.intellicode.core 1 0 2022-03-28 10:10:58.101
      !MESSAGE Completion request completed
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.126
      !MESSAGE >> workspace/executeCommand java.intellicode.completion.resolve
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.265
      !MESSAGE >> document/foldingRange
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.330
      !MESSAGE >> document/codeAction
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.344
      !MESSAGE >> workspace/executeCommand vscode.java.resolveMainMethod
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.362
      !MESSAGE >> workspace/executeCommand vscode.java.resolveMainMethod
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.369
      !MESSAGE >> textDocument/semanticTokens/full
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.593
      !MESSAGE begin problem for /DataFileServiceImpl.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.593
      !MESSAGE 0 problems reported for /DataFileServiceImpl.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.607
      !MESSAGE begin problem for /DataFileIterator.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.608
      !MESSAGE 0 problems reported for /DataFileIterator.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.629
      !MESSAGE begin problem for /DataFileFactoryImpl.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.629
      !MESSAGE 2 problems reported for /DataFileFactoryImpl.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.881
      !MESSAGE begin problem for /BinaryDataFileWriterImpl.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.882
      !MESSAGE 0 problems reported for /BinaryDataFileWriterImpl.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.895
      !MESSAGE begin problem for /InternalDataFileFactory.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.896
      !MESSAGE 0 problems reported for /InternalDataFileFactory.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:58.896
      !MESSAGE Validated 5. Took 403 ms
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:10:59.028
      !MESSAGE >> document/codeAction
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:11:00.075
      !MESSAGE >> document/didSave
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:11:00.389
      !MESSAGE >> workspace/didChangeWatchedFiles 
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:11:00.395
      !MESSAGE Reconciled 1. Took 0 ms
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:11:01.117
      !MESSAGE begin problem for /DataFileServiceImpl.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:11:01.117
      !MESSAGE 0 problems reported for /DataFileServiceImpl.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:11:01.128
      !MESSAGE begin problem for /DataFileIterator.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:11:01.128
      !MESSAGE 0 problems reported for /DataFileIterator.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:11:01.147
      !MESSAGE begin problem for /DataFileFactoryImpl.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:11:01.147
      !MESSAGE 2 problems reported for /DataFileFactoryImpl.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:11:01.219
      !MESSAGE begin problem for /BinaryDataFileWriterImpl.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:11:01.219
      !MESSAGE 0 problems reported for /BinaryDataFileWriterImpl.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:11:01.234
      !MESSAGE begin problem for /InternalDataFileFactory.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:11:01.234
      !MESSAGE 0 problems reported for /InternalDataFileFactory.java
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:11:01.234
      !MESSAGE Validated 5. Took 387 ms
      
      !ENTRY org.eclipse.jdt.ls.core 1 0 2022-03-28 10:11:01.412
      !MESSAGE >> document/codeAction
      
    • Other keystrokes, such as letters, which would normally suggest identifiers/members/imports/templates/etc. don't even trigger the "Loading..." popup.

  • Some code navigation, "Go to ___" and "Find all ___" commands not responding
    • Not working: "Go to Definition", "Go to References", "Find All References"
    • Working: "Go to Implementation", "Go to Super Implementation", "Go to Type Definition", "Find All Implementations"
    • For those not working:
      • the loading bar beneath tabs appears and moves indefinitely
      • tried triggering using Ctrl+click, keystrokes and context menu commands
  • A couple times these have resulted in significant, sustained CPU usage
  • vscode-java-test plugin appears to have crashed (not sure if this is related)
    • extension is greyed-out in the extension list, cannot be enabled/disabled
    • no "Run" icon beside test cases in code editor
    • test panel not populated

Related Issues:

Ngôn ngữ chính
TypeScript
Star
352
Fork
166
Merge trung bình
13 giờ 16 phút
Pull request đã merge (30 ngày)
22

Chuẩn bị môi trường

Chúng tôi chưa kiểm tra các tệp thiết lập môi trường của dự án này. Hãy bắt đầu từ README và xem hướng dẫn đóng góp lần đầu của chúng tôi để biết các bước chung.

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của microsoft/vscode-java-pack

Tất cả issue của microsoft/vscode-java-pack

Issue tương tự

Thêm issue về TypeScript

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.