GitHub Review Bot webhook returns 200 OK but no review task is created
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
- Tipo di issue
- Bug
- Chiarezza
- Da chiarire
- Stato di attività
- Attiva
- Stack tecnologico
- github, typescript
Direzione di ricerca
Start at the GitHub webhook handler and trace pubhost.PickHost() through ReviewAgent.ModelID lookup, review image selection, VM creation, and the GitTaskUsecase.Create transaction. Check backend logs for the reported account and Git Bot, including transaction rollbacks and task-slot allocation. Done means an accepted pull_request.opened event creates a visible Review Task and runs the cloud review.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Feedback details:
I am configuring the hosted MonkeyCode GitHub Review Bot for a private GitHub repository.
Environment:
- Hosted MonkeyCode: monkeycode-ai.net
- Git platform: GitHub
- Host: MonkeyCode Built in
- Repository: private GitHub repository
- MonkeyCode Global GitHub App is installed
- Repository is explicitly selected in the GitHub App installation
- GitHub App has read/write access to code, issues, pull requests, repository hooks, workflows and actions
- A separate MonkeyCode Git Bot was created in /console/gitbot
- GitHub PAT is limited to the repository and has Contents Read/Write and Pull Requests Read/Write
Observed behavior:
- GitHub webhook is configured with the webhook URL generated by MonkeyCode.
- Secret signing is enabled.
- Only pull_request events are enabled.
- A pull_request.opened event is delivered successfully.
- GitHub reports HTTP 200 from MonkeyCode.
- Response body is exactly:
ok
- Redelivering the same pull_request.opened event also returns HTTP 200 / ok.
- /console/gitbot -> Review tasks remains empty.
- No MonkeyCode review task is created.
- No review comment is posted on the PR.
- Mentioning @monkeycode-ai on the PR also produced no task or response.
The GitHub webhook transport therefore appears to work, but Git task creation does not occur after the webhook is accepted.
Could you please check the backend logs for this account/Git Bot and specifically verify failures around:
- pubhost.PickHost
- ReviewAgent.ModelID
- review model lookup
- GitTaskUsecase.Create
- VM creation
- Basic-plan concurrency / task-slot allocation
Expected result:
A pull_request.opened event accepted by the configured MonkeyCode Git Bot should create a visible Review Task in /console/gitbot -> Review tasks and run the cloud review without requiring an open browser session.
Additional source-level findings
I checked the current implementation more closely:
PR dedup is SETNX("pr_review:" + pr.HTMLURL, ..., 5 minutes). Therefore manual redeliveries of the same PR within 5 minutes are intentionally skipped before host selection. Our failing redelivery occurred outside that window, so dedup does not explain the observed failure.
PublicHostUsecase.PickHost() loads the public-host pool, calls taskflow.Host().IsOnline, and only considers hosts where OnlineMap[host.ID] == true and Weight > 0. If none qualify it returns no online public hosts found.
The GitBot-selected host is not used by the GitHub webhook path; the handler always calls pubhost.PickHost().
Review model resolution is server-side via cfg.ReviewAgent.ModelID. Invalid UUID yields failed to parse model id; missing DB model yields review model not found.
Review VM creation also depends on server-side cfg.ReviewAgent.Image.
Task/GitTask/VM/GitBotTask creation is wrapped in a transaction. A VM creation failure can therefore roll back the records entirely, which would explain why /console/gitbot -> Review tasks remains empty rather than showing a failed task.
Given the accepted webhook (200 ok) and no visible task, please check logs around:
PickHost() → review model lookup → review image / VM creation → transaction rollback.
Current UID: b69f3303-7ce5-41e7-a9e8-be3f213dbeaf
- Lingua principale
- TypeScript
- Stelle
- 4.9k
- Fork
- 749
- Merge medio
- 9h 25m
- PR unite (30g)
- 74
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di chaitin/MonkeyCode
-
Add a One-Click Copy Button for AI Agent ResponsesForse già presa @DhruvKhambhata l’ha presa 15 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
chaitin/MonkeyCode#1437 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
这个位置的停止服务,要二次确认,Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
chaitin/MonkeyCode#1286 ·
I maintainer di solito rispondono entro 1 giorno
-
官网试用明亮模式弹窗内容与背景重叠Forse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
chaitin/MonkeyCode#1069 ·
I maintainer di solito rispondono entro 1 giorno
-
fix(frontend): 补充任务预览弹窗的无障碍描述Forse già presa @goalup l’ha presa 105 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
chaitin/MonkeyCode#915 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
【技能】弹窗内容溢出Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
chaitin/MonkeyCode#907 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di chaitin/MonkeyCode
Issue simili
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
area:ui bug effort:S priority:P2
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
Typo in WSL project description on Projects pageForse già presa @akhil9tiet l’ha presa oggi. Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 75/100
microsoft/opensource.microsoft.com#1066 · 1 commento ·
-
ArcGIS Maps SDK for JavaScript c-carousel calcite-design-tokens enhancement impact - p3 - not time sensitive needs triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
Esri/calcite-design-system#15565 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
linkwarden/linkwarden#1891 ·
I maintainer di solito rispondono entro 1 giorno