feat(agents-api): Naive speed improvement to cozo queries by adding limit=1 to all relevant queries

[creatorrr]

Signed-off-by: Diwank Singh Tomer [email protected]

---

Important

Improve CozoDB query performance by adding :limit 1 to relevant queries and restructure CI/CD workflows for agents-api.

• Performance Improvement:
  • Add :limit 1 to CozoDB queries in get_agent.py, get_cached_response.py, and prepare_chat_context.py among others to improve query performance.
• CI/CD Workflow:
  • Rename lint-and-format.yml to lint-agents-api-pr.yml and remove typecheck and test steps.
  • Add test-agents-api-pr.yml for running tests on pull requests.
  • Add typecheck-agents-api-pr.yml for type-checking on pull requests.

^{This description was created by for 4cd6bb0. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 348079e in 17 seconds

More details

• Looked at 479 lines of code in 24 files
• Skipped 0 files when reviewing.
• Skipped posting 1 drafted comments based on config settings.

1. agents-api/agents_api/models/agent/get_agent.py:105

• Draft comment:
  Ensure that adding :limit 1 does not affect the logic where multiple results might be expected. This change is applied across multiple files, so verify its appropriateness in each context.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The PR adds a :limit 1 clause to several CozoDB queries to improve performance by limiting the result set to one record. This is a valid optimization for queries where only one result is expected or needed. However, it's important to ensure that this change does not affect the logic of the application, especially in cases where multiple results might be expected under certain conditions. The change seems consistent across multiple files, and the logic of the queries appears to be maintained. The PR also includes changes to GitHub Actions workflows, splitting linting, testing, and type-checking into separate workflows, which is a good practice for modularity and clarity. Overall, the changes seem appropriate and beneficial for performance and CI/CD process improvements.

Workflow ID: wflow_2DAtnrKOcXGEboh4

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

❌ Changes requested. Incremental review on 248288f in 17 seconds

More details

• Looked at 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 0 drafted comments based on config settings.

Workflow ID: wflow_CUpJ89wxKz5hXqkS

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

👍 Looks good to me! Incremental review on 4cd6bb0 in 11 seconds

More details

• Looked at 27 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 1 drafted comments based on config settings.

1. .github/workflows/typecheck-agents-api-pr.yml:40

• Draft comment:
  The change in the cache key to include ${{ github.base_ref }} is appropriate for ensuring cache specificity to the base branch in pull request workflows.
• Reason this comment was not posted:
  Confidence changes required: 0%
  The change in the cache key for pytype in the typecheck workflow is correct. It ensures that the cache is specific to the base branch, which is useful for pull request workflows. This change is appropriate and aligns with best practices for caching in CI workflows.

Workflow ID: wflow_HQXDGcgmYWom5eVa

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.