Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interrupted while waiting for CSS fragments cache lock, proceeding without using cache #1294

Closed
iloveeclipse opened this issue Mar 29, 2024 · 2 comments
Assignees
Labels
bug Something isn't working regression Regression defect
Milestone

Comments

@iloveeclipse
Copy link
Member

Using I20240327-1800 build I randomly get errors without stack trace while working in Java editor:

Interrupted while waiting for CSS fragments cache lock, proceeding without using cache

This is a regression from #1074.

@RedeemerSK: please check.

  • First of all, if errors are logged, they should be logged with a stack trace.
  • I assume the error is just caused by the fact that while editing or navigating inside Java file, mouse hover request may be cancelled because of some user actions that make the request obsolete. This is not an error and shouldn't be spamming the log.
@iloveeclipse iloveeclipse added bug Something isn't working regression Regression defect labels Mar 29, 2024
@iloveeclipse iloveeclipse added this to the 4.32 milestone Mar 29, 2024
iloveeclipse added a commit to iloveeclipse/eclipse.platform that referenced this issue Mar 29, 2024
Extend `contentMergeViewers` extension point: add an attribute to
consider "linked" editor content type associations. The code checks if
contentMergeViewers contribution refers to such "linked" editor id in
extension, and check if editor supports other content types. In case
there are more content types supported by same "linked" editor, these
would be automatically considered as valid contentTypes for the
contentMergeViewers.

Updated CompareViewerSwitchingPane to consider more precise title
calculations for ContentMergeViewer instances (where concrete type info
is available after instantiation of a particular viewer).

Fixes eclipse-jdt/eclipse.jdt.ui#1294
@RedeemerSK
Copy link
Contributor

@iloveeclipse fix in #1295

@iloveeclipse
Copy link
Member Author

fix in #1295

Thanks, I haven't seen this kind of errors in the log since the fix.

@iloveeclipse iloveeclipse modified the milestones: 4.32, 4.32 M1 Apr 4, 2024
rgrunber pushed a commit to rgrunber/eclipse.jdt.ui that referenced this issue Apr 12, 2024
…f bounds for length 1 (eclipse-jdt#724)

fixes eclipse-jdt#1294

+ Also fix it for TYPE_USE annotations
+ Test nesting in lambda instead of anonymous
+ additional fix for similar problem caused by varargs signature
+ require latest o.e.jdt.core.compiler.batch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working regression Regression defect
Projects
None yet
Development

No branches or pull requests

2 participants