Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 3 commits
- 9 files changed
- 3 contributors
Commits on Jun 6, 2025
-
Synchronize markers updates (#1283)
Sending the same diagnostics from LS twice for example results in race conditions in `LSPDiagnosticsToMarkers`, namely the job for updating the Eclipse resource markers in `updateMarkers(...)` method. The job's scheduling rule is `null`. There is an expression for computing proper marker modification scheduling rule but the value of the resultant rule is `null`. Therefore, marker update jobs can run in parallel and result in some markers duplicated sometimes. Fixing this cabbe a different scheduling rule, i.e. the resource but this might affect the build and other things. The other option is just sync block for updating the markers within the job body. The "sync block" solution seemed to work and is included in the PR.
Commits on Jun 11, 2025
-
fix: Check project is accessible before updating markers. (#1284)
Checking that a resource exists is not sufficient for Project resources as they still exist even if they are closed. This prevents 'project is not open' exceptions when publishing markers on a close-project event as introduced by #1266.
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 0.27.5...0.27.6