I'm only getting the first line of each error in my inline popups

[makoConstruct]

When I do the go to next error thing, it'll show an inline error window with a bit of information about the error, but it's usually not enough information, for instance, it will say "mismatched types", but it will never say which type was expected or which was present. To see that, I have to go scroll around in the command line output, which is frustrating.

I asked around a little bit, and apparently this isn't the normal behavior?

I'm on the pre-release version (v0.4.1078), using vscode 1.67.1

Any advice as to how to figure out what might be happening or fix my installation would be welcome. I've tried clearing my user settings, uninstalling the extension and reinstalling it, disabling extensions that might be interfering, with vscode restarts. Didn't help.

[makoConstruct]

(the reason I didn't file this via the 'bug' option was, It wasn't initially clear to me that this was a bug, I thought I might be writing up more of a feature request, only learned later that the feature is already implemented and working for most people.)

[flodiebold]

Can you show an example / screenshot of what you mean?

[makoConstruct]

[makoConstruct]

So in this case, my question would be, well, what types? Please tell me. But this inline box will not show enough information, and I'll have to resort to messing around with the terminal.

[flodiebold]

What rustc version are you using? Could you reproduce the problem with a small example in a new project?

[Veykril]

I think this is kind of expected since we split diagnostic sub-spans up into linked diagnostics (which have terrible UX in VSCode), so the expected foo, found bar part is in a different diagnostic on the same text range (Note the 1 of 3 problems part in the pop-up).

[makoConstruct]

we split diagnostic sub-spans up into linked diagnostics (which have terrible UX in VSCode)

What UX? There isn't a way here to get it to show the other diagnostic spans. Clicking the arrows doesn't do that, it goes between 'problems', none of which show the rest of the error. The number in 1 of 3 problems tracks with the number of problem sites across the whole file. There are no relevant actions in the action search relating to 'diagnostics'.

[makoConstruct]

What rustc version are you using? Could you reproduce the problem with a small example in a new project?

rustc 1.63.0-nightly (42e1761 2022-05-15). The problem is present in every project I've opened vscode on, including the projects of people who aren't experiencing this issue.

If no one can reproduce this, I'll just try to remember to close the issue myself when it stops happening.

[flodiebold]

The problem is present in every project I've opened vscode on, including the projects of people who aren't experiencing this issue.

I was hoping you could provide a concrete, small example so we could compare.

[makoConstruct]

The issue has ceased 🤷 no idea what changed. As promised, closing issue.

[makoConstruct]

Set up rust and vscode on another machine and it's happening again.

rustc 1.68.0-nightly (88c58e3c2 2022-12-26), rust analyzer v0.4.1367 Pre-Release

The only rust related extension I have is rust analyzer and I can't see how any of the others would affect it.

[disabled bookmarks just in case]

Here are some more examples of what the messages are like

Which bound? I need to know.

Which trait bounds?

I've just noticed this setting. It was turned off, it defaults to being turned off. I turned it on, but it didn't change anything.

[makoConstruct]

Why can rust analyzer sometimes output unhelpfully prosaic messages? Where should I start looking in the codebase to begin investigating how this could be happening?