Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 17:35
    dima74 opened #9020
  • 17:35
    dima74 labeled #9020
  • 17:35
    dima74 assigned #9020
  • 15:55
    Undin edited #6104
  • 15:54
    Undin edited #6104
  • 15:54
    Undin edited #6104
  • 15:54
    Undin edited #6104
  • 15:54
    Undin edited #6424
  • 15:54
    Undin edited #6424
  • 13:42
    github-actions[bot] milestoned #9012
  • 13:42
    bors[bot] closed #8965
  • 13:42
    bors[bot] closed #8965
  • 13:42
    bors[bot] closed #8779
  • 13:42
    bors[bot] closed #9012
  • 13:42
    bors[bot] closed #8114
  • 13:42
    bors[bot] closed #8779
  • 13:42
    bors[bot] closed #8114
  • 13:42
    bors[bot] closed #5062
  • 13:42
    bors[bot] closed #5062
  • 13:42
    bors[bot] closed #6424
David James
@xpe
Bug report: in the latest version of the plugin (0.2.152.4026-212), the following is incorrectly flagged as incorrect:
[with spaces]
toml table name with spaces.png
Tom Wang
@tomwang2011
Hi guys, I am running into an issue where my CLion with rust plugin is finding Cargo with older versions than Crate.io, local build creates a Cargo.lock with itoa version v0.4.8 while CLion's crate is looking for v0.4.7, has this happened to anyone else?
AidanConnelly
@AidanConnelly
Is there a way to solve the endless "Cannot move" false errors?
Jakub Beránek
@Kobzol
Try to invalidate IDE caches and reload the Cargo project.
AidanConnelly
@AidanConnelly
Tried that
Jakub Beránek
@Kobzol
Then it's probably a type inference or borrow checker problem that is caused by using some dependencies that cause a problem for the plugin. Please create an issue https://github.com/intellij-rust/intellij-rust/issues
Miha Rozina
@mrozina:matrix.org
[m]

Hi everyone. I have a problem with debugging. It works fine when debugging my program, but doesn't work when debugging tests. Break points are not hit and if a panic happens it breaks, but I can only see the names of the functions in the call stack, no locals or anything else though. This is on Linux. On Windows it works fine on the same project.

I am using Arch linux and I installed rustup through the arch repos, if that matters. Any ideas what could be wrong?

