Repository navigation
test(server): guard long-event overlap consumers - #215
TimeToBuildBob wants to merge 2 commits into
Conversation
[Low impact] No new issues were found; the stated dependency merge gate should remain in place. SummaryAdds four HTTP regression cases for a 48-hour event queried inside its second day.
Reviews (2) · Last reviewed commit: "test(server): verify long-event reads pr..." · Reviewed by Greptile |
Git-Session-Id: d8a22e8f-4386-4789-bab9-5ddd743d4b08
Git-Session-Id: 4cb0ead5-8800-5d0b-ae25-627bf2fd2fdf
e5cae17 to
61c0430
Compare
|
@greptileai review |
|
Rebased onto current master There is now no Force-with-lease push completed with hooks enabled; the Greptile helper accepted one fresh review request for this exact head. Latest-head CI/review is pending; no merge performed. |
Summary
Integration regressions for #213 and ActivityWatch/aw-core#194; depends on core repair ActivityWatch/aw-core#197.
Adds real Flask HTTP tests against a disposable Peewee database for a 48-hour event queried wholly inside its second day:
sum_durations(query_bucket(...))andquery_bucket_eventcount(...).The tests preserve existing clipped Peewee behavior (one-hour interior result), not full-duration AQL semantics. Reads must not alter the stored 48-hour event.
make testexplicitly runs the new file, so it cannot silently miss CI.Verification
make testwith repaired core: 148 passed;make typecheck: 32 files clean.test_client.py: 231 passed with repaired core.Deliberate merge gate
Draft until an aw-core dependency containing ActivityWatch/aw-core#197 is available and adopted. The locked aw-core 0.5.18 still has the defect, so these tests are expected RED with the unmodified lock. Do not merge a test suite that requires an unshipped dependency. No server production-code change or temporary version skip is proposed; the required follow-through is update the dependency/lock after a containing core release, replay this suite, then mark ready.