add: TestTraceOperations for trace-related functionality

[jack-devhub]

Changes

• Added a new test case in src/e2etests/judgment_client_test.py that makes a request to the endpoint and asserts the expected response.
• Ensured the test runs as part of the existing test suite.

Testing

• Ran the test locally to confirm it executes successfully.
• Verified the endpoint response matches expectations.

[JCamyre]

Were your tests able to pass when you ran them? My tests failed even when I added the eval_complete column to the traces table in the Supabase.
It seems your .gte("created_at", f"now()-{hours}h") # PostgreSQL interval notation is causing issues.

postgrest.exceptions.APIError: {'code': '22007', 'details': None, 'hint': None, 'message': 'invalid input syntax for type timestamp: "now()-1h"'}

Did you mean to add this code only after you update the traces table to be a time series DB?

[jack-devhub]

Were your tests able to pass when you ran them? My tests failed even when I added the eval_complete column to the traces table in the Supabase. It seems your .gte("created_at", f"now()-{hours}h") # PostgreSQL interval notation is causing issues.

postgrest.exceptions.APIError: {'code': '22007', 'details': None, 'hint': None, 'message': 'invalid input syntax for type timestamp: "now()-1h"'}

Did you mean to add this code only after you update the traces table to be a time series DB?

Updated the code into the judgment and resolved the time error as well as the query.

[JCamyre]

Run UT's