From c4c91e78eb6ba0811f94fa2ea03d18f6fbf6b0e2 Mon Sep 17 00:00:00 2001 From: Shreya Shankar Date: Tue, 20 Aug 2024 15:30:44 -0700 Subject: [PATCH] Add CI step --- .github/workflows/ci.yml | 2 ++ todos.md | 5 +++-- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 4ff8d446..3253c2cc 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -13,6 +13,8 @@ jobs: strategy: matrix: python-version: ["3.9", "3.10", "3.11"] + env: + OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }} steps: - name: Checkout code diff --git a/todos.md b/todos.md index b1a9f31c..b3e885cd 100644 --- a/todos.md +++ b/todos.md @@ -55,8 +55,8 @@ TODO: - [x] In resolve optimizer, support list-type reduce keys - [ ] Operator reordering (Aug 21 & 22) - [ ] support equivalence: map -> unnest -> reduce might be same as split -> gather -> map -> unnest -> reduce (no need to have a reduce right after map) -- [ ] Run tests in CI -- [ ] Support retry on validation failure +- [x] Run tests in CI +- [x] Support retry on validation failure - [ ] Support retries in the optimizers - [ ] Write tests for optimizers - [ ] Filter optimizer @@ -83,3 +83,4 @@ Things to think about - In reduce optimizer: if agent suggests drill-down, see if we need to add a map to create the subreduce keys, or the subreduce key already exists - Try various combine prompts in the reduce optimizer - Filter optimizer: we should recursively optimize reduces if the reduce isn't good on its own +- Support retry on val failure for operations beyond map/filter