lapce / lapce/lapce-rust

Cargo check not allowing all features

Open
#16 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
87
Forks
30
PR merge metrics
No merged PRs in 30d

Description

Lapce Version

0.2.4

System information

Arch Linux kernel version: 5.15.81-1-lts

Describe the problem

I was working on a Rust project, I had changed it to a library model for ease of organization.

But then I made the GUI a feature which is not compiled by default.

And then the only thing showing up now were syntax highlighting, the only exception was compile-time errors, warnings were ignored.

I have to add the GUI feature to the default temporarily so everything works has expected each time I want to work on it.
(And I have to remember to remove it from the default in the next git push)

Describe the bug

Adding the cargo check flag --all-features or --features '*' show me an error on restart and ask me to check the server logs...

But the thing is, the server logs of what? How am I supposed to magically just 'know' where that log file is?

And the features flag should have worked, this is clearly a bug/error in the Rust plugin.

Problem resumed

Cargo check gives an error when passing the --all-features flag in the Rust plugin configuration.

Lack of information of what server (Probably rust-analyzer or cargo) is the logs from and where the logs even are.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure through the Rust plugin configuration with Cargo check's --all-features flag. Inspect the server logs referenced by the error and determine which server is involved. Done means all features can be checked without a restart error and the message identifies the relevant server and log location.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.