Automatic Packages Get on Pubspec change not working if prompt to run "pub get" at startup is ignored
See original GitHub issueDescribe the bug
Hello, I’ve recently encountered with this odd behavior in my project. I’m aware of the dart.runPubGetOnPubspecChanges
setting, which is set to always
.
Trying it with a simpler project, it seems to work correctly.
I would like to know what could be causing it to fail in the other project. Is there any way to show the logger messages with the Extension installed from the store? I can see in the implementation that there are several messages when an early return occurs.
The automatic packages get behavior has been working fine for a long time in this project, so something must have changed recently on my end or on vscode.
To Reproduce Steps to reproduce the behavior:
- Edit pubspec.yaml
- Packages get is not run.
Expected behavior Packages get should run
Please complete the following information:
- Operating System and version: Fedora 37
- VS Code version: 1.74.1
- Dart extension version: 3.55.20221130
- Dart/Flutter SDK version: 3.55.20221129
Issue Analytics
- State:
- Created 9 months ago
- Comments:6 (3 by maintainers)
Top GitHub Comments
Ah, thanks! I see what’s happening. We set that flag as if we’re running pub around the notification that appears in the bottom corner. So if you don’t notice that notification (which VS code hides after ~10s), then it will be forever “locked” as already running, when in reality it didn’t start.
The messages logged with
logger.info
in that class should show up in the extension log. If you trigger the fetch-on-save that isn’t working and then run the Dart: Open Extension Log command, hopefully you can find those logs in there, which might help understand why it was skipped.Please let me know what you find!