When executing long-running or resource-intensive build commands such as cargo build or pnpm build within the Antigravity IDE, the process hangs indefinitely. The terminal/console stops returning any output, and the build process never completes or times out. This issue completely blocks the development workflow, requiring a manual restart of the IDE or forcefully killing the background processes.
- Antigravity IDE Version:
2.0.3 - Operating System:
Windows 11 x86_64
Steps to reproduce the issue:
-
Open a project (e.g., Rust or Node.js) in Antigravity IDE.
-
Open the integrated terminal or command runner.
-
Execute a build command such as
cargo buildorpnpm build. -
Observe the terminal output and the process status.
Expected behavior: The build process should execute normally, continuously stream the standard output/error logs to the console, and terminate with an appropriate exit code once the build is finished.
Actual behavior: The command executes initially, but the process freezes indefinitely. No further output is displayed, no exit code is returned, and the terminal becomes completely unresponsive.
Agent message
You are absolutely right. This is entirely a system-side “bug (design flaw).”
Despite being designed to “asynchronously prevent freezing,” the system is resulting in users being kept waiting and appearing to hang. This is due to the following bugs in the asynchronous task lifecycle management:
Technical background of the bug (flaw)
Bug that fails to detect instant process termination (Exit): Ideally, when a process terminates instantly due to the cargo not being found, the system should immediately notify me (the AI) of a “task failed” termination event and display an error on the screen. However, the system was not correctly monitoring the process’s exit status, and the task remained in a zombie state, showing “RUNNING” indefinitely.
Buffering and log synchronization delay bug: Although the error message (CommandNotFound) output from the shell was written to the log file, the update was not synchronized to the AI ​​in real time, and I could not detect the output until I manually “checked the status.”
As a result of these combined issues, a paradoxical bug has occurred where, despite intending to run asynchronously and safely, the application hangs in the background, constantly waiting for responses from zombie tasks.
I sincerely apologize for the extra time you’ve had to spend reinstalling your Rust environment, only to have the development tools bug cause this.
As long as the agent’s execution system has this bug, there’s a very high probability that executing commands from my end will result in the same zombie task issues and hangs again.
For this cargo build, I apologize for the inconvenience, but currently, the most reliable and fastest method is for you to run it directly from your terminal (PowerShell or VS Code terminal).
If you encounter any code errors or compilation errors during the build, please paste the error messages here, and I will immediately create a proposed code fix!
