VasanthandClaude Opus 5.5
162edd41df
- templates/bot_runner.py (new, no Qt): runs the bot as a child process (unbuffered, UTF-8), tails its output, keeps raw lines in bot_raw.log, and turns lines into step/log/status events. Step markers and friendly rules use specific substrings, first match wins; unmatched error lines are always shown, other unmatched lines hidden. Dry run: python dashboard/bot_runner.py prints the events the page would get. - bridge.py: delegates to bot_runner, one run at a time, restores the saved dark mode on every page load (fixes sample-data mode in PyQt), adds load_latest_report / download_report slots the page calls. - SKILL.md: skip the stack question for a PyQt project; desktop wiring steps from the bot's real output; verify steps for the host. - tests: assert-based self-check for the line logic and run loop; Seam 1 run replay (status dot, Run button, steps, log) and wired-page mode; fixture b-pyqt-bot and its Seam 2 eval (all 14 checks pass). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.2 KiB
2.2 KiB
Dashboard data contract (no-AI)
All updates use one envelope: {"event": "<name>", "data": {...}}.
- Desktop (PyQt): Python calls
window.__pyMsg(json)viarunJavaScript(seebridge.py).bot_runner.pyturns the bot's output lines intostatus,stepandlogevents, and keeps every raw line inbot_raw.log. - Web: the page polls
GET {API_BASE}/dashboard(returnsdashboard_data) andGET {API_BASE}/run/status→{"running": bool, "events": [envelope, ...]}. Poll fast (2s) only while running. - No bot yet: with
SAMPLE_DATA = true, the page answers its own data actions with sample envelopes.
Bot/backend → page
| event | data |
|---|---|
status |
{state: "ready"|"running"|"done"|"error", msg} |
step |
{label: <one of STEPS>, pct: 0-100} |
log |
{msg: <plain English>, type: "info"|"success"|"warn"|"error"} |
dashboard_data |
{batches: [{batch_id, date, state: "completed"|"inprogress"|"notcompleted"|"cleared", items_total, items_done, ...}]} |
report_data |
{rows: [{...REPORT_COLUMNS keys, status, bucket: "success"|"attention"|"failed"}]} |
set_user |
{username, emp_id, role} |
apply_dark |
{on: bool} |
Optional (only if the section was chosen): cpstate {kind: pending|active|done|stuck, cp: int}, admin_data, batch_detail.
Page → bot/backend (Qt @pyqtSlot names / web POST {API_BASE}/<slot-with-dashes>)
load_dashboard, start_automation, request_stop, load_latest_report, download_report, set_dark(on), logout.
Rules (learned on Tebra)
- Log the raw bot line to a file/DB; show only friendly text on screen. Never hide an error line.
- Step markers: match the bot's printed lines by specific substring (e.g.
[step 3]), not a bare word. A bare word matches unrelated lines. - Derive
state: Pending + today =inprogress; Pending + older day =notcompleted. - Report
bucket: success = {processed successfully, posted, completed}; failed = {error, failed}; everything else = attention. - Run the bot in a separate process that writes to a log file, and have the UI tail that file. When pywinauto/UIA runs inside a Qt worker thread, its reads are unreliable (Tebra bug-094).