feat(caretaker-triage): implement LLM triage orchestrator, GCS debug logger, and container build - #28307
feat(caretaker-triage): implement LLM triage orchestrator, GCS debug logger, and container build#28307chadd28 wants to merge 4 commits into
Conversation
…ss action publisher
…orchestrator docstrings
…d parsing, exception handling, and egress env var lookups
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request establishes the foundational infrastructure for the Caretaker Triage Cloud Run worker. It introduces the orchestration layer for LLM-based issue triage, integrates Firestore for distributed locking to prevent race conditions, and implements a Pub/Sub-based egress mechanism for performing GitHub actions like labeling and commenting. These changes provide the necessary plumbing to automate issue triage workflows within the Cloud Run environment. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
|
📊 PR Size: size/L
|
There was a problem hiding this comment.
Code Review
This pull request introduces a Cloud Run Job worker for issue triage, including the main execution loop in main.py, a stubbed triage orchestrator, and Pub/Sub egress utilities for sending label and comment actions. Feedback on the changes highlights a potential vulnerability to unhandled AttributeError exceptions during payload parsing and validation if the decoded JSON is not a dictionary or if expected fields are missing.
…, and container build
|
Will re-open this PR after previous #28306 is merged and this branch is rebased. |
Summary
Implements LLM inference orchestration (
triage_orchestrator.py) using Antigravity SDK, structured GCS debug logging (utils/agent_logger.py), and the Cloud Run Job container build definition (Dockerfile/requirements.txt).Includes a comprehensive end-to-end integration test suite (
tests/test_integration_main.py).Details
triage_orchestrator.py: Invokes the Antigravity Agent with read-only tool policies (allow/deny), system instructions, and triage skill prompts.utils/agent_logger.py: Serializes Antigravity Agent resolved stream chunks to JSON and uploads debug logs to GCS.tests/test_integration_main.py: End-to-end integration test suite verifying the worker execution loop acrossmain.pyandIssuesStore.Related Issues
IssuesStore&validator)How to Validate
Pre-Merge Checklist