Inability to set up Corrosion for Eclipse on W10 using Eclipse Marketplace

[Mrodent]

Please see the previous issue: both the "auto" and "manual" methods on this page for installing Corrosion when installing a new version of Eclipse IDE failed totally.

So, having installed the Edition "Eclipse for Committers" 2023-12 I tried the "Eclipse Marketplace" approach.

Similar thing happens as previously: I have syntax colouring ... and in fact no code analysis. And I am prompted to set up Corrosion properly.

Window --> Preferences --> Rust I find the following setup:

Rustup: D:\apps\rust\rust_1.70.0.cargo\bin\rustup.exe (file exists) (in fact 1.76 is now installed there) Toolchain: stable Cargo: D:\apps\rust\rust_1.70.0.cargo\bin\cargo.exe (file exists) SYSROOT: D:\apps\rust\rust_1.70.0.rustup\toolchains\stable-x86_64-pc-windows-msvc (dir exists) Working directory: D:\apps\Eclipse\eclipse-committers-2023-12-R-win32-x86_64\eclipse (dir exists) Language server: D:\apps\rust\rust_1.70.0.cargo\bin\rust-analyzer.exe (file exists) LS configuration: (empty)

I close and re-open Eclipse ... I get a dialog "Rust Support Not Found" --> Open Preferences. I get the above. I click "Cancel" (or anything) ... and the "Rust Support Not Found" dialog pops up again ...

Please can you advise what I should do? Currently I have no intellisense and no code analysis, only syntax colouring, with a bit of annoyance from the "Rust Support Not Found" dialog popping up, without me having a clue what it wants me to do.

The annoying typing latency which prompted the previous issue is also present:

java.version=17.0.9
java.vendor=Eclipse Adoptium
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB
Framework arguments:  -product org.eclipse.epp.package.committers.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.committers.product

This is a continuation of log file D:\My documents\software projects\EclipseWorkspace\.metadata\.bak_1.log
Created Time: 2024-03-10 12:18:35.955

org.eclipse.lsp4e
Warning
Sun Mar 10 12:20:46 GMT 2024
Could not get trigger characters due to timeout after 50 milliseconds

java.util.concurrent.TimeoutException
	at java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1960)
...
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:588)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1459)"

... it seems likely therefore that this is caused by the Rust 1.76 upgrade.

Do you have any views about what I might do about it?

[liuzq71]