Implement gRPC API for Test Case Reproduction #4998
Conversation
This commit introduces a new gRPC API for asynchronously reproducing test cases in ClusterFuzz. The API is designed to be a robust and scalable standard for exposing ClusterFuzz capabilities. It includes the following features: - **Asynchronous Job Management:** Clients can start reproduction jobs for multiple test cases and receive a job ID for tracking. - **Persistent State:** Job status is persisted using a simple `dbm` database to survive server restarts. - **Real-time Updates & Polling:** Supports both a server-streaming endpoint (`SubscribeToJobUpdates`) for real-time progress and a polling endpoint (`GetJobStatus`). - **Final Metrics:** A dedicated endpoint (`GetJobResults`) calculates and returns final metrics, such as success and failure percentages. - **Secure by Default:** The API is secured using an API key interceptor that reads valid keys from an environment variable (`VALID_API_KEYS`). The implementation is separated into modules for the server, job management, authentication, and integration with the existing `butler` reproduction logic. A new public function was added to the `butler` script to provide a clean API for this integration.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. |
This change adds a new gRPC service to ClusterFuzz that allows clients to asynchronously reproduce test cases. It provides endpoints to start jobs, get status, stream updates, and retrieve final results with metrics. The implementation includes persistent job storage, API key authentication, and clean integration with the existing reproduction logic.
PR created automatically by Jules for task 2654317184637777705