Added tests/stress/test_atypical_scenarios.py — 28 scenarios covering
atypical user inputs and environments that the normal tests assume
away. Surfaced one real UI bug in the process.
Bug found and fixed
- CLI display of negative elapsed time when NTP jumps backward
between claim_task and complete_task. The kernel faithfully stores
started_at > ended_at; both CLI display sites (_cmd_show's Runs
section at line 685, _cmd_runs's table at line 1153) now clamp
elapsed to max(0, end - start), matching the dashboard JS which
already had the same Math.max(0, ...) clamp. Regression test
test_cli_show_clamps_negative_elapsed forces a future started_at
via raw UPDATE and verifies neither show nor runs prints a
`-<digits>s` token.
Atypical scenarios covered (all passing, 28 total)
Data:
- unicode_and_emoji: CJK, RTL (Hebrew/Arabic), ZWJ emoji sequences,
control chars, null bytes in titles + metadata
- huge_strings: 1 MB body + 1 MB summary + 50-level nested metadata
- sql_injection_attempts: 6 classic payloads, parameterized queries
hold across every string field
- newlines_in_summary: full preserved on run, first line in event
payload for notifier brevity
- malformed_metadata_via_cli: 4 bad JSON values each cleanly
rejected with stderr error, no partial task mutation
- empty_string_fields: empty title rejected, whitespace-only title
rejected, empty body accepted
- tenant_with_newlines: multiline tenant strings survive
board_stats
Dependency graphs:
- dependency_cycle: A→B→A refused
- self_parent: cannot depend on itself
- diamond_dependency: child promotes only when both parents done
- wide_fan_out: 500 children promoted in 4ms via complete_task's
internal recompute_ready
- wide_fan_in: 500 parents → 1 child, promotion gated correctly
- parent_in_different_status_states: child stays todo for parent
in ready/running/blocked/triage/archived; only 'done' unblocks
Workspace:
- workspace_path_traversal: dir: workspaces are intentionally
arbitrary paths (documented threat model)
- workspace_nonexistent_path: spawn_failure counter increments,
task returns to ready
Clock:
- clock_skew_start_greater_than_end: kernel stores faithfully,
CLI now clamps at display (see Bug above)
Filesystem:
- hermes_home_with_spaces: works
- hermes_home_with_unicode: works
- hermes_home_via_symlink: two symlinks to same dir share DB
(Path.resolve() in _INITIALIZED_PATHS)
Scale extremes:
- huge_run_count_on_one_task: 1000 runs → list_runs in <1ms,
build_worker_context 3ms/63KB (flagged: unbounded on
retry-heavy tasks; v2 cap candidate)
- hundred_tenants: 5000 tasks / 100 tenants → stats 1ms, list 26ms
- comment_storm: 1000 comments → 50KB worker context (same
unbounded-context flag)
Lifecycle:
- completed_task_reclaim_attempt: done tasks can't be
re-claimed/re-completed/blocked
- archived_task_resurrection_attempt: archived tasks invisible to
default list + all ops refused
- unassigned_task_never_claims: dispatcher skips, task untouched
Assignees:
- assignee_with_special_chars: @-signs, dots, CJK, emoji, 200-char
names, empty strings all handled
Concurrency:
- idempotency_key_race: two concurrent processes calling
create_task with same key both get back the SAME task id,
exactly one row in DB
Dashboard:
- dashboard_rest_with_weird_inputs: empty/huge/unicode titles,
unknown fields, type mismatches handled correctly (200 for
valid, 400/422 for invalid)
Observations flagged for v2 (not fixed, not blocking)
- build_worker_context is unbounded on retry-heavy tasks (1000 runs
→ 63KB) and comment-heavy tasks (1000 comments → 50KB). A
`--max-prior-attempts` / `--max-comments` cap would be appropriate.
- `dir:` workspace paths are intentionally arbitrary; docs should
note the threat model (trusted local user; path is stored
verbatim, not sandboxed).
183/183 main kanban suite pass. Stress suite still opted out by
default; enable with `pytest --run-stress` or run scripts directly.
Teknium
63b7b6d5bd