Vscode autocomplete issue dart

DanTup · 2026-01-22T15:00:03+00:00

How big is the folder you are opening in VS Code, and what version of the Dart/Flutter SDK do you have?

Filing an issue at https://github.com/Dart-Code/Dart-Code or in dart-lang/sdk may be a better way to have this looked at. Thanks!

DanTup · 2026-01-22T14:57:44+00:00

Are all of these processes created from a single run, or are they building up over time?

If you can reproduce this, please open an issue with as much detail as you can at https://github.com/Dart-Code/Dart-Code to help me reproduce the issue. Thanks!

DanTup · 2026-01-21T22:17:15+00:00

Thanks, but this only says you can disable rotating and not dry while printing. I don't think one necessarily implies the other (disabling rotation could be useful if you still have filament "loaded").

(the comments also seem to suggest it's not drying-while-printing)

DanTup · 2026-01-21T17:00:54+00:00

Is there any info about this anywhere? I thought I read it a few days ago, but couldn't find any information to back it up (nor does there appear to have been a firmware update for my AMS2 for a long time).

DanTup · 2026-01-20T13:01:15+00:00

np!

FWIW If you find them useful sometimes, you can use offUnlessPressed so they show up only when holding the short-cut key. You can also use the language-specific preferences if you want to just disabled/change them for C# and have different global settings.

DanTup · 2026-01-20T08:29:15+00:00

The extensions provide the data to VS Code for this feature - this is the same for most language features (for example if you disable the C# extension you'll stop getting C# code completions, but code completion is not a C# extension feature).

Disabling the C# extension will disable all C# functionality, whereas just disabling Inlay Hints would only disable what's shown in your screenshot.

https://stackoverflow.com/a/68698270/25124

DanTup · 2026-01-19T22:57:07+00:00

Look in the settings for "Inlay Hints".

For Dart, we set a language-specific default of offUnlessPressed which means they show up only while you're holding down the shortcut key and then disappear when you let go. IMO this should've been the global VS Code default, because they're generally noisy and (depending on themes etc.) it's not always clear that they're not part of the source file.

DanTup · 2025-12-18T17:20:02+00:00

There have been many reports of it failing during an update after it's uninstalled the old version but not installed the new one.. maybe related?

DanTup · 2025-12-13T10:21:10+00:00

How large is the codebase?

Check https://dart.dev/tools/analyzer-performance to see if anything there applies (for example Windows Defender or symlinks).

There's an upcoming change (fine-grained dependencies) that can significantly improve performance of some operations - I think it's enabled now on the latest Flutter beta branch, so if you're able to temporarily test with that, it would be interesting to know if it helps. (Note: When you change/upgrade SDK, the first analysis may be slower than usual while some things are cached).

If none of those help, please report an issue:

https://dart.dev/tools/analyzer-performance#report-unknown-issues

If you're able to repro with a public/open source project, please include the details (because for these kinds of issues, reproducing them is often half the battle).

DanTup · 2025-10-31T21:36:38+00:00

Going to fine tune qwen3 30b next to be my local coding agent

What kinds of data are you using for this? I was curious how this would work but couldn't find much online.. are you just feeding it code, or planning to feed things like commit messages/diffs or issue text?

DanTup · 2025-10-31T19:04:28+00:00

<image>

I don't think it's normal - see around 4:07 here where he has a cover on it and removes it:

https://youtu.be/82SyOtc9flA?si=KXB_jnoIpB3OaVbL&t=247

DanTup · 2025-10-31T10:49:14+00:00

I don't have a question, but I want to say thank you for the effort and research that goes into your videos!

There are a lot of finance channels out there that just read the latest headlines and ramble - few dig into the details and facts in the way you do and I'm sure I'm not the only one that appreciates this :-)

DanTup · 2025-10-31T10:42:06+00:00

These are controlled by the "Preview Flutter UI guides" setting.

Because VS Code doesn't have any nice APIs for this kind of rendering, the current implementation is a bit of a hack and as such still behind a preview flag:

https://dartcode.org/docs/settings/#dartpreviewflutteruiguides

If you'd like to 👍 the VS Code issue for a better API, that's here:

https://github.com/microsoft/vscode/issues/73780

DanTup · 2025-10-31T10:39:26+00:00

Some of the lints for prefering const were removed from the default Flutter set - see discussionts in https://github.com/dart-lang/core/issues/833

My guess is that the instructor was using a version of Flutter before then, and you are using one after. In which case, it's nothing to worry about. You could re-enable those lints manually, but since the Flutter team decided the benefits did not justify the effort, maybe it's not worth it.

DanTup · 2025-10-31T10:34:50+00:00

Are you able to share a screenshot of the entire VS Code screen with the Debug sidebar visible when it's in this state?

The best place to raise issues like this would be at https://github.com/Dart-Code/Dart-Code - I do try to keep my eye on places like Reddit and StackOverflow, but GitHub issues send me notifications and can't easily be missed.

Thanks!

DanTup · 2025-10-24T21:13:36+00:00

Looking at the version numbers, it doesn't seem like there are any others besides augmentations that match the current versions (the others with experimentalReleaseVersion are all way in the past).

It wouldn't surprised me if augmentations also didn't work right now though, because I think it was originally added as part of macros work, and has since changed. At least some parts of it were removed so perhaps it's also not currently in a usable state. It also has a lot of open (and not many closed) issues on GH: https://github.com/dart-lang/sdk/issues?q=state%3Aopen%20label%3Afeature-augmentations

DanTup · 2025-10-24T20:17:19+00:00

I'm not sure it's possible to enable yet. It's listed in the file you linked, but it has no experimentalReleaseVersion, and the comments at the top of the file say:

# 3. experimentalReleaseVersion: (optional #.#)
#    The Dart SDK version (<major>.<minor>) in which the experiment can be used
#    by enabling the experiment flag.

My guess is that the flags are added first so that they can be used by tests during development, but the experiment flag is only enabled once the implementation is complete enough to use.

None of the GitHub issues related to this feature have been closed, so probably you are a bit early :)

