modular / modular/vscode-mojo

[BUG] Mojo LSP starts parsing multiple times in Google's Antigravity

Open
#42 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
38
Forks
17
Avg merge
4d 13h
Merged PRs (30d)
13

Description

Actual behavior

Sometimes the Mojo vscode extension/language server appears to be parsing the files multiple times concurrently in Google's Antigravity which causes the language server to never finish and just hangs forever. **Note I have not tested or reproduced this issue with VSCode, but antigravity is a modified fork of vscode so the extension is the same extension.

Image

You can see in the image how the document is being parsed multiple times. I've killed the background parsing processes repeatedly but they keep starting up when I save my file. I'm not sure if this is a bug with the Mojo language server/extension, or if this is an issue with Google's Antigravity. Restarting the LSP Server works to resolve the issue, but it happens frequently enough to become an issue. Sometimes I repeatedly press Ctrl. S to save quickly which might increase the likelihood of the issue, though I can't be certain.

Expected behavior

The language server should parse my documents (when it does successfully parse through the handful of documents I have, it does so in a matter of seconds) It should be quickly parsing each document once and not hanging forever causing syntax highlighting and errors to never resolve.

Steps to reproduce
  • Open some mojo files in Google's Antigravity
  • Make a change to one of the files
  • Press Ctrl S (possibly repeatedly multiple times)
  • Notice that often the Parsing Document notification on the status bar at the bottom hangs at parsing the current file and does not resolve. Clicking on it shows the list of files being parsed and often it shows the same file being parsed multiple times and never finishes.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with the Mojo VS Code extension in Google's Antigravity: open Mojo files, save one repeatedly, and inspect the Parsing Document status and concurrent processes. Compare behavior with VS Code if possible to determine whether the extension or Antigravity is responsible. Done means each document is parsed once, parsing finishes, and syntax highlighting and errors resolve.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.