python-jsonl-mixed-str-int-event-ids
Diagnosed, patched, and verified. Final solution file: ~/work/SOLUTION.md; patched scripts in ~/.hermes/skills/coding-hermes-foreman/scripts/.
Root cause: Fleet board scripts assumed event ids were always int. Legacy JSONL files carry hex string ids (ef6e3908, a1b2c3d4) alongside modern ints. In Python 3, max()/> between mixed str and int raises TypeError: '>' is not supported between instances of 'str' and 'int' (Python 2 silently compared, which is why the mismatch aged in unnoticed).
Fix: a coerce_id() helper that normalizes every raw id into a comparable int before any max()/comparison:
- real int → itself (bool → 0, since bool subclasses int)
- digit string → int(str) ("7" → 7)
- everything else (hex strings, None, "", missing) →0`
Applied at every comparison/max site in both append_board_event.py and board_jsonl_parity_probe.py.
Verification (all run in this sandbox):
- Reproduced the exact TypeError with the buggy version (exit 1)
- Fixed append_board_event.py on mixed file → next id would be: 8 (ids [1,0,3,0,7,5], max 7)
- Fixed probe → latest id: 7 | duplicate id lines: [4] (both hex → 0)
- Regression: int-only file → 31, empty file → 1, no exceptions, exit 0
- coerce_id() table confirmed: 1→1, '7'→7, 'ef6e3908'→0, None→0, True→0, -3→-3, '042'→42
One note worth flagging for the fleet skill: since all non-decimal legacy hex ids collide at 0, multiple distinct legacy events map to the same numeric key. The patched code now runs correctly, but if event-id uniqueness matters for parity/duplicate detection, those 0-keyed rows will be treated as duplicates — you may want to exclude 0-coerced ids from duplicate checks or keep the raw string alongside the numeric key.
# Evidence - Problem class: python-jsonl-mixed-str-int-event-ids - Model: openrouter/deepseek/deepseek-v4-flash-0731 - Solved: 2026-08-27T18:16:24.903Z - Verification: solution produced by pi in sandbox; see signatures.json
{"description": "Fleet board scripts (append_board_event.py, board_jsonl_parity_probe.py) crashed with TypeError: > not supported between instances of str and int on events.jsonl files carrying legacy string event ids (e.g. ef6e3908) alongside modern int ids. Fix: coerce id to int when isinstance str and isdigit(), else 0/None, before max()/comparison. Both scripts patched in ~/.hermes/skills/coding-hermes-foreman/scripts/.", "environment": "", "language": "", "model": "openrouter/deepseek/deepseek-v4-flash-0731", "problem_class": "python-jsonl-mixed-str-int-event-ids", "provider": "openrouter", "solved_at": "2026-08-27T18:16:24.903Z", "version": ""}Diagnosed, patched, and verified. Final solution file: ~/work/SOLUTION.md; patched scripts in ~/.hermes/skills/coding-hermes-foreman/scripts/.
Root cause: Fleet board scripts assumed event ids were always int. Legacy JSONL files carry hex string ids (ef6e3908, a1b2c3d4) alongside modern ints. In Python 3, max()/> between mixed str and int raises TypeError: '>' is not supported between instances of 'str' and 'int' (Python 2 silently compared, which is why the mismatch aged in unnoticed).
Fix: a coerce_id() helper that normalizes every raw id into a comparable int before any max()/comparison:
- real int → itself (bool → 0, since bool subclasses int)
- digit string → int(str) ("7" → 7)
- everything else (hex strings, None, "", missing) →0`
Applied at every comparison/max site in both append_board_event.py and board_jsonl_parity_probe.py.
Verification (all run in this sandbox):
- Reproduced the exact TypeError with the buggy version (exit 1)
- Fixed append_board_event.py on mixed file → next id would be: 8 (ids [1,0,3,0,7,5], max 7)
- Fixed probe → latest id: 7 | duplicate id lines: [4] (both hex → 0)
- Regression: int-only file → 31, empty file → 1, no exceptions, exit 0
- coerce_id() table confirmed: 1→1, '7'→7, 'ef6e3908'→0, None→0, True→0, -3→-3, '042'→42
One note worth flagging for the fleet skill: since all non-decimal legacy hex ids collide at 0, multiple distinct legacy events map to the same numeric key. The patched code now runs correctly, but if event-id uniqueness matters for parity/duplicate detection, those 0-keyed rows will be treated as duplicates — you may want to exclude 0-coerced ids from duplicate checks or keep the raw string alongside the numeric key.
# Evidence - Problem class: python-jsonl-mixed-str-int-event-ids - Model: openrouter/deepseek/deepseek-v4-flash-0731 - Solved: 2026-08-27T18:16:24.903Z - Verification: solution produced by pi in sandbox; see signatures.json
{"description": "Fleet board scripts (append_board_event.py, board_jsonl_parity_probe.py) crashed with TypeError: > not supported between instances of str and int on events.jsonl files carrying legacy string event ids (e.g. ef6e3908) alongside modern int ids. Fix: coerce id to int when isinstance str and isdigit(), else 0/None, before max()/comparison. Both scripts patched in ~/.hermes/skills/coding-hermes-foreman/scripts/.", "environment": "", "language": "", "model": "openrouter/deepseek/deepseek-v4-flash-0731", "problem_class": "python-jsonl-mixed-str-int-event-ids", "provider": "openrouter", "solved_at": "2026-08-27T18:16:24.903Z", "version": ""}