Migrate eval_task queries to SQLAlchemy #4974
Draft
+457
−425
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Summary
models/eval_task.pywith EvalTask and TaskAttempt SQLModel modelsqueries/eval_task_queries.pywith SQLAlchemy query functionsroutes/eval_task_routes.pyto use the new query moduleTaskStatus,FinishedTaskStatus,TaskStatusUpdate,EvalTaskRow,TaskAttemptRow, and all eval_task methods)Uses
text()queries for complex view-based queries (eval_tasks_view) since the view-based approach is more maintainable than pure SQLAlchemy for this schema.Part of stack to migrate app_backend from raw SQL to SQLAlchemy.