"target was empty" in Cargo.toml

[ricochet1k]

I've created a custom Dockerfile with @theia/rust:next, rls, rust-analysis, rust-src, and racer. When I open up a rust project, the only thing that happens is a target was empty error reported in Cargo.toml. As far as I can tell, this is reported because cargo was given the empty string as a build target.

From a cursory search through this project's directory, target appears in preferences, and defaults to null. This doesn't seem to be in any kind of documentation.

Can we add this to the README or some other documentation?
Or better yet, can we just set a default for the target? Some kind of auto-detected target based on the current platform, which is what cargo already does?

[ricochet1k]

rust.jobs must also be set to 1 or something like it, and then I get rustc complaining about - and x86_64-unknown-linux-gnu (the target I specified) as being "multiple input filenames", because I didn't specify a --sysroot.

Okay, these have to have defaults, this is crazy.

[marcdumais-work]

Hi @ricochet1k ,

I see there was a recent breaking change related to preferences, that will be part of Theia 0.6.0, that may be affecting you already if you base your application on next. It's also possible that another change is causing this issue.

So it could be that this will work as expected, once this repo is uplifted to use the most recent Theia APIs. see also: #11 (comment)