mesonbuild / mesonbuild/vscode-meson
VSCode requires a restart sometimes a fanthom error occurs.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 138
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
On one of the sessions each time I were to rebuild or reconfigure the build I would get an "Couldn't find header" error until I've restarted VSCode.
I've meson clean'd my build dir, but that didn't help at a time.
I've renamed the folder and it suddenly began happening.
I then have tried removing the build dir and recreating it in both the terminal and VSCode.
I don't have a minimum reproducible sadly.
Meson: v1.7.0
VSCode: Microsoft RPM Repo. v1.100.1
Distro: Fedora 42
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the rebuild or reconfigure flow in VSCode with Meson 1.7.0 on Fedora 42, including after renaming and recreating the build directory. Done means the intermittent "Couldn't find header" error is reproducible and can be resolved without restarting VSCode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- build-system, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100