Probe ty readiness in CI - #347
Merged
Merged
Conversation
uriahf
marked this pull request as ready for review
August 20, 2026 18:58
Contributor
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
uv run ty check src/rtichokein package CIBaseline
tyreports 11 diagnostics on the current package source:calibration/__init__.pytimesannotation mismatch inperformance_table.pymax()values used as floatsdetails=confusion_matrixprocessing/combinations.pyThe package CI otherwise passes: Ruff lint, Ruff format, build, and all 137 tests.
Scope
Developer tooling only. No type fixes, runtime dependencies, API changes, statistical changes, or functional refactoring.
Recommendation
Keep this probe non-blocking for now. The 11-error baseline is small enough to address incrementally in a follow-up PR; once it reaches zero, make
tyblocking in CI.