[Bug] Antigravity 2.33.0 不再默认开启 --remote-debugging-port=0,导致 GravityBox 一直等待连接
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- macos
- Domain
- desktop
Research direction
The issue names no files, so start by finding where GravityBox spawns or launches Antigravity (a shell open -a Antigravity call or an NSWorkspace/Process launch in the app's launch helper) and where status.json with mode: "waiting" is written. Reproduce by upgrading to 2.33.0 and confirming ~/Library/Application Support/Antigravity/DevToolsActivePort is missing. Done means the launcher appends --remote-debugging-port=0 (plus a menu entry to restart in debug mode) and the wait loop connects without the manual command.
Written by the indexing model from the issue text.
Description
- 环境:macOS (Apple Silicon) / Antigravity
2.33.0(官方正式版)/ GravityBoxv1.1.1 - 现象:Antigravity 自动升级到
2.33.0后,GravityBox 一直停在「等待 Antigravity 打开」(status.json显示mode: "waiting",windows: 0),界面未汉化、HUD 也未挂载。 - 原因排查:
- 对比
2.32.x与2.33.0,2.33.0进程启动时不再默认携带--remote-debugging-port=0,导致~/Library/Application Support/Antigravity/DevToolsActivePort未生成。 - 退出后改用
open -a Antigravity --args --remote-debugging-port=0启动,即正常生成DevToolsActivePort,GravityBox 立刻连接成功,中文与 HUD 均恢复正常。
- 对比
- 建议:希望在 GravityBox 中增加「以调试模式启动 / 重启 Antigravity」的入口(或在使用 GravityBox 拉起 Antigravity 时自动附加
--remote-debugging-port=0),以兼容2.33.0及后续版本。
- Dominant language
- JavaScript
- Stars
- 21
- Forks
- 0
- Avg merge
- 30m
- Merged PRs (30d)
- 9
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from Enzoo404/gravitybox
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
Enzoo404/gravitybox#18 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Enzoo404/gravitybox#20 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 40/100
Enzoo404/gravitybox#19 ·
Maintainers usually reply within 1 day
-
[FEAT] 搞个Windows版本Openenhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 8/100
Enzoo404/gravitybox#17 · 1 comment ·
Maintainers usually reply within 1 day
All issues in Enzoo404/gravitybox
Similar issues
-
bug pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pydantic/pydantic-ai#13939 ·
Maintainers usually reply within 1 day
-
self-host
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
funmusicplace/mirlo#2625 ·
Maintainers usually reply within 1 day
-
Bug Tests
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
JSPrismarine/JSPrismarine#3271 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 85/100
sindresorhus/eslint-plugin-unicorn#4034 ·
Maintainers usually reply within 1 day
-
Content:WebExt needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day