scholarr/app
Justin Visser 2c591a0ca3 fix(ingestion,frontend): show live counter immediately on run start
Two issues with the initial implementation:
- Counter only appeared after the first SSE event arrived (scholarProgress null
  kept the v-else static template showing until a scholar completed)
- First events were often dropped because the EventSource hadn't subscribed yet

Fix:
- Backend: emit an initial scholar_progress kickoff event (0/0/N) at the
  start of run_scholar_iteration so the frontend receives total early
- Frontend: gate on isLikelyRunning alone (not scholarProgress); use optional
  chaining with fallbacks so "0 / … visited · 0 finished" shows immediately
  when a run starts, before any SSE events arrive

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-03 18:37:53 +01:00
..
api fix(db,frontend): reserve DB connections for API and reduce frontend polling 2026-03-02 19:09:06 +01:00
auth Initial release prep 2026-02-27 10:46:05 +01:00
db fix(db,frontend): reserve DB connections for API and reduce frontend polling 2026-03-02 19:09:06 +01:00
http after audit 2026-03-01 18:14:22 +01:00
security after audit 2026-03-01 18:14:22 +01:00
services fix(ingestion,frontend): show live counter immediately on run start 2026-03-03 18:37:53 +01:00
__init__.py First product 2026-02-17 14:51:25 +01:00
logging_config.py ci: add ruff linting and mypy type checking 2026-02-26 22:11:41 +01:00
logging_context.py ci: add ruff linting and mypy type checking 2026-02-26 22:11:41 +01:00
logging_utils.py refactor: add structured_log utility to eliminate logging boilerplate 2026-02-26 21:31:32 +01:00
main.py Bugfixeds 2026-03-01 22:54:23 +01:00
settings.py fix(db,frontend): reserve DB connections for API and reduce frontend polling 2026-03-02 19:09:06 +01:00