Fix ACE Optimizer Input/Output Confusion #456
Conversation
The AxACE optimizer was incorrectly passing the entire example, including output fields, to the curator's `question_context`. This caused the curator to generate a playbook that confused inputs and outputs. This commit fixes the issue by filtering the example object based on the program's input signature before serializing it to `question_context`. Additionally, this commit: - Adds a unit test to verify that the `question_context` is correctly formed. - Removes several `console.log` statements from the test suite. - Refactors the test suite to use the `flow()` factory function instead of the deprecated `new AxFlow()` constructor.
|
👋 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. New to Jules? Learn more at jules.google/docs. |
This PR fixes a bug in the AxACE optimizer where it was incorrectly passing output fields to the curator's
question_context, leading to a faulty playbook. The fix ensures that only input fields are passed to the curator. The PR also includes a new unit test to verify the fix and several improvements to the test suite.PR created automatically by Jules for task 17621115354183839524 started by @dosco