Skip to content

correct: Type the correction deadline as always set - #82

Closed
BenWestgate wants to merge 1 commit into
codex/37-mixed-case-correctionfrom
claude/project-thread-b1oz3e
Closed

BenWestgate wants to merge 1 commit into
codex/37-mixed-case-correctionfrom
claude/project-thread-b1oz3e

Conversation

@BenWestgate

Copy link
Copy Markdown
Owner

Requested by Ben · project thread

Before: #42's head (7e398b0, "Schedule embedded mixed-case recovery") fails CI on all six OS/Python jobs. Tests pass, but mypy reports two errors at src/codex32/_cli_input.py:549 and :565, where it assigns float | None to a variable typed float.

After: mypy is clean and #42 can go green once this is merged into its branch.

_correction_candidates always fills in a missing deadline (deadline = monotonic() + 10 if deadline is None else deadline) before it returns one. Its return annotation still said float | None, and the new scheduling code feeds that value back into the local deadline.

How: the return annotation now says float. There is no runtime change.

Checked on Python 3.13 with mypy (clean), ruff check and format (clean), and 887 tests passing in both normal and -O mode.

🤖 Generated with Claude Code

https://claude.ai/code/session_01E75K4nCzge7jFwjwDgeBrR


Generated by Claude Code

_correction_candidates always fills in a missing deadline before
returning it, but its annotation still said float | None. The
mixed-case scheduling commit feeds that value back into the local
deadline, so mypy rejects both assignments and CI fails on every OS.
Narrow the return annotation to float.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E75K4nCzge7jFwjwDgeBrR
@BenWestgate BenWestgate self-assigned this Sep 30, 2026
@BenWestgate

Copy link
Copy Markdown
Owner Author

Superseded by #42 head 97d2080, which contains this exact one-line return-type correction. Strict mypy is clean there and the full exact-head GitHub matrix is green, so keeping a second draft for the same diff would only duplicate review work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants