Fix Chrome session list API pagination in IDE beta 9
This commit is contained in:
1 parent
fa63e03eb7
commit
ff2eb47302
7 files changed
+189
-8
No files matched your search
+15
-2
@@ -1,7 +1,7 @@
|
||||
# AITURK Chrome beta
|
||||
|
||||
Windows / Chrome MV3 side panel for existing local AITURK IDE conversations.
|
||||
Requires AITURK IDE 1.0.0-beta.7 or later; see `KURULUM.txt` for Turkish setup.
|
||||
Requires AITURK IDE 1.0.0-beta.9 or later; see `KURULUM.txt` for Turkish setup.
|
||||
|
||||
The extension talks only to `online.turkservis.aiturk` using Chrome native
|
||||
messaging. The per-user .NET Framework host authenticates to Electron's random
|
||||
@@ -12,7 +12,8 @@ runtime identity, then submits only the new prompt. No parallel agent backend,
|
||||
history reconstruction, model API key in the browser or telemetry is involved.
|
||||
|
||||
Only the active local profile is supported. The list searches titles among
|
||||
desktop sessions in the most recent 200 records. The transcript shows the last
|
||||
the most recent 200 desktop sessions (two API pages of at most 100, filtered
|
||||
server-side before pagination). The transcript shows the last
|
||||
40 records, with up to 8,000 characters per visible message; the model's existing
|
||||
context is not truncated by this display policy. Approvals and clarifications
|
||||
remain in the IDE. A backend event is stamped once and delivered to every
|
||||
@@ -40,6 +41,18 @@ npm ci --workspace apps/desktop --include-workspace-root
|
||||
node --test apps/chrome/tests/panel.test.mjs
|
||||
```
|
||||
|
||||
Exercise the production FastAPI session router and real temporary SQLite stores
|
||||
with the JS bridge (no model requests or user data):
|
||||
|
||||
```powershell
|
||||
$env:AITURK_TEST_PYTHON = 'C:/path/to/python-with-hermes-dependencies.exe'
|
||||
node --test apps/chrome/tests/sessions-api.test.mjs
|
||||
```
|
||||
|
||||
This contract test reproduces the original 422 for an oversized page, then
|
||||
verifies 200 desktop conversations across two valid pages, profile isolation,
|
||||
short/empty lists, archived/empty/cron exclusion and bounded pagination.
|
||||
|
||||
Run backend fan-out and replay tests with the canonical hermetic runner:
|
||||
|
||||
```bash
|
||||
|
||||
Reference in new issue
Block a user