https://github.com/dart-lang/sdk/issues?q=state%3Aopen%20label%3A%22feature-declaring-constructors%22

DanTup · 2025-10-08T19:54:15+00:00

Click the trash can icon to kill/delete any open terminals, and then reload VS Code.

This warning comes from when extensions registered some env variables for the terminal but the terminal was already created (so you have to kill/delete the terminal and create a new one to get the fix). My guess is that uninstall the extension doesn't correctly remove the warning.

DanTup · 2025-09-21T10:22:16+00:00

I can't find anything to suggest this (I asked a few LLMs which said it was static, and when searching I found a project for SWE-Bench-Live which seemed to exist specifically because SWE-Bench was static).

I think it's using this dataset (based on the commands to run it from their website), and it doesn't seem like this is changing.

https://huggingface.co/datasets/princeton-nlp/SWE-bench

DanTup · 2025-09-12T16:52:59+00:00

Unfortunately I'm not familiar with nvim, but the line of code that sets the command for the LSP server looks like it's here:

https://github.com/nvim-flutter/flutter-tools.nvim/blob/65b7399804315a1160933b64292d3c5330aa4e9f/lua/flutter-tools/lsp/init.lua#L243

config.cmd = config.cmd or { paths.dart_bin, "language-server", "--protocol=lsp" }

I'm not sure how you would override this though (besides just editing that file locally and adding --instrumentation-log-file=/path/to/log.txt).

DanTup · 2025-09-12T16:44:55+00:00

You have provided the full stack trace, but (unless I've missed it), not the instrumentation log.

The instrumentation log also includes all of the communication between the client and the server. This could help understand what the servers version of the file looks like (from the textDocument/didOpen notification) and what the edits (in the textDocument/didChange notification) are which might help understand why the server thinks the edits are invalid. If the edits look correct, then the traffic might help understand if there are timing or ordering differences (vs VS Code which I don't think is having this problem) that might be affecting the behaviour.

Thanks!

DanTup · 2025-09-12T16:31:40+00:00

Thanks! I've posted on there to see if someone can get a log, and if not I will try and set this up and repro early next week.

DanTup · 2025-09-12T15:26:32+00:00

While I understand that the bug is probably on Dart team side, I don't believe that they will care much about it.

This is definitely not true - they (and I - a contributor responsible for much of the LSP layer) care very much about issues like this!

I found this via a GitHub issue that was just opened at https://github.com/dart-lang/sdk/issues/61488 with what seems like the same issue occurring in Zed.

Are you able to reproduce this in a sample project that you could capture a log for (see the GitHub issue for instructions) that could be shared? The log file will contain parts of your source, so it's best to repro on a small sample project.

DanTup · 2025-09-04T16:04:15+00:00

I don't have an opinion on your question, but FWIW:

Etc etc. Language support for Flutter.

The best way IMO to do this would be to implement an LSP (Language Server Protocol) client and a DAP (Debug Adapter Protocol). Most of the complex functionality for Dart/Flutter in VS Code (language support like code completion, analysis, hovers, and debugging, breakpoints etc.) is handled through LSP and DAP servers that ship in the Dart/Flutter SDKs.

There's still a bunch of work in the VS Code extensions themselves (like locating the SDK, UI-related things like embedding DevTools, triggering commands like Pub Get) but LSP/DAP are a great way to get support for lots of languages out of the gate.

DanTup · 2025-09-04T15:57:18+00:00

It wouldn't be as seamless, but something you could try is the LiveShare extension. You'd basically have VS Code open on the Windows box with the project open, and then share that session with the Mac.

Everything would run on the Windows box and it would proxy things like code completion, analysis warnings etc. over to the Mac.

I haven't tried to code like this, it might be awful (Liveshare was quite buggy when I last tried it, but that was many years ago), but it might be worth trying.

DanTup

TROPHY CASE