NPComplete
@dbrowne
Are there any guiedlines for running code within CLion that calls Command::new().spawn() ? Getting inconsistent results within the IDE
Remoun Metyas
@remoun
Hi there, is there any work planned for supporting passing environment variables to the Build step?
Jakub Beránek
@Kobzol
Does it not work for you? (intellij-rust/intellij-rust#5031) Or do you want something else than this?
Remoun Metyas
@remoun
Ah, setting env vars on a run configuration makes that run's build use those vars. That doesn't address the top-level Build Project, but it's a good enough workaround for my needs. Thanks!
Naoyuki Tai
@NaoyukiTai
Does any one know that the conditional breakpoint work? If so, is there any doc for the expression? (I expect Rust expression based condition to not work)
Jakub Beránek
@Kobzol

I tried this:

fn foo(a: u32) {
    println!("{}", a);
}

fn main() {
    foo(6);
    foo(5);
    foo(7);
}

with conditional expression a == 5 at line 2 and it only stopped on the second call. so it seems that it works for simple cases.
But it only worked in CLion with GDB. With LLDB, the debugger has crashed.
In IDEA, which only supports LLDB I think, it didn't crash, but the breakpoint also didn't work.

Naoyuki Tai
@NaoyukiTai
@Kobzol Thanks. On Mac, the breakpoint does work with lldb but not conditional bp. I may try gdb.
feelingnothing
@feelingnothing
Hi! Is there a way to enable macro expansion for syntax suggestions?
Jakub Beránek
@Kobzol
macros are expanded by default, if you also want to expand procedural macros, please see this issue: intellij-rust/intellij-rust#6908. You have to enable two experimental features (org.rust.cargo.evaluate.build.scripts and org.rust.macros.proc)
Andrey Cherkashin
@andoriyu
I have literally every experimental feature enabled, but I still can't get include!(concat!(env!("OUT_DIR"), "/ping.v1.rs")); to work
Andrey Cherkashin
@andoriyu
in fact, I can't even get include!("generated/ping.v1.rs"); to work if file is there without any buildscripts.
1 reply
Lex Cao
@lexcao
Hello, I'm new to contribute here.
Can anyone help to trigger this pr?
intellij-rust/intellij-rust#8633
Norbert Podsadowski
@Norbo11
does anyone know why I dont have any red problem underlines in my editor window, even though there's tons of build errors visible in the build tab?
1 reply
Mia
@squili
i've got a weird issue: the updating indexes background task keeps looping after it encounters a com.intellij.psi.stubs.SerializerNotFoundException: No serializer is registered for stub ID: 1602, externalId: Y_EXPRrust.ARRAY_TYPErust.ASSOC_TYPE_BINDINGrust.BASE_TYPErus, name: null; parent stub class: null
Jacob Birkett
@spikespaz:matrix.org
[m]
how can I use unstable options with rustfmt? there is no way to specify command line args to use either preview or nightly
Jakub Beránek
@Kobzol
There is currently an open PR that will add support for this (intellij-rust/intellij-rust#7825). There may also be some workaround in the meantime (intellij-rust/intellij-rust#4024 check the last two commits).
Jacob Birkett
@spikespaz:matrix.org
[m]
@Kobzol I can't see how the person on that issue managed to get the nightly version working just by having it installed. Is there a way to set it to use nightly globally?
Jakub Beránek
@Kobzol
Hmm, I suppose that in the end they just symlinked stable rustfmt to nightly rustfmt binary :D
Jacob Birkett
@spikespaz:matrix.org
[m]
Does the debugger support asynchronous executors? My breakpoint that is called from a future never seems to be getting called for some reason.
Jakub Beránek
@Kobzol
it shouldn't really matter who/what executes the code, as long as the line with the breakpoint is executed, it should stop there. if you put e.g. println on that line, does it get printed out?
Jacob Birkett
@spikespaz:matrix.org
[m]
No, that is what I'm debugging.
Jacob Birkett
@spikespaz:matrix.org
[m]
@2xsaiko If you're curious, I have an implementation of the Stream trait from futures-core that makes a request to an API and stores the future and polls it until its ready. Except it never gets polled. Here is an email that I wrote to Jon Gjengset that details the issue, I am not hopeful that he will respond but I'm trying to get some experienced person to look at it.
Wrong mention and messages out of order. Sorry random person, meant @Kobzol.
Jakub Beránek
@Kobzol
to be honest, this looks way too complicated to be considered to be a minimal reproducible example. it would be great if you could put all of the code (the Stream and some code that uses it, but doesn't work) into a single repository, along with a simple demonstration how to reproduce the problem. I would also suggest you to post it on Reddit (/r/rust) or on the Rust forum (https://users.rust-lang.org/).
Jacob Birkett
@spikespaz:matrix.org
[m]
See even if I took the time to write out an MCVE it would look much the same
Jakub Beránek
@Kobzol
then I would suggest some general debugging tips. e.g. litter the code with println!, before/after every await, and mainly inside the manual Stream implementation, to see where does the code gets "stuck"
Jacob Birkett
@spikespaz:matrix.org
[m]
I can see where it gets stuck, and I believe I know where the problem is. I've already done all that and had some guys on Discord look at it. I need a doctor of computer science with 35 years industry experience for this one haha
I think it may be a flaw with the executors
Jakub Beránek
@Kobzol
have you tried with a different executor? smol probably isn't as battle tested as e.g. tokio
Jacob Birkett
@spikespaz:matrix.org
[m]
Tried the big three
All questions you could ask are in that email tbh
Occuros
@Occuros

I started using rocket, and code completion stops working properly on any method with a macro annotation:

 #[get("/login"]
pub async login() {...}

If I comment out the #[get["/login"] route annotation, code completion works as expected.

Is there a way to fix it?

Jakub Beránek
@Kobzol
the problem with proc macros in general is that they might arbitrarily change the generated code, and it's very difficult (borderline impossible) to always map that correctly back to the original code. if that is indeed the problem that causes this, the only solution would be to disable macro expansion in the settings, but that will break a lot of stuff. I think that some kind of blacklist is planned, to mark macros that shouldn't be expanded, in order to make code completion still work inside of them
Here it was done for async_trait: intellij-rust/intellij-rust#8183. I would suggest that you create an issue on the repository with this specific code example. Maybe the plugin could be changed to allow users to add these blacklisted macros manually.
intellij-rust/intellij-rust#6908 But first make sure that you have these two options enabled.
asaning
@asaning
can anyone help to resolve this issue
Pedro Henrique
@eexsty
Hello!
nils
@Nilstrieb
Would anyone like to review my PR? It's been open for a month and shouldn't be complex intellij-rust/intellij-rust#8904