Open
Conversation
- context.md: background, current state analysis, problem statement - prd.md: product requirements with 4 capabilities, user stories, acceptance criteria - research.md: analysis of current EvaluationQueue implementation - rfc.md: technical RFC with two solution options (extend runs vs new domain)
- competitive-analysis.md: anonymized analysis of competitor's approach - rfc.md: added Solution C using metadata-based queues (no new tables) - Updated recommendation: Solution C for v1 (1-2 weeks vs 4-5 weeks) Key insight: annotations and review status can be stored as metadata on existing items, with queues as filtered views rather than entities.
…re/webhooks # Conflicts: # api/entrypoints/routers.py # api/oss/src/routers/variants_router.py
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
[feat] Extend `queues`
The TimestampModel and UserUpdate Pydantic models used datetime.now(timezone.utc) evaluated at import time as the default value for created_at/updated_at fields. This baked the server startup timestamp into the OpenAPI schema, causing the daily docs CI to detect spurious changes and create a new PR every run.
fix(ci): stop docs CI from creating daily phantom PRs
docs: add endoze as a contributor for infra, doc, and infra
[release] v0.88.0
[feat] Add `events` and `webhooks`
[fix] created_at ingestion
|
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR: Loadables Retrieval Alignment
Summary
This PR aligns loadables retrieval behavior across testsets/queries, removes stale design drift in docs, and makes the traces router a first-class traces API (no tracing-shaped response types in traces endpoints).
Change Inventory
API: Testsets
_populate_testcases(...)call-site argument binding bugs by switching to keyword arguments.order,next,limit) when enumeratingtestcase_ids.include_testcases=truereturns bothtestcasesandtestcase_ids./preview/testsets/revisions/retrievecaching policy to cache only wheninclude_testcases=false.API: Queries
next,limit) into stored windowing.tracesandtrace_ids./preview/queries/revisions/retrievecaching policy to cache only when bothinclude_trace_ids=falseandinclude_traces=false.API: Traces Router
TraceResponseTracesResponseTracesQueryRequestformattingfromTracesQueryRequest./preview/traces/queryto always return Agenta trace trees (never spans/opentelemetry formatting).TracingQueryrequest contract fromTracesRouter.query_traces; traces endpoint now consumes onlyTracesQueryRequest.query_ref,query_variant_ref,query_revision_ref).GET /preview/traces/{trace_id}) returningTraceResponse.Docs
docs/designs/loadables/loadables.querying.strategies.mdto include:windowing.nextterminologydocs/designs/loadables/loadables.initial.specs.mdexamples fromcursortonext.docs/designs/loadables/loadables.querying.gap-analysis.mdafter consolidating its useful content into the strategies document.Behavior Summary
/preview/testcases,/preview/traces) remain record-returning endpoints without extra top-level ID arrays.Validation
cd api && ruff format && ruff check --fixpytest -q oss/tests/pytest/e2e/tracing/test_traces_basics.py oss/tests/pytest/e2e/loadables/test_loadable_strategies.py27 passedpytest -q oss/tests/pytest/e2e/testsets/test_testsets_basics.py oss/tests/pytest/e2e/testsets/test_testsets_queries.py oss/tests/pytest/e2e/testsets/test_testcases_basics.py oss/tests/pytest/e2e/tracing/test_spans_basics.py oss/tests/pytest/e2e/tracing/test_spans_queries.py17 passed, 3 skipped(existing flaky skips)pytest -q oss/tests/pytest/e2e175 passed, 3 skipped