==> Synchronizing chroot copy [/home/alhp/workspace/chroot/root] -> [build_96120eae-5adc-4377-91c9-9bfde1e2c497]...done ==> Making package: ty 0.0.49-1.1 (Fri Jun 12 11:37:31 2026) ==> Retrieving sources... -> Cloning ty git repo... Cloning into bare repository '/home/alhp/workspace/build/x86-64-v2/ty-0.0.49-1/ty'... -> Cloning ruff git repo... Cloning into bare repository '/home/alhp/workspace/build/x86-64-v2/ty-0.0.49-1/ruff'... ==> Validating source files with b2sums... ty ... Passed ruff ... Skipped ==> Making package: ty 0.0.49-1.1 (Fri Jun 12 09:41:42 2026) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Installing missing dependencies... resolving dependencies... looking for conflicting packages... Package (14) New Version Net Change extra/compiler-rt 22.1.6-1 54.94 MiB core/libedit 20260512_3.1-1 0.27 MiB extra/libgit2 1:1.9.4-1 3.15 MiB extra/lld 22.1.6-1 7.14 MiB extra/llhttp 9.3.1-1 0.11 MiB extra/llvm-libs 22.1.6-1 163.72 MiB extra/perl-error 0.17030-3 0.04 MiB extra/perl-mailtools 2.22-3 0.10 MiB extra/perl-timedate 2.35-1 0.15 MiB extra/rust 1:1.96.0-1 274.33 MiB extra/zlib-ng 2.3.3-1 0.28 MiB extra/git 2.54.0-1 30.26 MiB extra/maturin 1.13.3-1 24.02 MiB extra/python-installer 1.0.0-1 0.20 MiB Total Installed Size: 558.72 MiB :: Proceed with installation? [Y/n] checking keyring... checking package integrity... loading package files... checking for file conflicts... :: Processing package changes... installing perl-error... installing perl-timedate... installing perl-mailtools... installing zlib-ng... installing git... Optional dependencies for git git-zsh-completion: upstream zsh completion tk: gitk and git gui openssh: ssh transport and crypto man: show help with `git command --help` perl-libwww: git svn perl-term-readkey: git svn and interactive.singlekey setting perl-io-socket-ssl: git send-email TLS support perl-authen-sasl: git send-email TLS support perl-cgi: gitweb (web interface) support python: git svn & git p4 [installed] subversion: git svn org.freedesktop.secrets: keyring credential helper libsecret: libsecret credential helper [installed] less: the default pager for git installing compiler-rt... installing llhttp... installing libgit2... installing libedit... installing llvm-libs... installing lld... installing rust... Optional dependencies for rust gdb: rust-gdb script [installed] lldb: rust-lldb script installing maturin... installing python-installer... :: Running post-transaction hooks... (1/3) Creating system user accounts... Creating group 'git' with GID 969. Creating user 'git' (git daemon user) with UID 969 and GID 969. (2/3) Reloading system manager configuration... Skipped: Current root is not booted. (3/3) Arming ConditionNeedsUpdate... ==> Retrieving sources... ==> WARNING: Skipping all source file integrity checks. ==> Extracting sources... -> Creating working copy of ty git repo... Cloning into 'ty'... done. Switched to a new branch 'makepkg' -> Creating working copy of ruff git repo... Cloning into 'ruff'... done. ==> Starting prepare()... Submodule 'ruff' (https://github.com/astral-sh/ruff) registered for path 'ruff' Cloning into '/startdir/src/ty/ruff'... done. Submodule path 'ruff': checked out '094025e32eee9a29c5f32d07569e0ebe5e639de1' Updating crates.io index Downloading crates ... Downloaded wasm-bindgen-test-macro v0.3.55 Downloaded unicode-ident v1.0.24 Downloaded wasm-bindgen-test v0.3.55 Downloaded libtest-mimic v0.8.1 Downloaded quote v1.0.45 Downloaded equivalent v1.0.2 Downloaded same-file v1.0.6 Downloaded ref-cast v1.0.25 Downloaded console v0.16.1 Downloaded dyn-clone v1.0.20 Downloaded ref-cast-impl v1.0.25 Downloaded generic-array v0.14.7 Downloaded cpufeatures v0.3.0 Downloaded wasm-bindgen-shared v0.2.105 Downloaded collection_literals v1.0.2 Downloaded quote-use-macros v0.8.4 Downloaded pest v2.8.2 Downloaded heck v0.5.0 Downloaded quote-use v0.8.4 Downloaded manyhow-macros v0.11.4 Downloaded attribute-derive-macro v0.10.3 Downloaded lazy_static v1.5.0 Downloaded castaway v0.2.4 Downloaded wasm-bindgen-macro v0.2.105 Downloaded cfg-if v1.0.4 Downloaded idna_adapter v1.2.1 Downloaded dirs-sys v0.5.0 Downloaded drop_bomb v0.1.5 Downloaded darling_macro v0.23.0 Downloaded bit-set v0.8.0 Downloaded pathdiff v0.2.3 Downloaded strum v0.28.0 Downloaded rustc-hash v2.1.2 Downloaded supports-hyperlinks v3.2.0 Downloaded get-size-derive2 v0.9.0 Downloaded itoa v1.0.15 Downloaded serde_test v1.0.177 Downloaded which v8.0.2 Downloaded funty v2.0.0 Downloaded walkdir v2.5.0 Downloaded etcetera v0.11.0 Downloaded path-slash v0.2.1 Downloaded strip-ansi-escapes v0.2.1 Downloaded ident_case v1.0.1 Downloaded autocfg v1.5.0 Downloaded matchers v0.2.0 Downloaded nu-ansi-term v0.50.1 Downloaded thread_local v1.1.9 Downloaded proc-macro-utils v0.10.0 Downloaded attribute-derive v0.10.3 Downloaded serde_derive_internals v0.29.1 Downloaded schemars_derive v1.2.1 Downloaded dunce v1.0.5 Downloaded pin-project-lite v0.2.16 Downloaded foldhash v0.2.0 Downloaded jobserver v0.1.34 Downloaded typed-arena v2.0.2 Downloaded stable_deref_trait v1.2.0 Downloaded tap v1.0.1 Downloaded test-case v3.3.1 Downloaded wasm-bindgen-futures v0.4.55 Downloaded zerofrom-derive v0.1.6 Downloaded shlex v1.3.0 Downloaded pkg-config v0.3.32 Downloaded zstd-safe v7.2.4 Downloaded zstd v0.13.3 Downloaded rand_core v0.10.0 Downloaded rustversion v1.0.22 Downloaded option-ext v0.2.0 Downloaded inotify-sys v0.1.5 Downloaded yoke-derive v0.8.2 Downloaded radium v0.7.0 Downloaded memoffset v0.9.1 Downloaded countme v3.0.1 Downloaded get-size2 v0.9.0 Downloaded quickcheck_macros v1.2.0 Downloaded siphasher v1.0.1 Downloaded crossbeam-queue v0.3.12 Downloaded crc32fast v1.5.0 Downloaded either v1.15.0 Downloaded static_assertions v1.1.0 Downloaded tracing-log v0.2.0 Downloaded manyhow v0.11.4 Downloaded smallvec v1.15.1 Downloaded tracing-attributes v0.1.31 Downloaded interpolator v0.5.0 Downloaded potential_utf v0.1.3 Downloaded zmij v1.0.10 Downloaded find-msvc-tools v0.1.2 Downloaded unscanny v0.1.0 Downloaded chacha20 v0.10.0 Downloaded libz-rs-sys v0.5.5 Downloaded iana-time-zone v0.1.64 Downloaded ryu v1.0.20 Downloaded wasm-bindgen v0.2.105 Downloaded thin-vec v0.2.18 Downloaded once_cell v1.21.4 Downloaded dirs v6.0.0 Downloaded snapbox-macros v1.0.0 Downloaded colorchoice v1.0.4 Downloaded form_urlencoded v1.2.2 Downloaded lock_api v0.4.13 Downloaded js-sys v0.3.82 Downloaded serde_derive v1.0.228 Downloaded crossbeam v0.8.4 Downloaded num-traits v0.2.19 Downloaded wasm-bindgen-macro-support v0.2.105 Downloaded allocator-api2 v0.2.21 Downloaded proc-macro2 v1.0.106 Downloaded log v0.4.31 Downloaded derive-where v1.6.0 Downloaded phf v0.11.3 Downloaded anstyle-svg v0.1.11 Downloaded globset v0.4.18 Downloaded ctrlc v3.5.2 Downloaded seahash v4.1.0 Downloaded unit-prefix v0.5.1 Downloaded test-case-macros v3.3.1 Downloaded anstream v1.0.0 Downloaded tracing-core v0.1.36 Downloaded ordermap v1.2.0 Downloaded test-case-core v3.3.1 Downloaded notify-types v2.0.0 Downloaded zerofrom v0.1.6 Downloaded typeid v1.0.3 Downloaded sharded-slab v0.1.7 Downloaded toml_datetime v1.1.1+spec-1.1.0 Downloaded flate2 v1.1.2 Downloaded utf8_iter v1.0.4 Downloaded html-escape v0.2.13 Downloaded arrayvec v0.7.6 Downloaded ciborium-ll v0.2.2 Downloaded serde_core v1.0.228 Downloaded alloca v0.4.0 Downloaded ciborium-io v0.2.2 Downloaded percent-encoding v2.3.2 Downloaded cast v0.3.0 Downloaded escargot v0.5.15 Downloaded getrandom v0.4.2 Downloaded serde v1.0.228 Downloaded compact_str v0.9.1 Downloaded utf8-width v0.1.7 Downloaded schemars v1.2.1 Downloaded bumpalo v3.19.0 Downloaded thiserror v2.0.18 Downloaded pest_derive v2.8.2 Downloaded unty v0.0.4 Downloaded argfile v1.0.0 Downloaded jod-thread v1.0.0 Downloaded bincode_derive v2.0.1 Downloaded condtype v1.3.0 Downloaded divan-macros v0.1.17 Downloaded cc v1.2.38 Downloaded uuid v1.23.2 Downloaded page_size v0.6.0 Downloaded vt100 v0.16.2 Downloaded inotify v0.11.0 Downloaded codspeed-divan-compat v4.4.1 Downloaded memchr v2.8.1 Downloaded anes v0.1.6 Downloaded criterion-plot v0.8.2 Downloaded ciborium v0.2.2 Downloaded vte v0.15.0 Downloaded block-buffer v0.10.4 Downloaded ppv-lite86 v0.2.21 Downloaded oorandom v11.1.5 Downloaded tinytemplate v1.2.1 Downloaded version_check v0.9.5 Downloaded crypto-common v0.1.6 Downloaded synstructure v0.13.2 Downloaded foldhash v0.1.5 Downloaded lsp-server v0.7.9 Downloaded boxcar v0.2.14 Downloaded hashlink v0.11.0 Downloaded tracing-flame v0.2.0 Downloaded urlencoding v2.1.3 Downloaded paste v1.0.15 Downloaded rand v0.8.5 Downloaded toml v1.1.2+spec-1.1.0 Downloaded num_cpus v1.17.0 Downloaded phf_generator v0.11.3 Downloaded similar v2.7.0 Downloaded anstyle-query v1.1.4 Downloaded wait-timeout v0.2.1 Downloaded glob v0.3.3 Downloaded tinyvec_macros v0.1.1 Downloaded quickcheck v1.1.0 Downloaded rustc-stable-hash v0.1.2 Downloaded strum_macros v0.28.0 Downloaded approx v0.5.1 Downloaded predicates-core v1.0.10 Downloaded utf8parse v0.2.2 Downloaded virtue v0.0.18 Downloaded indexmap v2.14.0 Downloaded rand v0.10.1 Downloaded cpufeatures v0.2.17 Downloaded termtree v0.5.1 Downloaded scopeguard v1.2.0 Downloaded indicatif v0.18.4 Downloaded pyproject-toml v0.13.7 Downloaded toml_datetime v0.7.5+spec-1.1.0 Downloaded inventory v0.3.24 Downloaded parking_lot_core v0.9.11 Downloaded newtype-uuid v1.3.2 Downloaded is-macro v0.3.7 Downloaded natord v1.0.9 Downloaded clap_complete v4.5.58 Downloaded writeable v0.6.2 Downloaded tracing-indicatif v0.3.14 Downloaded codspeed-criterion-compat v4.4.1 Downloaded fnv v1.0.7 Downloaded cachedir v0.3.1 Downloaded cfg_aliases v0.2.1 Downloaded dashmap v6.2.1 Downloaded zip v5.1.1 Downloaded half v2.6.0 Downloaded salsa-macro-rules v0.27.0 Downloaded csv-core v0.1.12 Downloaded pest_generator v2.8.2 Downloaded crossbeam-epoch v0.9.18 Downloaded assert_fs v1.1.4 Downloaded tempfile v3.27.0 Downloaded globwalk v0.9.1 Downloaded errno v0.3.14 Downloaded terminfo v0.9.0 Downloaded displaydoc v0.2.5 Downloaded shellexpand v3.1.2 Downloaded filetime v0.2.29 Downloaded is_terminal_polyfill v1.70.1 Downloaded rand_chacha v0.3.1 Downloaded zerovec-derive v0.11.3 Downloaded clap_complete_command v0.6.1 Downloaded indoc v2.0.7 Downloaded regex-lite v0.1.7 Downloaded wild v2.2.1 Downloaded codspeed-divan-compat-walltime v4.4.1 Downloaded parking_lot v0.12.4 Downloaded ucd-trie v0.1.7 Downloaded hashbrown v0.17.1 Downloaded serde_with_macros v3.20.0 Downloaded datatest-stable v0.3.3 Downloaded quick-junit v0.6.0 Downloaded bit-vec v0.8.0 Downloaded rand_core v0.6.4 Downloaded wyz v0.5.1 Downloaded regex v1.12.3 Downloaded syn v2.0.117 Downloaded gen-lsp-types v0.8.0 Downloaded colored v3.1.1 Downloaded darling v0.23.0 Downloaded version-ranges v0.1.1 Downloaded tinystr v0.8.3 Downloaded serde_spanned v1.1.1 Downloaded anstyle-parse v1.0.0 Downloaded notify v8.2.0 Downloaded tikv-jemallocator v0.6.1 Downloaded terminal_size v0.4.3 Downloaded threadpool v1.8.1 Downloaded normalize-line-endings v0.3.0 Downloaded libcst_derive v1.8.6 Downloaded os_pipe v1.2.2 Downloaded clap_lex v1.0.0 Downloaded predicates-tree v1.0.13 Downloaded pep508_rs v0.9.2 Downloaded is-terminal v0.4.16 Downloaded codspeed-divan-compat-macros v4.4.1 Downloaded peg-macros v0.8.5 Downloaded serde_json v1.0.150 Downloaded toml v0.9.12+spec-1.1.0 Downloaded salsa-macros v0.27.0 Downloaded digest v0.10.7 Downloaded path-absolutize v3.1.1 Downloaded path-dedot v3.1.1 Downloaded phf_shared v0.11.3 Downloaded phf_codegen v0.11.3 Downloaded imperative v1.0.7 Downloaded insta-cmd v0.6.0 Downloaded itertools v0.14.0 Downloaded anstream v0.6.21 Downloaded criterion-plot v0.5.0 Downloaded termcolor v1.4.1 Downloaded proc-macro-crate v3.4.0 Downloaded anstyle v1.0.14 Downloaded anstyle-lossy v1.1.4 Downloaded aho-corasick v1.1.4 Downloaded console_log v1.0.0 Downloaded sha2 v0.10.9 Downloaded intrusive-collections v0.10.1 Downloaded unicode_names2_generator v1.3.0 Downloaded os_str_bytes v7.1.1 Downloaded fs-err v3.3.0 Downloaded crossbeam-deque v0.8.6 Downloaded matchit v0.9.2 Downloaded pest_meta v2.8.2 Downloaded unicode-id v0.3.6 Downloaded predicates v3.1.4 Downloaded bincode v2.0.1 Downloaded criterion v0.8.2 Downloaded annotate-snippets v0.11.5 Downloaded thiserror-impl v1.0.69 Downloaded clap_complete_nushell v4.5.8 Downloaded litemap v0.8.0 Downloaded yoke v0.8.2 Downloaded serde-wasm-bindgen v0.6.5 Downloaded anyhow v1.0.102 Downloaded toml_writer v1.1.1+spec-1.1.0 Downloaded zlib-rs v0.5.5 Downloaded getrandom v0.2.16 Downloaded itertools v0.13.0 Downloaded crossbeam-utils v0.8.21 Downloaded toml_edit v0.23.6 Downloaded minimal-lexical v0.2.1 Downloaded strsim v0.11.1 Downloaded fastrand v2.3.0 Downloaded difflib v0.4.0 Downloaded chrono v0.4.44 Downloaded thiserror v1.0.69 Downloaded tryfn v1.0.0 Downloaded tracing-subscriber v0.3.23 Downloaded phf v0.13.1 Downloaded hashbrown v0.15.5 Downloaded itertools v0.10.5 Downloaded peg v0.8.5 Downloaded clap_derive v4.6.1 Downloaded getopts v0.2.24 Downloaded ron v0.12.0 Downloaded nom v7.1.3 Downloaded pep440_rs v0.7.3 Downloaded libtest-mimic v0.7.3 Downloaded thiserror-impl v2.0.18 Downloaded clap_builder v4.6.0 Downloaded imara-diff v0.2.0 Downloaded diff v0.1.13 Downloaded icu_provider v2.2.0 Downloaded unicode-normalization v0.1.24 Downloaded statrs v0.18.0 Downloaded winnow v0.7.13 Downloaded phf_shared v0.13.1 Downloaded portable-atomic v1.13.1 Downloaded yansi v1.0.1 Downloaded darling_core v0.23.0 Downloaded unicode-width v0.2.2 Downloaded clearscreen v4.0.6 Downloaded toml_parser v1.1.2+spec-1.1.0 Downloaded hashbrown v0.16.1 Downloaded regex-syntax v0.8.10 Downloaded colored v2.2.0 Downloaded codspeed v4.4.1 Downloaded nix v0.31.2 Downloaded icu_normalizer v2.2.0 Downloaded vte v0.14.1 Downloaded arc-swap v1.9.1 Downloaded unicode_names2 v1.3.0 Downloaded fern v0.7.1 Downloaded markdown v1.0.0 Downloaded bstr v1.12.1 Downloaded peg-runtime v0.8.5 Downloaded icu_normalizer_data v2.2.0 Downloaded pretty_assertions v1.4.1 Downloaded rayon-core v1.13.0 Downloaded anstyle-parse v0.2.7 Downloaded snapbox v1.0.0 Downloaded icu_properties v2.2.0 Downloaded escape8259 v0.5.3 Downloaded camino v1.2.2 Downloaded insta v1.47.2 Downloaded tracing v0.1.44 Downloaded fancy-regex v0.14.0 Downloaded zerotrie v0.2.4 Downloaded typenum v1.18.0 Downloaded regex-automata v0.4.14 Downloaded clap v4.6.1 Downloaded icu_collections v2.2.0 Downloaded icu_locale_core v2.2.0 Downloaded zstd-sys v2.0.16+zstd.1.5.7 Downloaded url v2.5.8 Downloaded libc v0.2.186 Downloaded bitflags v2.12.1 Downloaded crossbeam-channel v0.5.15 Downloaded tikv-jemalloc-sys v0.6.1+5.3.0-1-ge13ca993e8ccb9ba9847cc330696e02839f328f7 Downloaded jiff-static v0.2.28 Downloaded ignore v0.4.25 Downloaded tinyvec v1.10.0 Downloaded mio v1.0.4 Downloaded similar v3.1.1 Downloaded zerovec v0.11.6 Downloaded libcst v1.8.6 Downloaded linux-raw-sys v0.12.1 Downloaded idna v1.1.0 Downloaded codspeed-criterion-compat-walltime v4.4.1 Downloaded hashbrown v0.14.5 Downloaded rayon v1.12.0 Downloaded icu_properties_data v2.2.0 Downloaded serde_with v3.20.0 Downloaded winnow v1.0.0 Downloaded quick-xml v0.38.4 Downloaded bitvec v1.0.1 Downloaded salsa v0.27.0 Downloaded zerocopy v0.8.27 Downloaded rustix v1.1.4 Downloaded console_error_panic_hook v0.1.7 Downloaded web-sys v0.3.82 Downloaded jiff v0.2.28 Downloaded csv v1.4.0 Downloaded rust-stemmers v1.2.0 ==> Starting build()... 📦 Including license file `LICENSE` 🍹 Building a mixed python/rust project 🔗 Found bin bindings 📡 Using build options bindings from pyproject.toml Compiling proc-macro2 v1.0.106 Compiling unicode-ident v1.0.24 Compiling quote v1.0.45 Compiling libc v0.2.186 Compiling cfg-if v1.0.4 Compiling serde_core v1.0.228 Compiling memchr v2.8.1 Compiling autocfg v1.5.0 Compiling smallvec v1.15.1 Compiling serde v1.0.228 Compiling foldhash v0.2.0 Compiling find-msvc-tools v0.1.2 Compiling shlex v1.3.0 Compiling rustversion v1.0.22 Compiling itoa v1.0.15 Compiling allocator-api2 v0.2.21 Compiling crossbeam-utils v0.8.21 Compiling equivalent v1.0.2 Compiling bitflags v2.12.1 Compiling zerocopy v0.8.27 Compiling heck v0.5.0 Compiling interpolator v0.5.0 Compiling collection_literals v1.0.2 Compiling once_cell v1.21.4 Compiling static_assertions v1.1.0 Compiling pkg-config v0.3.32 Compiling ryu v1.0.20 Compiling regex-syntax v0.8.10 Compiling siphasher v1.0.1 Compiling parking_lot_core v0.9.11 Compiling stable_deref_trait v1.2.0 Compiling log v0.4.31 Compiling scopeguard v1.2.0 Compiling zstd-safe v7.2.4 Compiling hashbrown v0.17.1 Compiling pin-project-lite v0.2.16 Compiling phf_shared v0.11.3 Compiling portable-atomic v1.13.1 Compiling tracing-core v0.1.36 Compiling aho-corasick v1.1.4 Compiling crc32fast v1.5.0 Compiling either v1.15.0 Compiling thiserror v2.0.18 Compiling typeid v1.0.3 Compiling hashbrown v0.16.1 Compiling lock_api v0.4.13 Compiling memoffset v0.9.1 Compiling unicode-width v0.2.2 Compiling itertools v0.14.0 Compiling jobserver v0.1.34 Compiling getrandom v0.2.16 Compiling crossbeam-queue v0.3.12 Compiling getopts v0.2.24 Compiling castaway v0.2.4 Compiling regex-automata v0.4.14 Compiling syn v2.0.117 Compiling proc-macro-utils v0.10.0 Compiling ppv-lite86 v0.2.21 Compiling hashlink v0.11.0 Compiling rand_core v0.6.4 Compiling getrandom v0.4.2 Compiling cc v1.2.38 Compiling intrusive-collections v0.10.1 Compiling zmij v1.0.10 Compiling rustc-hash v2.1.2 Compiling boxcar v0.2.14 Compiling anstyle v1.0.14 Compiling rand_core v0.10.0 Compiling inventory v0.3.24 Compiling salsa-macro-rules v0.27.0 Compiling phf v0.11.3 Compiling filetime v0.2.29 Compiling num-traits v0.2.19 Compiling seahash v4.1.0 Compiling rand_chacha v0.3.1 Compiling cpufeatures v0.3.0 Compiling parking_lot v0.12.4 Compiling ident_case v1.0.1 Compiling strsim v0.11.1 Compiling indexmap v2.14.0 Compiling manyhow-macros v0.11.4 Compiling rand v0.8.5 Compiling glob v0.3.3 Compiling serde_json v1.0.150 Compiling chacha20 v0.10.0 Compiling crossbeam-epoch v0.9.18 Compiling writeable v0.6.2 Compiling tinyvec_macros v0.1.1 Compiling ruff_text_size v0.0.0 (/startdir/src/ty/ruff/crates/ruff_text_size) Compiling litemap v0.8.0 Compiling tinyvec v1.10.0 Compiling rand v0.10.1 Compiling anyhow v1.0.102 Compiling phf_generator v0.11.3 Compiling crossbeam-deque v0.8.6 Compiling ruff_source_file v0.0.0 (/startdir/src/ty/ruff/crates/ruff_source_file) Compiling iana-time-zone v0.1.64 Compiling utf8_iter v1.0.4 Compiling icu_properties_data v2.2.0 Compiling unicode-normalization v0.1.24 Compiling ordermap v1.2.0 Compiling phf_codegen v0.11.3 Compiling chrono v0.4.44 Compiling same-file v1.0.6 Compiling zlib-rs v0.5.5 Compiling uuid v1.23.2 Compiling walkdir v2.5.0 Compiling vte v0.14.1 Compiling camino v1.2.2 Compiling unicode_names2_generator v1.3.0 Compiling ruff_python_trivia v0.0.0 (/startdir/src/ty/ruff/crates/ruff_python_trivia) Compiling which v8.0.2 Compiling zstd-sys v2.0.16+zstd.1.5.7 Compiling quick-xml v0.38.4 Compiling hashbrown v0.14.5 Compiling strip-ansi-escapes v0.2.1 Compiling newtype-uuid v1.3.2 Compiling bstr v1.12.1 Compiling regex v1.12.3 Compiling synstructure v0.13.2 Compiling manyhow v0.11.4 Compiling darling_core v0.23.0 Compiling ruff_annotate_snippets v0.1.0 (/startdir/src/ty/ruff/crates/ruff_annotate_snippets) Compiling arc-swap v1.9.1 Compiling etcetera v0.11.0 Compiling unicode_names2 v1.3.0 Compiling similar v3.1.1 Compiling dunce v1.0.5 Compiling pathdiff v0.2.3 Compiling matchit v0.9.2 Compiling supports-hyperlinks v3.2.0 Compiling globset v0.4.18 Compiling dashmap v6.2.1 Compiling path-slash v0.2.1 Compiling ref-cast v1.0.25 Compiling icu_normalizer_data v2.2.0 Compiling radium v0.7.0 Compiling rustix v1.1.4 Compiling ruff_cache v0.0.0 (/startdir/src/ty/ruff/crates/ruff_cache) Compiling ignore v0.4.25 Compiling serde_derive_internals v0.29.1 Compiling utf8parse v0.2.2 Compiling rayon-core v1.13.0 Compiling tap v1.0.1 Compiling linux-raw-sys v0.12.1 Compiling anstyle-parse v1.0.0 Compiling wyz v0.5.1 Compiling ruff_python_stdlib v0.0.0 (/startdir/src/ty/ruff/crates/ruff_python_stdlib) Compiling funty v2.0.0 Compiling colorchoice v1.0.4 Compiling is_terminal_polyfill v1.70.1 Compiling colored v3.1.1 Compiling option-ext v0.2.0 Compiling dyn-clone v1.0.20 Compiling anstyle-query v1.1.4 Compiling dirs-sys v0.5.0 Compiling bitvec v1.0.1 Compiling anstream v1.0.0 Compiling libz-rs-sys v0.5.5 Compiling flate2 v1.1.2 Compiling inotify-sys v0.1.5 Compiling crossbeam-channel v0.5.15 Compiling terminal_size v0.4.3 Compiling cfg_aliases v0.2.1 Compiling clap_lex v1.0.0 Compiling winnow v1.0.0 Compiling inotify v0.11.0 Compiling dirs v6.0.0 Compiling serde_spanned v1.1.1 Compiling toml_datetime v1.1.1+spec-1.1.0 Compiling rayon v1.12.0 Compiling mio v1.0.4 Compiling serde_derive v1.0.228 Compiling quote-use-macros v0.8.4 Compiling derive-where v1.6.0 Compiling zerofrom-derive v0.1.6 Compiling yoke-derive v0.8.2 Compiling tracing-attributes v0.1.31 Compiling zerovec-derive v0.11.3 Compiling thiserror-impl v2.0.18 Compiling displaydoc v0.2.5 Compiling salsa-macros v0.27.0 Compiling is-macro v0.3.7 Compiling darling_macro v0.23.0 Compiling strum_macros v0.28.0 Compiling ref-cast-impl v1.0.25 Compiling schemars_derive v1.2.1 Compiling toml_parser v1.1.2+spec-1.1.0 Compiling quote-use v0.8.4 Compiling nix v0.31.2 Compiling attribute-derive-macro v0.10.3 Compiling darling v0.23.0 Compiling clap_derive v4.6.1 Compiling serde_with_macros v3.20.0 Compiling ruff_macros v0.0.0 (/startdir/src/ty/ruff/crates/ruff_macros) Compiling clap_builder v4.6.0 Compiling version-ranges v0.1.1 Compiling lazy_static v1.5.0 Compiling drop_bomb v0.1.5 Compiling unscanny v0.1.0 Compiling percent-encoding v2.3.2 Compiling notify-types v2.0.0 Compiling toml_writer v1.1.1+spec-1.1.0 Compiling sharded-slab v0.1.7 Compiling quick-junit v0.6.0 Compiling shellexpand v3.1.2 Compiling zerofrom v0.1.6 Compiling notify v8.2.0 Compiling yoke v0.8.2 Compiling form_urlencoded v1.2.2 Compiling toml v1.1.2+spec-1.1.0 Compiling crossbeam v0.8.4 Compiling tracing v0.1.44 Compiling attribute-derive v0.10.3 Compiling matchers v0.2.0 Compiling tikv-jemalloc-sys v0.6.1+5.3.0-1-ge13ca993e8ccb9ba9847cc330696e02839f328f7 Compiling zerovec v0.11.6 Compiling zerotrie v0.2.4 Compiling terminfo v0.9.0 Compiling fs-err v3.3.0 Compiling thread_local v1.1.9 Compiling ruff_options_metadata v0.0.0 (/startdir/src/ty/ruff/crates/ruff_options_metadata) Compiling serde_with v3.20.0 Compiling nu-ansi-term v0.50.1 Compiling minimal-lexical v0.2.1 Compiling get-size-derive2 v0.9.0 Compiling fnv v1.0.7 Compiling nom v7.1.3 Compiling tinystr v0.8.3 Compiling potential_utf v0.1.3 Compiling strum v0.28.0 Compiling tracing-subscriber v0.3.23 Compiling icu_collections v2.2.0 Compiling console v0.16.1 Compiling os_str_bytes v7.1.1 Compiling icu_locale_core v2.2.0 Compiling ty v0.0.0 (/startdir/src/ty/ruff/crates/ty) Compiling ty_static v0.0.1 (/startdir/src/ty/ruff/crates/ty_static) Compiling jod-thread v1.0.0 Compiling unit-prefix v0.5.1 Compiling argfile v1.0.0 Compiling wild v2.2.1 Compiling jiff v0.2.28 Compiling icu_provider v2.2.0 Compiling clap v4.6.1 Compiling clap_complete v4.5.58 Compiling thin-vec v0.2.18 Compiling compact_str v0.9.1 Compiling schemars v1.2.1 Compiling icu_properties v2.2.0 Compiling icu_normalizer v2.2.0 Compiling lsp-server v0.7.9 Compiling pep440_rs v0.7.3 Compiling tracing-flame v0.2.0 Compiling clap_complete_nushell v4.5.8 Compiling get-size2 v0.9.0 Compiling salsa v0.27.0 Compiling clap_complete_command v0.6.1 Compiling ctrlc v3.5.2 Compiling idna_adapter v1.2.1 Compiling indicatif v0.18.4 Compiling ruff_memory_usage v0.0.0 (/startdir/src/ty/ruff/crates/ruff_memory_usage) Compiling ruff_diagnostics v0.0.0 (/startdir/src/ty/ruff/crates/ruff_diagnostics) Compiling idna v1.1.0 Compiling ruff_notebook v0.0.0 (/startdir/src/ty/ruff/crates/ruff_notebook) Compiling ruff_index v0.0.0 (/startdir/src/ty/ruff/crates/ruff_index) Compiling url v2.5.8 Compiling ruff_python_ast v0.0.0 (/startdir/src/ty/ruff/crates/ruff_python_ast) Compiling clearscreen v4.0.6 Compiling gen-lsp-types v0.8.0 Compiling ruff_python_parser v0.0.0 (/startdir/src/ty/ruff/crates/ruff_python_parser) Compiling ruff_python_literal v0.0.0 (/startdir/src/ty/ruff/crates/ruff_python_literal) Compiling ruff_python_codegen v0.0.0 (/startdir/src/ty/ruff/crates/ruff_python_codegen) Compiling ruff_python_importer v0.0.0 (/startdir/src/ty/ruff/crates/ruff_python_importer) Compiling zstd v0.13.3 Compiling zip v5.1.1 Compiling ruff_db v0.0.0 (/startdir/src/ty/ruff/crates/ruff_db) Compiling ty_combine v0.0.0 (/startdir/src/ty/ruff/crates/ty_combine) Compiling ty_module_resolver v0.0.0 (/startdir/src/ty/ruff/crates/ty_module_resolver) Compiling ty_site_packages v0.0.0 (/startdir/src/ty/ruff/crates/ty_site_packages) Compiling ty_vendored v0.0.0 (/startdir/src/ty/ruff/crates/ty_vendored) Compiling tikv-jemallocator v0.6.1 Compiling ty_python_core v0.0.0 (/startdir/src/ty/ruff/crates/ty_python_core) Compiling ty_python_semantic v0.0.0 (/startdir/src/ty/ruff/crates/ty_python_semantic) Compiling ty_project v0.0.0 (/startdir/src/ty/ruff/crates/ty_project) Compiling ty_ide v0.0.0 (/startdir/src/ty/ruff/crates/ty_ide) Compiling ty_server v0.0.0 (/startdir/src/ty/ruff/crates/ty_server) Finished `release` profile [optimized] target(s) in 9m 16s 📦 Built wheel to /startdir/src/ty/ruff/target/wheels/ty-0.0.49-py3-none-manylinux_2_39_x86_64.whl ==> Starting check()... Compiling unicode-ident v1.0.24 Compiling proc-macro2 v1.0.106 Compiling quote v1.0.45 Compiling cfg-if v1.0.4 Compiling memchr v2.8.1 Compiling libc v0.2.186 Compiling serde_core v1.0.228 Compiling autocfg v1.5.0 Compiling smallvec v1.15.1 Compiling serde v1.0.228 Compiling equivalent v1.0.2 Compiling regex-syntax v0.8.10 Compiling foldhash v0.2.0 Compiling bitflags v2.12.1 Compiling itoa v1.0.15 Compiling allocator-api2 v0.2.21 Compiling crossbeam-utils v0.8.21 Compiling rustversion v1.0.22 Compiling heck v0.5.0 Compiling zerocopy v0.8.27 Compiling once_cell v1.21.4 Compiling siphasher v1.0.1 Compiling collection_literals v1.0.2 Compiling interpolator v0.5.0 Compiling ryu v1.0.20 Compiling shlex v1.3.0 Compiling find-msvc-tools v0.1.2 Compiling log v0.4.31 Compiling static_assertions v1.1.0 Compiling unicode-width v0.2.2 Compiling either v1.15.0 Compiling phf_shared v0.11.3 Compiling stable_deref_trait v1.2.0 Compiling strsim v0.11.1 Compiling hashbrown v0.17.1 Compiling parking_lot_core v0.9.11 Compiling tracing-core v0.1.36 Compiling thiserror v2.0.18 Compiling aho-corasick v1.1.4 Compiling portable-atomic v1.13.1 Compiling pin-project-lite v0.2.16 Compiling getrandom v0.4.2 Compiling itertools v0.14.0 Compiling rand_core v0.10.0 Compiling pkg-config v0.3.32 Compiling scopeguard v1.2.0 Compiling typeid v1.0.3 Compiling hashbrown v0.16.1 Compiling zmij v1.0.10 Compiling getopts v0.2.24 Compiling crossbeam-queue v0.3.12 Compiling rustc-hash v2.1.2 Compiling inventory v0.3.24 Compiling anstyle v1.0.14 Compiling boxcar v0.2.14 Compiling zstd-safe v7.2.4 Compiling serde_json v1.0.150 Compiling salsa-macro-rules v0.27.0 Compiling syn v2.0.117 Compiling proc-macro-utils v0.10.0 Compiling hashlink v0.11.0 Compiling crc32fast v1.5.0 Compiling lock_api v0.4.13 Compiling memoffset v0.9.1 Compiling num-traits v0.2.19 Compiling phf v0.11.3 Compiling seahash v4.1.0 Compiling glob v0.3.3 Compiling ident_case v1.0.1 Compiling zlib-rs v0.5.5 Compiling cpufeatures v0.3.0 Compiling intrusive-collections v0.10.1 Compiling chacha20 v0.10.0 Compiling crossbeam-epoch v0.9.18 Compiling writeable v0.6.2 Compiling getrandom v0.2.16 Compiling regex-automata v0.4.14 Compiling jobserver v0.1.34 Compiling ruff_text_size v0.0.0 (/startdir/src/ty/ruff/crates/ruff_text_size) Compiling rand_core v0.6.4 Compiling tinyvec_macros v0.1.1 Compiling litemap v0.8.0 Compiling same-file v1.0.6 Compiling tinyvec v1.10.0 Compiling crossbeam-deque v0.8.6 Compiling ruff_source_file v0.0.0 (/startdir/src/ty/ruff/crates/ruff_source_file) Compiling cc v1.2.38 Compiling filetime v0.2.29 Compiling walkdir v2.5.0 Compiling anyhow v1.0.102 Compiling parking_lot v0.12.4 Compiling rand v0.10.1 Compiling iana-time-zone v0.1.64 Compiling castaway v0.2.4 Compiling icu_properties_data v2.2.0 Compiling utf8_iter v1.0.4 Compiling unicode-normalization v0.1.24 Compiling ppv-lite86 v0.2.21 Compiling ruff_python_trivia v0.0.0 (/startdir/src/ty/ruff/crates/ruff_python_trivia) Compiling lazy_static v1.5.0 Compiling indexmap v2.14.0 Compiling chrono v0.4.44 Compiling rand_chacha v0.3.1 Compiling sharded-slab v0.1.7 Compiling vte v0.14.1 Compiling thread_local v1.1.9 Compiling rand v0.8.5 Compiling camino v1.2.2 Compiling uuid v1.23.2 Compiling nu-ansi-term v0.50.1 Compiling path-slash v0.2.1 Compiling manyhow-macros v0.11.4 Compiling strip-ansi-escapes v0.2.1 Compiling newtype-uuid v1.3.2 Compiling which v8.0.2 Compiling quick-xml v0.38.4 Compiling ordermap v1.2.0 Compiling rustix v1.1.4 Compiling hashbrown v0.14.5 Compiling arc-swap v1.9.1 Compiling ruff_annotate_snippets v0.1.0 (/startdir/src/ty/ruff/crates/ruff_annotate_snippets) Compiling phf_generator v0.11.3 Compiling etcetera v0.11.0 Compiling phf_codegen v0.11.3 Compiling libz-rs-sys v0.5.5 Compiling matchit v0.9.2 Compiling pathdiff v0.2.3 Compiling similar v3.1.1 Compiling supports-hyperlinks v3.2.0 Compiling unicode_names2_generator v1.3.0 Compiling flate2 v1.1.2 Compiling dashmap v6.2.1 Compiling linux-raw-sys v0.12.1 Compiling dunce v1.0.5 Compiling ref-cast v1.0.25 Compiling icu_normalizer_data v2.2.0 Compiling radium v0.7.0 Compiling utf8parse v0.2.2 Compiling tap v1.0.1 Compiling rayon-core v1.13.0 Compiling wyz v0.5.1 Compiling anstyle-parse v1.0.0 Compiling ruff_python_stdlib v0.0.0 (/startdir/src/ty/ruff/crates/ruff_python_stdlib) Compiling colorchoice v1.0.4 Compiling synstructure v0.13.2 Compiling manyhow v0.11.4 Compiling darling_core v0.23.0 Compiling serde_derive_internals v0.29.1 Compiling regex v1.12.3 Compiling anstyle-query v1.1.4 Compiling funty v2.0.0 Compiling colored v3.1.1 Compiling bstr v1.12.1 Compiling matchers v0.2.0 Compiling option-ext v0.2.0 Compiling dyn-clone v1.0.20 Compiling is_terminal_polyfill v1.70.1 Compiling dirs-sys v0.5.0 Compiling anstream v1.0.0 Compiling bitvec v1.0.1 Compiling globset v0.4.18 Compiling ruff_cache v0.0.0 (/startdir/src/ty/ruff/crates/ruff_cache) Compiling ignore v0.4.25 Compiling inotify-sys v0.1.5 Compiling crossbeam-channel v0.5.15 Compiling terminal_size v0.4.3 Compiling winnow v1.0.0 Compiling cfg_aliases v0.2.1 Compiling clap_lex v1.0.0 Compiling nix v0.31.2 Compiling toml_parser v1.1.2+spec-1.1.0 Compiling clap_builder v4.6.0 Compiling rayon v1.12.0 Compiling inotify v0.11.0 Compiling dirs v6.0.0 Compiling serde_spanned v1.1.1 Compiling toml_datetime v1.1.1+spec-1.1.0 Compiling mio v1.0.4 Compiling unicode_names2 v1.3.0 Compiling version-ranges v0.1.1 Compiling notify-types v2.0.0 Compiling drop_bomb v0.1.5 Compiling toml_writer v1.1.1+spec-1.1.0 Compiling percent-encoding v2.3.2 Compiling unscanny v0.1.0 Compiling form_urlencoded v1.2.2 Compiling toml v1.1.2+spec-1.1.0 Compiling notify v8.2.0 Compiling shellexpand v3.1.2 Compiling crossbeam v0.8.4 Compiling terminfo v0.9.0 Compiling console v0.16.1 Compiling fs-err v3.3.0 Compiling minimal-lexical v0.2.1 Compiling ruff_options_metadata v0.0.0 (/startdir/src/ty/ruff/crates/ruff_options_metadata) Compiling nom v7.1.3 Compiling fnv v1.0.7 Compiling os_str_bytes v7.1.1 Compiling jod-thread v1.0.0 Compiling unit-prefix v0.5.1 Compiling ty v0.0.0 (/startdir/src/ty/ruff/crates/ty) Compiling fastrand v2.3.0 Compiling indicatif v0.18.4 Compiling argfile v1.0.0 Compiling tempfile v3.27.0 Compiling wild v2.2.1 Compiling similar v2.7.0 Compiling jiff v0.2.28 Compiling ctrlc v3.5.2 Compiling zstd-sys v2.0.16+zstd.1.5.7 Compiling tikv-jemalloc-sys v0.6.1+5.3.0-1-ge13ca993e8ccb9ba9847cc330696e02839f328f7 Compiling serde_derive v1.0.228 Compiling quote-use-macros v0.8.4 Compiling derive-where v1.6.0 Compiling zerofrom-derive v0.1.6 Compiling yoke-derive v0.8.2 Compiling tracing-attributes v0.1.31 Compiling zerovec-derive v0.11.3 Compiling thiserror-impl v2.0.18 Compiling displaydoc v0.2.5 Compiling is-macro v0.3.7 Compiling salsa-macros v0.27.0 Compiling darling_macro v0.23.0 Compiling ruff_macros v0.0.0 (/startdir/src/ty/ruff/crates/ruff_macros) Compiling strum_macros v0.28.0 Compiling ref-cast-impl v1.0.25 Compiling schemars_derive v1.2.1 Compiling clap_derive v4.6.1 Compiling tikv-jemallocator v0.6.1 Compiling quote-use v0.8.4 Compiling attribute-derive-macro v0.10.3 Compiling darling v0.23.0 Compiling serde_with_macros v3.20.0 Compiling zstd v0.13.3 Compiling zip v5.1.1 Compiling ty_vendored v0.0.0 (/startdir/src/ty/ruff/crates/ty_vendored) Compiling attribute-derive v0.10.3 Compiling quick-junit v0.6.0 Compiling clearscreen v4.0.6 Compiling clap v4.6.1 Compiling clap_complete v4.5.58 Compiling clap_complete_nushell v4.5.8 Compiling clap_complete_command v0.6.1 Compiling serde_with v3.20.0 Compiling zerofrom v0.1.6 Compiling yoke v0.8.2 Compiling zerovec v0.11.6 Compiling zerotrie v0.2.4 Compiling get-size-derive2 v0.9.0 Compiling tracing v0.1.44 Compiling tracing-subscriber v0.3.23 Compiling tinystr v0.8.3 Compiling potential_utf v0.1.3 Compiling icu_collections v2.2.0 Compiling icu_locale_core v2.2.0 Compiling icu_provider v2.2.0 Compiling tracing-flame v0.2.0 Compiling icu_properties v2.2.0 Compiling icu_normalizer v2.2.0 Compiling strum v0.28.0 Compiling idna_adapter v1.2.1 Compiling idna v1.1.0 Compiling compact_str v0.9.1 Compiling thin-vec v0.2.18 Compiling schemars v1.2.1 Compiling url v2.5.8 Compiling lsp-server v0.7.9 Compiling insta v1.47.2 Compiling pep440_rs v0.7.3 Compiling ty_static v0.0.1 (/startdir/src/ty/ruff/crates/ty_static) Compiling gen-lsp-types v0.8.0 Compiling get-size2 v0.9.0 Compiling ruff_memory_usage v0.0.0 (/startdir/src/ty/ruff/crates/ruff_memory_usage) Compiling ruff_diagnostics v0.0.0 (/startdir/src/ty/ruff/crates/ruff_diagnostics) Compiling insta-cmd v0.6.0 Compiling ruff_notebook v0.0.0 (/startdir/src/ty/ruff/crates/ruff_notebook) Compiling salsa v0.27.0 Compiling ruff_python_ast v0.0.0 (/startdir/src/ty/ruff/crates/ruff_python_ast) Compiling ruff_index v0.0.0 (/startdir/src/ty/ruff/crates/ruff_index) Compiling ruff_python_parser v0.0.0 (/startdir/src/ty/ruff/crates/ruff_python_parser) Compiling ruff_python_literal v0.0.0 (/startdir/src/ty/ruff/crates/ruff_python_literal) Compiling ruff_db v0.0.0 (/startdir/src/ty/ruff/crates/ruff_db) Compiling ruff_python_codegen v0.0.0 (/startdir/src/ty/ruff/crates/ruff_python_codegen) Compiling ruff_python_importer v0.0.0 (/startdir/src/ty/ruff/crates/ruff_python_importer) Compiling ty_module_resolver v0.0.0 (/startdir/src/ty/ruff/crates/ty_module_resolver) Compiling ty_site_packages v0.0.0 (/startdir/src/ty/ruff/crates/ty_site_packages) Compiling ty_combine v0.0.0 (/startdir/src/ty/ruff/crates/ty_combine) Compiling ty_python_core v0.0.0 (/startdir/src/ty/ruff/crates/ty_python_core) Compiling ty_python_semantic v0.0.0 (/startdir/src/ty/ruff/crates/ty_python_semantic) Compiling ty_project v0.0.0 (/startdir/src/ty/ruff/crates/ty_project) Compiling ty_ide v0.0.0 (/startdir/src/ty/ruff/crates/ty_ide) Compiling ty_server v0.0.0 (/startdir/src/ty/ruff/crates/ty_server) Finished `test` profile [unoptimized + debuginfo] target(s) in 6m 54s Running unittests src/lib.rs (ruff/target/debug/deps/ty-4f8df442ac6b7fe8) running 4 tests test version::tests::version_formatting ... ok test version::tests::version_formatting_with_commits_since_last_tag ... ok test version::tests::version_formatting_with_commit_info ... ok test version::tests::version_serializable ... ok test result: ok. 4 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.04s Running unittests src/main.rs (ruff/target/debug/deps/ty-18469b7999eeadfd) running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s Running tests/cli/main.rs (ruff/target/debug/deps/cli-f81d98b02e0df493) running 127 tests test config_option::cli_config_args_invalid_option ... ok test check_non_existing_path ... ok test check_file_without_extension_in_subfolder ... ok test concise_revealed_type ... ok test concise_diagnostics ... ok test can_handle_large_binop_expressions ... ok test analysis_options::overrides_inherit_global ... ok test check_file_without_extension ... ok test config_option::cli_config_args_later_overrides_earlier ... ok test exit_code::only_info_and_error_on_warning_is_true ... ok test exit_code::exit_zero_is_true ... ok test analysis_options::overrides_basic ... ok test exit_code::both_warnings_and_errors_and_error_on_warning_is_true ... ok test exit_code::both_warnings_and_errors ... ok test exit_code::only_info ... ok test analysis_options::overrides_precedence ... ok test exit_code::no_errors_but_error_on_warning_is_true ... ok test exit_code::no_errors_but_error_on_warning_is_enabled_in_configuration ... ok test file_selection::invalid_include_pattern ... ok test file_selection::invalid_exclude_pattern ... ok test file_selection::invalid_include_pattern_concise_output ... ok test config_option::config_file_override ... ok test file_selection::exclude_argument_precedence_include_argument ... ok test analysis_options::respect_type_ignore_comments_is_turned_off ... ok test cli_arguments_are_relative_to_the_current_directory ... ok test file_selection::exclude_precedence_over_include ... ok test config_option::cli_config_args_overrides_ty_toml ... ok test config_option::cli_config_args_toml_string_basic ... ok test exit_code::only_warnings ... ok test check_specific_paths ... ok test file_selection::configuration_exclude ... ok test python_environment::cli_unsupported_python_version ... ok Snapshot test passes but the existing value is in a legacy format. Please run `cargo insta test --force-update-snapshots` to update to a newer format. Snapshot contents: x = 1 test fixes::fix_unfixable ... ok Snapshot test passes but the existing value is in a legacy format. Please run `cargo insta test --force-update-snapshots` to update to a newer format. Snapshot contents: x = 1 test fixes::add_ignore_unfixable ... ok test fixes::fix ... ok test fixes::fix_clean_file ... ok test file_selection::force_exclude_directory_exclusion ... ok test gitlab_empty_diagnostics ... ok test python_environment::config_file_unsupported_python_version ... ok test python_environment::config_file_python_setting_directory_with_no_site_packages ... ok test paths_in_configuration_files_are_relative_to_the_project_root ... ok test file_selection::configuration_include_no_extension ... ok test python_environment::config_file_broken_python_setting ... ok test github_diagnostics ... ok test file_selection::exclude_argument ... ok test file_selection::cli_removes_config_exclude ... ok test fixes::add_ignore ... ok test file_selection::remove_default_exclude ... ok test python_environment::config_file_python_setting_directory_with_unsupported_python_version ... ok test file_selection::configuration_include ... ok test gitlab_diagnostics ... ok test file_selection::bazel_symlinked_files ... ok test python_environment::default_root_python_package ... ok test python_environment::environment_root_takes_precedence_over_src_root ... ok test python_environment::missing_virtual_env ... ok test python_environment::default_root_flat_layout ... ok test file_selection::cli_and_configuration_exclude ... ok test python_environment::default_root_tests_folder ... ok test python_environment::config_file_annotation_showing_where_python_version_set_typing_error ... ok test python_environment::default_root_project_name_folder ... ok test python_environment::default_root_flat_layout_variant ... ok test python_environment::lib64_site_packages_directory_on_unix ... ok test python_environment::default_root_tests_package ... ok test python_environment::python_argument_points_to_symlinked_executable ... ok test file_selection::explicit_path_overrides_exclude ... ok test file_selection::exclude_symlink_source_not_target ... ok test python_environment::default_root_python_folder ... ok test python_environment::default_root_src_layout ... ok test python_environment::default_root_python_package_pyi ... ok test python_environment::config_override_python_platform ... ok test python_environment::config_file_annotation_showing_where_python_version_set_syntax_error ... ok test python_environment::config_override_python_version ... ok test python_environment::src_root_deprecation_warning_with_environment_root ... ok test python_environment::src_root_deprecation_warning ... ok test python_environment::pyvenv_cfg_file_annotation_showing_where_python_version_set ... ok test python_environment::unix_system_installation_with_no_lib_directory ... ok test rule::rule_json_output ... ok test python_environment::src_subdirectory_takes_precedence_over_repo_root ... ok test python_environment::python_cli_argument_system_installation ... ok test python_environment::pyvenv_cfg_file_annotation_no_trailing_newline ... ok # abstract-method-in-final-class Default level: error | Stable (since 0.0.13) ## What it does Checks for `@final` classes that have unimplemented abstract methods. ## Why is this bad? A class decorated with `@final` cannot be subclassed. If such a class has abstract methods that are not implemented, the class can never be properly instantiated, as the abstract methods can never be implemented (since subclassing is prohibited). At runtime, instantiation of classes with unimplemented abstract methods is only prevented for classes that have `ABCMeta` (or a subclass of it) as their metaclass. However, type checkers also enforce this for classes that do not use `ABCMeta`, since the intent for the class to be abstract is clear from the use of `@abstractmethod`. ## Example ```python from abc import ABC, abstractmethod from typing import final class Base(ABC): @abstractmethod def method(self) -> int: ... @final class Derived(Base): # Error: `Derived` does not implement `method` pass ``` # ambiguous-protocol-member Default level: warn | Stable (since 0.0.1-alpha.20) ## What it does Checks for protocol classes with members that will lead to ambiguous interfaces. ## Why is this bad? Assigning to an undeclared variable in a protocol class leads to an ambiguous interface which may lead to the type checker inferring unexpected things. It's recommended to ensure that all members of a protocol class are explicitly declared. ## Examples ```py from typing import Protocol class BaseProto(Protocol): a: int # fine (explicitly declared as `int`) def method_member(self) -> int: ... # fine: a method definition using `def` is considered a declaration c = "some variable" # error: no explicit declaration, leading to ambiguity b = method_member # error: no explicit declaration, leading to ambiguity # error: this creates implicit assignments of `d` and `e` in the protocol class body. # Were they really meant to be considered protocol members? for d, e in enumerate(range(42)): pass class SubProto(BaseProto, Protocol): a = 42 # fine (declared in superclass) ``` # assert-type-unspellable-subtype Default level: error | Stable (since 0.0.14) ## What it does Checks for `assert_type()` calls where the actual type is an unspellable subtype of the asserted type. ## Why is this bad? `assert_type()` is intended to ensure that the inferred type of a value is exactly the same as the asserted type. But in some situations, ty has nonstandard extensions to the type system that allow it to infer more precise types than can be expressed in user annotations. ty emits a different error code to `type-assertion-failure` in these situations so that users can easily differentiate between the two cases. ## Example ```python def _(x: int): assert_type(x, int) # fine if x: assert_type(x, int) # error: [assert-type-unspellable-subtype] # the actual type is `int & ~AlwaysFalsy`, # which excludes types like `Literal[0]` ``` # call-abstract-method Default level: error | Preview (since 0.0.16) ## What it does Checks for calls to abstract `@classmethod`s or `@staticmethod`s with "trivial bodies" when accessed on the class object itself. "Trivial bodies" are bodies that solely consist of `...`, `pass`, a docstring, and/or `raise NotImplementedError`. ## Why is this bad? An abstract method with a trivial body has no concrete implementation to execute, so calling such a method directly on the class will probably not have the desired effect. It is also unsound to call these methods directly on the class. Unlike other methods, ty permits abstract methods with trivial bodies to have non-`None` return types even though they always return `None` at runtime. This is because it is expected that these methods will always be overridden rather than being called directly. As a result of this exception to the normal rule, ty may infer an incorrect type if one of these methods is called directly, which may then mean that type errors elsewhere in your code go undetected by ty. Calling abstract classmethods or staticmethods via `type[X]` is allowed, since the actual runtime type could be a concrete subclass with an implementation. ## Example ```python from abc import ABC, abstractmethod class Foo(ABC): @classmethod @abstractmethod def method(cls) -> int: ... Foo.method() # Error: cannot call abstract classmethod ``` # call-non-callable Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for calls to non-callable objects. ## Why is this bad? Calling a non-callable object will raise a `TypeError` at runtime. ## Examples ```python 4() # TypeError: 'int' object is not callable ``` # call-top-callable Default level: error | Stable (since 0.0.7) ## What it does Checks for calls to objects typed as `Top[Callable[..., T]]` (the infinite union of all callable types with return type `T`). ## Why is this bad? When an object is narrowed to `Top[Callable[..., object]]` (e.g., via `callable(x)` or `isinstance(x, Callable)`), we know the object is callable, but we don't know its precise signature. This type represents the set of all possible callable types (including, e.g., functions that take no arguments and functions that require arguments), so no specific set of arguments can be guaranteed to be valid. ## Examples ```python def f(x: object): if callable(x): x() # error: We know `x` is callable, but not what arguments it accepts ``` # conflicting-declarations Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks whether a variable has been declared as two conflicting types. ## Why is this bad A variable with two conflicting declarations likely indicates a mistake. Moreover, it could lead to incorrect or ill-defined type inference for other code that relies on these variables. ## Examples ```python if b: a: int else: a: str a = 1 ``` # conflicting-metaclass Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for class definitions where the metaclass of the class being created would not be a subclass of the metaclasses of all the class's bases. ## Why is it bad? Such a class definition raises a `TypeError` at runtime. ## Examples ```python class M1(type): ... class M2(type): ... class A(metaclass=M1): ... class B(metaclass=M2): ... # TypeError: metaclass conflict class C(A, B): ... ``` # cyclic-class-definition Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for class definitions in stub files that inherit (directly or indirectly) from themselves. ## Why is it bad? Although forward references are natively supported in stub files, inheritance cycles are still disallowed, as it is impossible to resolve a consistent [method resolution order] for a class that inherits from itself. ## Examples ```python # foo.pyi class A(B): ... class B(A): ... ``` [method resolution order]: https://docs.python.org/3/glossary.html#term-method-resolution-order # cyclic-type-alias-definition Default level: error | Stable (since 0.0.1-alpha.29) ## What it does Checks for type alias definitions that (directly or mutually) refer to themselves. ## Why is it bad? Although it is permitted to define a recursive type alias, it is not meaningful to have a type alias whose expansion can only result in itself, and is therefore not allowed. ## Examples ```python type Itself = Itself type A = B type B = A ``` # dataclass-field-order Default level: error | Stable (since 0.0.15) ## What it does Checks for dataclass definitions where required fields are defined after fields with default values. ## Why is this bad? In dataclasses, all required fields (fields without default values) must be defined before fields with default values. This is a Python requirement that will raise a `TypeError` at runtime if violated. ## Example ```python from dataclasses import dataclass @dataclass class Example: x: int = 1 # Field with default value y: str # Error: Required field after field with default ``` # deprecated Default level: warn | Stable (since 0.0.1-alpha.16) ## What it does Checks for uses of deprecated items ## Why is this bad? Deprecated items should no longer be used. ## Examples ```python @warnings.deprecated("use new_func instead") def old_func(): ... old_func() # emits [deprecated] diagnostic ``` # division-by-zero Default level: ignore | Stable (since 0.0.1-alpha.1) ## What it does It detects division by zero. ## Why is this bad? Dividing by zero raises a `ZeroDivisionError` at runtime. ## Rule status This rule is currently disabled by default because of the number of false positives it can produce. ## Examples ```python 5 / 0 ``` # duplicate-base Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for class definitions with duplicate bases. ## Why is this bad? Class definitions with duplicate bases raise `TypeError` at runtime. ## Examples ```python class A: ... # TypeError: duplicate base class class B(A, A): ... ``` # duplicate-kw-only Default level: error | Stable (since 0.0.1-alpha.12) ## What it does Checks for dataclass definitions with more than one field annotated with `KW_ONLY`. ## Why is this bad? `dataclasses.KW_ONLY` is a special marker used to emulate the `*` syntax in normal signatures. It can only be used once per dataclass. Attempting to annotate two different fields with it will lead to a runtime error. ## Examples ```python from dataclasses import dataclass, KW_ONLY @dataclass class A: # Crash at runtime b: int _1: KW_ONLY c: str _2: KW_ONLY d: bytes ``` # empty-body Default level: error | Stable (since 0.0.14) ## What it does Detects functions with empty bodies that have a non-`None` return type annotation. The errors reported by this rule have the same motivation as the `invalid-return-type` rule. The diagnostic exists as a separate error code to allow users to disable this rule while prototyping code. While we strongly recommend enabling this rule if possible, users migrating from other type checkers may also find it useful to temporarily disable this rule on some or all of their codebase if they find it results in a large number of diagnostics. ## Why is this bad? A function with an empty body (containing only `...`, `pass`, or a docstring) will implicitly return `None` at runtime. Returning `None` when the return type is non-`None` is unsound, and will lead to ty inferring incorrect types elsewhere. Functions with empty bodies are permitted in certain contexts where they serve as declarations rather than implementations: - Functions in stub files (`.pyi`) - Methods in Protocol classes - Abstract methods decorated with `@abstractmethod` - Overload declarations decorated with `@overload` - Functions in `if TYPE_CHECKING` blocks ## Examples ```python def foo() -> int: ... # error: [empty-body] def bar() -> str: """A function that does nothing.""" pass # error: [empty-body] ``` # escape-character-in-forward-annotation Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for forward annotations that contain escape characters. ## Why is this bad? Static analysis tools like ty can't analyze type annotations that contain escape characters. ## Example ```python def foo() -> "intt\b": ... ``` # final-on-non-method Default level: error | Stable (since 0.0.20) ## What it does Checks for `@final` decorators applied to non-method functions. ## Why is this bad? The `@final` decorator is only meaningful on methods and classes. Applying it to a module-level function or a nested function has no effect and is likely a mistake. ## Example ```python from typing import final # Error: @final is not allowed on non-method functions @final def my_function() -> int: return 0 ``` # final-without-value Default level: error | Stable (since 0.0.15) ## What it does Checks for `Final` symbols that are declared without a value and are never assigned a value in their scope. ## Why is this bad? A `Final` symbol must be initialized with a value at the time of declaration or in a subsequent assignment. At module or function scope, the assignment must occur in the same scope. In a class body, the assignment may occur in `__init__`. ## Examples ```python from typing import Final # Error: `Final` symbol without a value MY_CONSTANT: Final[int] # OK: `Final` symbol with a value MY_CONSTANT: Final[int] = 1 ``` # ignore-comment-unknown-rule Default level: warn | Stable (since 0.0.1-alpha.1) ## What it does Checks for `ty: ignore[code]` or `type: ignore[ty:code]` comments where `code` isn't a known lint rule. ## Why is this bad? A `ty: ignore[code]` or a `type:ignore[ty:code] directive with a `code` that doesn't match any known rule will not suppress any type errors, and is probably a mistake. ## Examples ```py a = 20 / 0 # ty: ignore[division-by-zer] ``` Use instead: ```py a = 20 / 0 # ty: ignore[division-by-zero] ``` # implicit-concatenated-string-type-annotation Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for implicit concatenated strings in type annotation positions. ## Why is this bad? Static analysis tools like ty can't analyze type annotations that use implicit concatenated strings. ## Examples ```python def test(): -> "Literal[" "5" "]": ... ``` Use instead: ```python def test(): -> "Literal[5]": ... ``` # inconsistent-mro Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for classes with an inconsistent [method resolution order] (MRO). ## Why is this bad? Classes with an inconsistent MRO will raise a `TypeError` at runtime. ## Examples ```python class A: ... class B(A): ... # TypeError: Cannot create a consistent method resolution order class C(A, B): ... ``` [method resolution order]: https://docs.python.org/3/glossary.html#term-method-resolution-order # index-out-of-bounds Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for attempts to use an out of bounds index to get an item from a container. ## Why is this bad? Using an out of bounds index will raise an `IndexError` at runtime. ## Examples ```python t = (0, 1, 2) t[3] # IndexError: tuple index out of range ``` # ineffective-final Default level: warn | Stable (since 0.0.1-alpha.33) ## What it does Checks for calls to `final()` that type checkers cannot interpret. ## Why is this bad? The `final()` function is designed to be used as a decorator. When called directly as a function (e.g., `final(type(...))`), type checkers will not understand the application of `final` and will not prevent subclassing. ## Example ```python from typing import final # Incorrect: type checkers will not prevent subclassing MyClass = final(type("MyClass", (), {})) # Correct: use `final` as a decorator @final class MyClass: ... ``` # instance-layout-conflict Default level: error | Stable (since 0.0.1-alpha.12) ## What it does Checks for classes definitions which will fail at runtime due to "instance memory layout conflicts". This error is usually caused by attempting to combine multiple classes that define non-empty `__slots__` in a class's [Method Resolution Order] (MRO), or by attempting to combine multiple builtin classes in a class's MRO. ## Why is this bad? Inheriting from bases with conflicting instance memory layouts will lead to a `TypeError` at runtime. An instance memory layout conflict occurs when CPython cannot determine the memory layout instances of a class should have, because the instance memory layout of one of its bases conflicts with the instance memory layout of one or more of its other bases. For example, if a Python class defines non-empty `__slots__`, this will impact the memory layout of instances of that class. Multiple inheritance from more than one different class defining non-empty `__slots__` is not allowed: ```python class A: __slots__ = ("a", "b") class B: __slots__ = ("a", "b") # Even if the values are the same # TypeError: multiple bases have instance lay-out conflict class C(A, B): ... ``` An instance layout conflict can also be caused by attempting to use multiple inheritance with two builtin classes, due to the way that these classes are implemented in a CPython C extension: ```python class A(int, float): ... # TypeError: multiple bases have instance lay-out conflict ``` Note that pure-Python classes with no `__slots__`, or pure-Python classes with empty `__slots__`, are always compatible: ```python class A: ... class B: __slots__ = () class C: __slots__ = ("a", "b") # fine class D(A, B, C): ... ``` ## Known problems Classes that have "dynamic" definitions of `__slots__` (definitions do not consist of string literals, or tuples of string literals) are not currently considered disjoint bases by ty. Additionally, this check is not exhaustive: many C extensions (including several in the standard library) define classes that use extended memory layouts and thus cannot coexist in a single MRO. Since it is currently not possible to represent this fact in stub files, having a full knowledge of these classes is also impossible. When it comes to classes that do not define `__slots__` at the Python level, therefore, ty, currently only hard-codes a number of cases where it knows that a class will produce instances with an atypical memory layout. ## Further reading - [CPython documentation: `__slots__`](https://docs.python.org/3/reference/datamodel.html#slots) - [CPython documentation: Method Resolution Order](https://docs.python.org/3/glossary.html#term-method-resolution-order) [Method Resolution Order]: https://docs.python.org/3/glossary.html#term-method-resolution-order # invalid-argument-type Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Detects call arguments whose type is not assignable to the corresponding typed parameter. ## Why is this bad? Passing an argument of a type the function (or callable object) does not accept violates the expectations of the function author and may cause unexpected runtime errors within the body of the function. ## Examples ```python def func(x: int): ... func("foo") # error: [invalid-argument-type] ``` # invalid-assignment Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for assignments where the type of the value is not [assignable to] the type of the assignee. ## Why is this bad? Such assignments break the rules of the type system and weaken a type checker's ability to accurately reason about your code. ## Examples ```python a: int = '' ``` [assignable to]: https://typing.python.org/en/latest/spec/glossary.html#term-assignable # invalid-attribute-access Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for assignments to class variables from instances and assignments to instance variables from its class. ## Why is this bad? Incorrect assignments break the rules of the type system and weaken a type checker's ability to accurately reason about your code. ## Examples ```python class C: class_var: ClassVar[int] = 1 instance_var: int C.class_var = 3 # okay C().class_var = 3 # error: Cannot assign to class variable C().instance_var = 3 # okay C.instance_var = 3 # error: Cannot assign to instance variable ``` # invalid-attribute-override Default level: error | Stable (since 0.0.33) ## What it does Detects attribute overrides that change whether an inherited attribute is a class variable or an instance variable. This rule currently only covers class-variable and instance-variable category changes. ## Why is this bad? Pure class variables and instance variables have different access and assignment behavior. Overriding one with the other violates the [Liskov Substitution Principle] ("LSP"), because code that is valid for the superclass may no longer be valid for the subclass. ## Example ```python from typing import ClassVar class Base: instance_attr: int class_attr: ClassVar[int] class Sub(Base): instance_attr: ClassVar[int] # error: [invalid-attribute-override] class_attr: int # error: [invalid-attribute-override] ``` [Liskov Substitution Principle]: https://en.wikipedia.org/wiki/Liskov_substitution_principle # invalid-await Default level: error | Stable (since 0.0.1-alpha.19) ## What it does Checks for `await` being used with types that are not [Awaitable]. ## Why is this bad? Such expressions will lead to `TypeError` being raised at runtime. ## Examples ```python import asyncio class InvalidAwait: def __await__(self) -> int: return 5 async def main() -> None: await InvalidAwait() # error: [invalid-await] await 42 # error: [invalid-await] asyncio.run(main()) ``` [Awaitable]: https://docs.python.org/3/library/collections.abc.html#collections.abc.Awaitable # invalid-base Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for class definitions that have bases which are not instances of `type`. ## Why is this bad? Class definitions with bases like this will lead to `TypeError` being raised at runtime. ## Examples ```python class A(42): ... # error: [invalid-base] ``` # invalid-context-manager Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for expressions used in `with` statements that do not implement the context manager protocol. ## Why is this bad? Such a statement will raise `TypeError` at runtime. ## Examples ```python # TypeError: 'int' object does not support the context manager protocol with 1: print(2) ``` # invalid-dataclass Default level: error | Stable (since 0.0.12) ## What it does Checks for invalid applications of the `@dataclass` decorator. ## Why is this bad? Applying `@dataclass` to a class that inherits from `NamedTuple`, `TypedDict`, `Enum`, or `Protocol` is invalid: - `NamedTuple` and `TypedDict` classes will raise an exception at runtime when instantiating the class. - `Enum` classes with `@dataclass` are [explicitly not supported]. - `Protocol` classes define interfaces and cannot be instantiated. ## Examples ```python from dataclasses import dataclass from typing import NamedTuple @dataclass # error: [invalid-dataclass] class Foo(NamedTuple): x: int ``` [explicitly not supported]: https://docs.python.org/3/howto/enum.html#dataclass-support # invalid-dataclass-override Default level: error | Stable (since 0.0.13) ## What it does Checks for dataclass definitions that have both `frozen=True` and a custom `__setattr__` or `__delattr__` method defined. ## Why is this bad? Frozen dataclasses synthesize `__setattr__` and `__delattr__` methods which raise a `FrozenInstanceError` to emulate immutability. Overriding either of these methods raises a runtime error. ## Examples ```python from dataclasses import dataclass @dataclass(frozen=True) class A: def __setattr__(self, name: str, value: object) -> None: ... ``` # invalid-declaration Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for declarations where the inferred type of an existing symbol is not [assignable to] its post-hoc declared type. ## Why is this bad? Such declarations break the rules of the type system and weaken a type checker's ability to accurately reason about your code. ## Examples ```python a = 1 a: str ``` [assignable to]: https://typing.python.org/en/latest/spec/glossary.html#term-assignable # invalid-enum-member-annotation Default level: warn | Stable (since 0.0.20) ## What it does Checks for enum members that have explicit type annotations. ## Why is this bad? The [typing spec] states that type checkers should infer a literal type for all enum members. An explicit type annotation on an enum member is misleading because the annotated type will be incorrect — the actual runtime type is the enum class itself, not the annotated type. In CPython's `enum` module, annotated assignments with values are still treated as members at runtime, but the annotation will confuse readers of the code. ## Examples ```python from enum import Enum class Pet(Enum): CAT = 1 # OK DOG: int = 2 # Error: enum members should not be annotated ``` Use instead: ```python from enum import Enum class Pet(Enum): CAT = 1 DOG = 2 ``` ## References - [Typing spec: Enum members](https://typing.python.org/en/latest/spec/enums.html#enum-members) [typing spec]: https://typing.python.org/en/latest/spec/enums.html#enum-members # invalid-exception-caught Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for exception handlers that catch non-exception classes. ## Why is this bad? Catching classes that do not inherit from `BaseException` will raise a `TypeError` at runtime. ## Example ```python try: 1 / 0 except 1: ... ``` Use instead: ```python try: 1 / 0 except ZeroDivisionError: ... ``` ## References - [Python documentation: except clause](https://docs.python.org/3/reference/compound_stmts.html#except-clause) - [Python documentation: Built-in Exceptions](https://docs.python.org/3/library/exceptions.html#built-in-exceptions) ## Ruff rule This rule corresponds to Ruff's [`except-with-non-exception-classes` (`B030`)](https://docs.astral.sh/ruff/rules/except-with-non-exception-classes) # invalid-explicit-override Default level: error | Stable (since 0.0.1-alpha.28) ## What it does Checks for methods that are decorated with `@override` but do not override any method in a superclass. ## Why is this bad? Decorating a method with `@override` declares to the type checker that the intention is that it should override a method from a superclass. ## Example ```python from typing import override class A: @override def foo(self): ... # Error raised here class B(A): @override def ffooo(self): ... # Error raised here class C: @override def __repr__(self): ... # fine: overrides `object.__repr__` class D(A): @override def foo(self): ... # fine: overrides `A.foo` ``` # invalid-frozen-dataclass-subclass Default level: error | Stable (since 0.0.1-alpha.35) ## What it does Checks for dataclasses with invalid frozen inheritance: - A frozen dataclass cannot inherit from a non-frozen dataclass. - A non-frozen dataclass cannot inherit from a frozen dataclass. ## Why is this bad? Python raises a `TypeError` at runtime when either of these inheritance patterns occurs. ## Example ```python from dataclasses import dataclass @dataclass class Base: x: int @dataclass(frozen=True) class Child(Base): # Error raised here y: int @dataclass(frozen=True) class FrozenBase: x: int @dataclass class NonFrozenChild(FrozenBase): # Error raised here y: int ``` # invalid-generic-class Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for the creation of invalid generic classes ## Why is this bad? There are several requirements that you must follow when defining a generic class. Many of these result in `TypeError` being raised at runtime if they are violated. ## Examples ```python from typing_extensions import Generic, TypeVar T = TypeVar("T") U = TypeVar("U", default=int) # error: class uses both PEP-695 syntax and legacy syntax class C[U](Generic[T]): ... # error: type parameter with default comes before type parameter without default class D(Generic[U, T]): ... ``` ## References - [Typing spec: Generics](https://typing.python.org/en/latest/spec/generics.html#introduction) # invalid-generic-enum Default level: error | Stable (since 0.0.12) ## What it does Checks for enum classes that are also generic. ## Why is this bad? Enum classes cannot be generic. Python does not support generic enums: attempting to create one will either result in an immediate `TypeError` at runtime, or will create a class that cannot be specialized in the way that a normal generic class can. ## Examples ```python from enum import Enum from typing import Generic, TypeVar T = TypeVar("T") # error: enum class cannot be generic (class creation fails with `TypeError`) class E[T](Enum): A = 1 # error: enum class cannot be generic (class creation fails with `TypeError`) class F(Enum, Generic[T]): A = 1 # error: enum class cannot be generic -- the class creation does not immediately fail... class G(Generic[T], Enum): A = 1 # ...but this raises `KeyError`: x: G[int] ``` ## References - [Python documentation: Enum](https://docs.python.org/3/library/enum.html) # invalid-ignore-comment Default level: warn | Stable (since 0.0.1-alpha.1) ## What it does Checks for `type: ignore` and `ty: ignore` comments that are syntactically incorrect. ## Why is this bad? A syntactically incorrect ignore comment is probably a mistake and is useless. ## Examples ```py a = 20 / 0 # type: ignoree ``` Use instead: ```py a = 20 / 0 # type: ignore ``` # invalid-key Default level: error | Stable (since 0.0.1-alpha.17) ## What it does Checks for subscript accesses with invalid keys and `TypedDict` construction with an unknown key. ## Why is this bad? Subscripting with an invalid key will raise a `KeyError` at runtime. Creating a `TypedDict` with an unknown key is likely a mistake; if the `TypedDict` is `closed=true` it also violates the expectations of the type. ## Examples ```python from typing import TypedDict class Person(TypedDict): name: str age: int alice = Person(name="Alice", age=30) alice["height"] # KeyError: 'height' bob: Person = { "nickname": "Bob", "age": 30 } # typo! carol = Person(name="Carol", aeg=25) # typo! ``` # invalid-legacy-positional-parameter Default level: warn | Stable (since 0.0.15) ## What it does Checks for parameters that appear to be attempting to use the legacy convention to specify that a parameter is positional-only, but do so incorrectly. The "legacy convention" for specifying positional-only parameters was specified in [PEP 484]. It states that parameters with names starting with `__` should be considered positional-only by type checkers. [PEP 570], introduced in Python 3.8, added dedicated syntax for specifying positional-only parameters, rendering the legacy convention obsolete. However, some codebases may still use the legacy convention for compatibility with older Python versions. ## Why is this bad? In most cases, a type checker will not consider a parameter to be positional-only if it comes after a positional-or-keyword parameter, even if its name starts with `__`. This may be unexpected to the author of the code. ## Example ```python def f(x, __y): # Error: `__y` is not considered positional-only pass ``` Use instead: ```python def f(__x, __y): # If you need compatibility with Python <=3.7 pass ``` or: ```python def f(x, y, /): # Python 3.8+ syntax pass ``` ## References - [Typing spec: positional-only parameters (legacy syntax)](https://typing.python.org/en/latest/spec/historical.html#pos-only-double-underscore) - [Python glossary: parameters](https://docs.python.org/3/glossary.html#term-parameter) [PEP 484]: https://peps.python.org/pep-0484/#positional-only-arguments [PEP 570]: https://peps.python.org/pep-0570/ # invalid-legacy-type-variable Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for the creation of invalid legacy `TypeVar`s ## Why is this bad? There are several requirements that you must follow when creating a legacy `TypeVar`. ## Examples ```python from typing import TypeVar T = TypeVar("T") # okay T = TypeVar("T") # error: TypeVars should not be redefined # error: TypeVar must be immediately assigned to a variable def f(t: TypeVar("U")): ... ``` ## References - [Typing spec: Generics](https://typing.python.org/en/latest/spec/generics.html#introduction) # invalid-match-pattern Default level: error | Stable (since 0.0.18) ## What it does Checks for invalid match patterns. ## Why is this bad? Matching on invalid patterns will lead to a runtime error. ## Examples ```python NotAClass = 42 match x: case NotAClass(): # TypeError at runtime: must be a class ... ``` # invalid-metaclass Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for arguments to `metaclass=` that are invalid. ## Why is this bad? Python allows arbitrary expressions to be used as the argument to `metaclass=`. These expressions, however, need to be callable and accept the same arguments as `type.__new__`. ## Example ```python def f(): ... # TypeError: f() takes 0 positional arguments but 3 were given class B(metaclass=f): ... ``` ## References - [Python documentation: Metaclasses](https://docs.python.org/3/reference/datamodel.html#metaclasses) # invalid-method-override Default level: error | Stable (since 0.0.1-alpha.20) ## What it does Detects method overrides that violate the [Liskov Substitution Principle] ("LSP"). The LSP states that an instance of a subtype should be substitutable for an instance of its supertype. Applied to Python, this means: 1. All argument combinations a superclass method accepts must also be accepted by an overriding subclass method. 2. The return type of an overriding subclass method must be a subtype of the return type of the superclass method. ## Why is this bad? Violating the Liskov Substitution Principle will lead to many of ty's assumptions and inferences being incorrect, which will mean that it will fail to catch many possible type errors in your code. ## Example ```python class Super: def method(self, x) -> int: return 42 class Sub(Super): # Liskov violation: `str` is not a subtype of `int`, # but the supertype method promises to return an `int`. def method(self, x) -> str: # error: [invalid-override] return "foo" def accepts_super(s: Super) -> int: return s.method(x=42) accepts_super(Sub()) # The result of this call is a string, but ty will infer # it to be an `int` due to the violation of the Liskov Substitution Principle. class Sub2(Super): # Liskov violation: the superclass method can be called with a `x=` # keyword argument, but the subclass method does not accept it. def method(self, y) -> int: # error: [invalid-override] return 42 accepts_super(Sub2()) # TypeError at runtime: method() got an unexpected keyword argument 'x' # ty cannot catch this error due to the violation of the Liskov Substitution Principle. ``` ## Common issues ### Why does ty complain about my `__eq__` method? `__eq__` and `__ne__` methods in Python are generally expected to accept arbitrary objects as their second argument, for example: ```python class A: x: int def __eq__(self, other: object) -> bool: # gracefully handle an object of an unexpected type # without raising an exception if not isinstance(other, A): return False return self.x == other.x ``` If `A.__eq__` here were annotated as only accepting `A` instances for its second argument, it would imply that you wouldn't be able to use `==` between instances of `A` and instances of unrelated classes without an exception possibly being raised. While some classes in Python do indeed behave this way, the strongly held convention is that it should be avoided wherever possible. As part of this check, therefore, ty enforces that `__eq__` and `__ne__` methods accept `object` as their second argument. ### Why does ty disagree with Ruff about how to write my method? Ruff has several rules that will encourage you to rename a parameter, or change its type signature, if it thinks you're falling into a certain anti-pattern. For example, Ruff's [ARG002](https://docs.astral.sh/ruff/rules/unused-method-argument/) rule recommends that an unused parameter should either be removed or renamed to start with `_`. Applying either of these suggestions can cause ty to start reporting an `invalid-method-override` error if the function in question is a method on a subclass that overrides a method on a superclass, and the change would cause the subclass method to no longer accept all argument combinations that the superclass method accepts. This can usually be resolved by adding [`@typing.override`][override] to your method definition. Ruff knows that a method decorated with `@typing.override` is intended to override a method by the same name on a superclass, and avoids reporting rules like ARG002 for such methods; it knows that the changes recommended by ARG002 would violate the Liskov Substitution Principle. Correct use of `@override` is enforced by ty's `invalid-explicit-override` rule. [Liskov Substitution Principle]: https://en.wikipedia.org/wiki/Liskov_substitution_principle [override]: https://docs.python.org/3/library/typing.html#typing.override # invalid-named-tuple Default level: error | Stable (since 0.0.1-alpha.19) ## What it does Checks for invalidly defined `NamedTuple` classes. ## Why is this bad? An invalidly defined `NamedTuple` class may lead to the type checker drawing incorrect conclusions. It may also lead to `TypeError`s or `AttributeError`s at runtime. ## Examples A class definition cannot combine `NamedTuple` with other base classes in multiple inheritance; doing so raises a `TypeError` at runtime. The sole exception to this rule is `Generic[]`, which can be used alongside `NamedTuple` in a class's bases list. ```pycon >>> from typing import NamedTuple >>> class Foo(NamedTuple, object): ... TypeError: can only inherit from a NamedTuple type and Generic ``` Further, `NamedTuple` field names cannot start with an underscore: ```pycon >>> from typing import NamedTuple >>> class Foo(NamedTuple): ... _bar: int ValueError: Field names cannot start with an underscore: '_bar' ``` `NamedTuple` classes also have certain synthesized attributes (like `_asdict`, `_make`, `_replace`, etc.) that cannot be overwritten. Attempting to assign to these attributes without a type annotation will raise an `AttributeError` at runtime. ```pycon >>> from typing import NamedTuple >>> class Foo(NamedTuple): ... x: int ... _asdict = 42 AttributeError: Cannot overwrite NamedTuple attribute _asdict ``` # invalid-named-tuple-override Default level: warn | Stable (since 0.0.31) ## What it does Checks for subclass members that override inherited `NamedTuple` fields. ## Why is this bad? Reusing an inherited `NamedTuple` field name in a subclass creates a class where tuple indexing and `repr()` still reflect the original field, while attribute access follows the subclass member. ## Default level This rule is a warning by default because these overrides do not make the class invalid at runtime. ## Examples ```python from typing import NamedTuple class User(NamedTuple): name: str class Admin(User): name = "shadowed" # error: [invalid-named-tuple-override] admin = Admin("Alice") admin.name # "shadowed" admin[0] # "Alice" ``` # invalid-newtype Default level: error | Stable (since 0.0.1-alpha.27) ## What it does Checks for the creation of invalid `NewType`s ## Why is this bad? There are several requirements that you must follow when creating a `NewType`. ## Examples ```python from typing import NewType def get_name() -> str: ... Foo = NewType("Foo", int) # okay Bar = NewType(get_name(), int) # error: The first argument to `NewType` must be a string literal Baz = NewType("Baz", int | str) # error: invalid base for `typing.NewType` ``` # invalid-overload Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for various invalid `@overload` usages. ## Why is this bad? The `@overload` decorator is used to define functions and methods that accepts different combinations of arguments and return different types based on the arguments passed. This is mainly beneficial for type checkers. But, if the `@overload` usage is invalid, the type checker may not be able to provide correct type information. ## Example Defining only one overload: ```py from typing import overload @overload def foo(x: int) -> int: ... def foo(x: int | None) -> int | None: return x ``` Or, not providing an implementation for the overloaded definition: ```py from typing import overload @overload def foo() -> None: ... @overload def foo(x: int) -> int: ... ``` ## References - [Python documentation: `@overload`](https://docs.python.org/3/library/typing.html#typing.overload) # invalid-parameter-default Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for default values that can't be assigned to the parameter's annotated type. ## Why is this bad? This breaks the rules of the type system and weakens a type checker's ability to accurately reason about your code. ## Examples ```python def f(a: int = ''): ... ``` # invalid-paramspec Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for the creation of invalid `ParamSpec`s ## Why is this bad? There are several requirements that you must follow when creating a `ParamSpec`. ## Examples ```python from typing import ParamSpec P1 = ParamSpec("P1") # okay P2 = ParamSpec() # error: ParamSpec requires a name ``` ## References - [Typing spec: ParamSpec](https://typing.python.org/en/latest/spec/generics.html#paramspec) # invalid-protocol Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for protocol classes that will raise `TypeError` at runtime. ## Why is this bad? An invalidly defined protocol class may lead to the type checker inferring unexpected things. It may also lead to `TypeError`s at runtime. ## Examples A `Protocol` class cannot inherit from a non-`Protocol` class; this raises a `TypeError` at runtime: ```pycon >>> from typing import Protocol >>> class Foo(int, Protocol): ... ... Traceback (most recent call last): File "", line 1, in class Foo(int, Protocol): ... TypeError: Protocols can only inherit from other protocols, got ``` # invalid-raise Default level: error | Stable (since 0.0.1-alpha.1) Checks for `raise` statements that raise non-exceptions or use invalid causes for their raised exceptions. ## Why is this bad? Only subclasses or instances of `BaseException` can be raised. For an exception's cause, the same rules apply, except that `None` is also permitted. Violating these rules results in a `TypeError` at runtime. ## Examples ```python def f(): try: something() except NameError: raise "oops!" from f def g(): raise NotImplemented from 42 ``` Use instead: ```python def f(): try: something() except NameError as e: raise RuntimeError("oops!") from e def g(): raise NotImplementedError from None ``` ## References - [Python documentation: The `raise` statement](https://docs.python.org/3/reference/simple_stmts.html#raise) - [Python documentation: Built-in Exceptions](https://docs.python.org/3/library/exceptions.html#built-in-exceptions) # invalid-return-type Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Detects returned values that can't be assigned to the function's annotated return type. Note that the special case of a function with a non-`None` return type and an empty body is handled by the separate `empty-body` error code. ## Why is this bad? Returning an object of a type incompatible with the annotated return type is unsound, and will lead to ty inferring incorrect types elsewhere. ## Examples ```python def func() -> int: return "a" # error: [invalid-return-type] ``` # invalid-super-argument Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Detects `super()` calls where: - the first argument is not a valid class literal, or - the second argument is not an instance or subclass of the first argument. ## Why is this bad? `super(type, obj)` expects: - the first argument to be a class, - and the second argument to satisfy one of the following: - `isinstance(obj, type)` is `True` - `issubclass(obj, type)` is `True` Violating this relationship will raise a `TypeError` at runtime. ## Examples ```python class A: ... class B(A): ... super(A, B()) # it's okay! `A` satisfies `isinstance(B(), A)` super(A(), B()) # error: `A()` is not a class super(B, A()) # error: `A()` does not satisfy `isinstance(A(), B)` super(B, A) # error: `A` does not satisfy `issubclass(A, B)` ``` ## References - [Python documentation: super()](https://docs.python.org/3/library/functions.html#super) # invalid-syntax-in-forward-annotation Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for string-literal annotations where the string cannot be parsed as a Python expression. ## Why is this bad? Type annotations are expected to be Python expressions that describe the expected type of a variable, parameter, attribute or `return` statement. Type annotations are permitted to be string-literal expressions, in order to enable forward references to names not yet defined. However, it must be possible to parse the contents of that string literal as a normal Python expression. ## Example ```python def foo() -> "intstance of C": return 42 class C: ... ``` Use instead: ```python def foo() -> "C": return 42 class C: ... ``` ## References - [Typing spec: The meaning of annotations](https://typing.python.org/en/latest/spec/annotations.html#the-meaning-of-annotations) - [Typing spec: String annotations](https://typing.python.org/en/latest/spec/annotations.html#string-annotations) # invalid-total-ordering Default level: error | Stable (since 0.0.10) ## What it does Checks for classes decorated with `@functools.total_ordering` that don't define any ordering method (`__lt__`, `__le__`, `__gt__`, or `__ge__`). ## Why is this bad? The `@total_ordering` decorator requires the class to define at least one ordering method. If none is defined, Python raises a `ValueError` at runtime. ## Example ```python from functools import total_ordering @total_ordering class MyClass: # Error: no ordering method defined def __eq__(self, other: object) -> bool: return True ``` Use instead: ```python from functools import total_ordering @total_ordering class MyClass: def __eq__(self, other: object) -> bool: return True def __lt__(self, other: "MyClass") -> bool: return True ``` # invalid-type-alias-type Default level: error | Stable (since 0.0.1-alpha.6) ## What it does Checks for the creation of invalid `TypeAliasType`s ## Why is this bad? There are several requirements that you must follow when creating a `TypeAliasType`. ## Examples ```python from typing import TypeAliasType IntOrStr = TypeAliasType("IntOrStr", int | str) # okay NewAlias = TypeAliasType(get_name(), int) # error: TypeAliasType name must be a string literal ``` # invalid-type-arguments Default level: error | Stable (since 0.0.1-alpha.29) ## What it does Checks for invalid type arguments in explicit type specialization. ## Why is this bad? Providing the wrong number of type arguments or type arguments that don't satisfy the type variable's bounds or constraints will lead to incorrect type inference and may indicate a misunderstanding of the generic type's interface. ## Examples Using legacy type variables: ```python from typing import Generic, TypeVar T1 = TypeVar('T1', int, str) T2 = TypeVar('T2', bound=int) class Foo1(Generic[T1]): ... class Foo2(Generic[T2]): ... Foo1[bytes] # error: bytes does not satisfy T1's constraints Foo2[str] # error: str does not satisfy T2's bound ``` Using PEP 695 type variables: ```python class Foo[T]: ... class Bar[T, U]: ... Foo[int, str] # error: too many arguments Bar[int] # error: too few arguments ``` # invalid-type-checking-constant Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for a value other than `False` assigned to the `TYPE_CHECKING` variable, or an annotation not assignable from `bool`. ## Why is this bad? The name `TYPE_CHECKING` is reserved for a flag that can be used to provide conditional code seen only by the type checker, and not at runtime. Normally this flag is imported from `typing` or `typing_extensions`, but it can also be defined locally. If defined locally, it must be assigned the value `False` at runtime; the type checker will consider its value to be `True`. If annotated, it must be annotated as a type that can accept `bool` values. ## Examples ```python TYPE_CHECKING: str TYPE_CHECKING = '' ``` # invalid-type-form Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for expressions that are used as [type expressions] but cannot validly be interpreted as such. ## Why is this bad? Such expressions cannot be understood by ty. In some cases, they might raise errors at runtime. ## Examples ```python from typing import Annotated a: type[1] # `1` is not a type b: Annotated[int] # `Annotated` expects at least two arguments ``` [type expressions]: https://typing.python.org/en/latest/spec/annotations.html#type-and-annotation-expressions # invalid-type-guard-call Default level: error | Stable (since 0.0.1-alpha.11) ## What it does Checks for type guard function calls without a valid target. ## Why is this bad? The first non-keyword non-variadic argument to a type guard function is its target and must map to a symbol. Starred (`is_str(*a)`), literal (`is_str(42)`) and other non-symbol-like expressions are invalid as narrowing targets. ## Examples ```python from typing import TypeIs def is_int(value: object = object()) -> TypeIs[int]: return isinstance(value, int) is_int() # Error: no positional narrowing target is_int(value=1) # Error: narrowing target passed by keyword ``` # invalid-type-guard-definition Default level: error | Stable (since 0.0.1-alpha.11) ## What it does Checks for type guard functions without a first non-self-like non-keyword-only non-variadic parameter. ## Why is this bad? Type narrowing functions must accept at least one positional argument (non-static methods must accept another in addition to `self`/`cls`). Extra parameters/arguments are allowed but do not affect narrowing. ## Examples ```python from typing import TypeIs def f() -> TypeIs[int]: ... # Error, no parameter def f(*, v: object) -> TypeIs[int]: ... # Error, no positional arguments allowed def f(*args: object) -> TypeIs[int]: ... # Error, expect variadic arguments class C: def f(self) -> TypeIs[int]: ... # Error, only positional argument expected is `self` ``` # invalid-type-variable-bound Default level: error | Stable (since 0.0.15) ## What it does Checks for [type variables] whose bounds reference type variables. ## Why is this bad? The bound of a type variable must be a concrete type. ## Examples ```python T = TypeVar('T', bound=list['T']) # error: [invalid-type-variable-bound] U = TypeVar('U') T = TypeVar('T', bound=U) # error: [invalid-type-variable-bound] def f[T: list[T]](): ... # error: [invalid-type-variable-bound] def g[U, T: U](): ... # error: [invalid-type-variable-bound] ``` [type variable]: https://docs.python.org/3/library/typing.html#typing.TypeVar # invalid-type-variable-constraints Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for constrained [type variables] with only one constraint, or that those constraints reference type variables. ## Why is this bad? A constrained type variable must have at least two constraints. ## Examples ```python from typing import TypeVar T = TypeVar('T', str) # invalid constrained TypeVar I = TypeVar('I', bound=int) U = TypeVar('U', list[I], int) # invalid constrained TypeVar ``` Use instead: ```python T = TypeVar('T', str, int) # valid constrained TypeVar # or T = TypeVar('T', bound=str) # valid bound TypeVar U = TypeVar('U', list[int], int) # valid constrained Type ``` [type variables]: https://docs.python.org/3/library/typing.html#typing.TypeVar # invalid-type-variable-default Default level: error | Stable (since 0.0.16) ## What it does Checks for [type variables] whose default type is not compatible with the type variable's bound or constraints. ## Why is this bad? If a type variable has a bound, the default must be assignable to that bound (see: [bound rules]). If a type variable has constraints, the default must be one of the constraints (see: [constraint rules]). ## Examples ```python T = TypeVar("T", bound=str, default=int) # error: [invalid-type-variable-default] U = TypeVar("U", int, str, default=bytes) # error: [invalid-type-variable-default] ``` [type variables]: https://docs.python.org/3/library/typing.html#typing.TypeVar [bound rules]: https://typing.python.org/en/latest/spec/generics.html#bound-rules [constraint rules]: https://typing.python.org/en/latest/spec/generics.html#constraint-rules # invalid-typed-dict-field Default level: error | Stable (since 0.0.28) ## What it does Detects invalid `TypedDict` field declarations. ## Why is this bad? `TypedDict` subclasses cannot redefine inherited fields incompatibly. Doing so breaks the subtype guarantees that `TypedDict` inheritance is meant to preserve. ## Example ```python from typing import TypedDict class Base(TypedDict): x: int class Child(Base): x: str # error: [invalid-typed-dict-field] ``` # invalid-typed-dict-header Default level: error | Stable (since 0.0.14) ## What it does Detects errors in `TypedDict` class headers, such as unexpected arguments or invalid base classes. ## Why is this bad? The typing spec states that `TypedDict`s are not permitted to have custom metaclasses. Using `**` unpacking in a `TypedDict` header is also prohibited by ty, as it means that ty cannot statically determine whether keys in the `TypedDict` are intended to be required or optional. ## Example ```python from typing import TypedDict class Foo(TypedDict, metaclass=whatever): # error: [invalid-typed-dict-header] ... def f(x: dict): class Bar(TypedDict, **x): # error: [invalid-typed-dict-header] ... ``` # invalid-typed-dict-statement Default level: error | Stable (since 0.0.9) ## What it does Detects statements other than annotated declarations in `TypedDict` class bodies. ## Why is this bad? `TypedDict` class bodies aren't allowed to contain any other types of statements. For example, method definitions and field values aren't allowed. None of these will be available on "instances of the `TypedDict`" at runtime (as `dict` is the runtime class of all "`TypedDict` instances"). ## Example ```python from typing import TypedDict class Foo(TypedDict): def bar(self): # error: [invalid-typed-dict-statement] pass ``` # invalid-yield Default level: error | Stable (since 0.0.25) ## What it does Detects `yield` and `yield from` expressions where the "yield" or "send" type is incompatible with the generator function's annotated return type. ## Why is this bad? Yielding a value of a type that doesn't match the generator's declared yield type, or using `yield from` with a sub-iterator whose yield or send type is incompatible, is a type error that may cause downstream consumers of the generator to receive values of an unexpected type. ## Examples ```python from typing import Iterator def gen() -> Iterator[int]: yield "not an int" # error: [invalid-yield] ``` # isinstance-against-protocol Default level: error | Stable (since 0.0.14) ## What it does Reports invalid runtime checks against `Protocol` classes. This includes explicit calls `isinstance()`/`issubclass()` against non-runtime-checkable protocols, `issubclass()` calls against protocols that have non-method members, and implicit `isinstance()` checks against non-runtime-checkable protocols via pattern matching. ## Why is this bad? These calls (implicit or explicit) raise `TypeError` at runtime. ## Examples ```python from typing_extensions import Protocol, runtime_checkable class HasX(Protocol): x: int @runtime_checkable class HasY(Protocol): y: int def f(arg: object, arg2: type): isinstance(arg, HasX) # error: [isinstance-against-protocol] (not runtime-checkable) issubclass(arg2, HasX) # error: [isinstance-against-protocol] (not runtime-checkable) def g(arg: object): match arg: case HasX(): # error: [isinstance-against-protocol] (not runtime-checkable) pass def h(arg2: type): isinstance(arg2, HasY) # fine (runtime-checkable) # `HasY` is runtime-checkable, but has non-method members, # so it still can't be used in `issubclass` checks) issubclass(arg2, HasY) # error: [isinstance-against-protocol] ``` ## References - [Typing documentation: `@runtime_checkable`](https://docs.python.org/3/library/typing.html#typing.runtime_checkable) # isinstance-against-typed-dict Default level: error | Stable (since 0.0.15) ## What it does Reports runtime checks against `TypedDict` classes. This includes explicit calls to `isinstance()`/`issubclass()` and implicit checks performed by `match` class patterns. ## Why is this bad? Using a `TypedDict` class in these contexts raises `TypeError` at runtime. ## Examples ```python from typing_extensions import TypedDict class Movie(TypedDict): name: str director: str def f(arg: object, arg2: type): isinstance(arg, Movie) # error: [isinstance-against-typed-dict] issubclass(arg2, Movie) # error: [isinstance-against-typed-dict] def g(arg: object): match arg: case Movie(): # error: [isinstance-against-typed-dict] pass ``` ## References - [Typing specification: `TypedDict`](https://typing.python.org/en/latest/spec/typeddict.html) # mismatched-type-name Default level: warn | Stable (since 0.0.30) ## What it does Checks for functional typing definitions whose declared name does not match the variable they are assigned to. ## Why is this bad? Constructors like `TypeVar`, `ParamSpec`, `NewType`, `NamedTuple`, `TypedDict`, and `TypeAliasType` all take a name argument that is normally expected to match the assigned variable. A mismatch is usually a typo and makes later diagnostics harder to understand. ## Default level This rule is a warning by default because ty can usually recover and continue understanding the resulting type. ## Examples ```python from typing import NewType, ParamSpec, TypeVar from typing_extensions import TypedDict T = TypeVar("U") # error: [mismatched-type-name] P = ParamSpec("Q") # error: [mismatched-type-name] UserId = NewType("Id", int) # error: [mismatched-type-name] Movie = TypedDict("Film", {"title": str}) # error: [mismatched-type-name] ``` # missing-argument Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for missing required arguments in a call. ## Why is this bad? Failing to provide a required argument will raise a `TypeError` at runtime. ## Examples ```python def func(x: int): ... func() # TypeError: func() missing 1 required positional argument: 'x' ``` # missing-override-decorator Default level: ignore | Preview (since 0.0.41) ## What it does Checks for methods that override a method or attribute in a superclass but are not decorated with `@override`. This rule is disabled by default. Enable it to opt in to strict `@override` enforcement for a project. ## Exemptions Overriding `__init__`, `__new__`, `__init_subclass__`, or `__post_init__` does not require `@override`, even if the method is explicitly declared by a superclass. ## Why is this bad? Without an `@override` annotation, refactors can silently change whether a method is an override. Requiring `@override` on every override lets ty report when an intended override stops overriding anything, and when a method unexpectedly starts overriding a superclass member. ## Example ```python from typing import override class Parent: def method(self) -> int: return 1 class Child(Parent): def method(self) -> int: # Error raised here when the rule is enabled return 2 class ExplicitChild(Parent): @override def method(self) -> int: # fine return 2 ``` # missing-type-argument Default level: ignore | Stable (since 0.0.45) ## What it does Checks for generic types used without type parameters in type expressions. ## Why is this bad? Using a generic type without specifying its type parameters results in the type parameters being implicitly filled with `Unknown`, reducing the precision of type checking. Explicit type parameters make the intended types clear and enable the type checker to catch more errors. ## Examples ```python import re def handle(m: re.Match) -> str: # error: [missing-type-argument] return m.string # Use explicit type parameters instead: def handle(m: re.Match[str]) -> str: return m.string ``` # missing-typed-dict-key Default level: error | Stable (since 0.0.1-alpha.20) ## What it does Detects missing required keys in `TypedDict` constructor calls. ## Why is this bad? `TypedDict` requires all non-optional keys to be provided during construction. Missing items can lead to a `KeyError` at runtime. ## Example ```python from typing import TypedDict class Person(TypedDict): name: str age: int alice: Person = {"name": "Alice"} # missing required key 'age' alice["age"] # KeyError ``` # no-matching-overload Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for calls to an overloaded function that do not match any of the overloads. ## Why is this bad? Failing to provide the correct arguments to one of the overloads will raise a `TypeError` at runtime. ## Examples ```python @overload def func(x: int): ... @overload def func(x: bool): ... func("string") # error: [no-matching-overload] ``` # non-callable-init-subclass Default level: error | Stable (since 0.0.30) ## What it does Checks for class definitions that will fail due to non-callable `__init_subclass__` methods. ## Why is this bad? If a class defines a non-callable `__init_subclass__` method/attribute, any attempt to subclass that class will raise a `TypeError` at runtime. ## Examples ```python class Super: __init_subclass__ = None class Sub(Super): ... # error: [non-callable-init-subclass] ``` ## References - [Python data model: Customizing class creation](https://docs.python.org/3/reference/datamodel.html#customizing-class-creation) # not-iterable Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for objects that are not iterable but are used in a context that requires them to be. ## Why is this bad? Iterating over an object that is not iterable will raise a `TypeError` at runtime. ## Examples ```python for i in 34: # TypeError: 'int' object is not iterable pass ``` # not-subscriptable Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for subscripting objects that do not support subscripting. ## Why is this bad? Subscripting an object that does not support it will raise a `TypeError` at runtime. ## Examples ```python 4[1] # TypeError: 'int' object is not subscriptable ``` # override-of-final-method Default level: error | Stable (since 0.0.1-alpha.29) ## What it does Checks for methods on subclasses that override superclass methods decorated with `@final`. ## Why is this bad? Decorating a method with `@final` declares to the type checker that it should not be overridden on any subclass. ## Example ```python from typing import final class A: @final def foo(self): ... class B(A): def foo(self): ... # Error raised here ``` # override-of-final-variable Default level: error | Stable (since 0.0.16) ## What it does Checks for class variables on subclasses that override a superclass variable that has been declared as `Final`. ## Why is this bad? Declaring a variable as `Final` indicates to the type checker that it should not be overridden on any subclass. ## Example ```python from typing import Final class A: X: Final[int] = 1 class B(A): X = 2 # Error raised here ``` # parameter-already-assigned Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for calls which provide more than one argument for a single parameter. ## Why is this bad? Providing multiple values for a single parameter will raise a `TypeError` at runtime. ## Examples ```python def f(x: int) -> int: ... f(1, x=2) # Error raised here ``` # positional-only-parameter-as-kwarg Default level: error | Stable (since 0.0.1-alpha.22) ## What it does Checks for keyword arguments in calls that match positional-only parameters of the callable. ## Why is this bad? Providing a positional-only parameter as a keyword argument will raise `TypeError` at runtime. ## Example ```python def f(x: int, /) -> int: ... f(x=1) # Error raised here ``` # possibly-missing-attribute Default level: ignore | Stable (since 0.0.1-alpha.22) ## What it does Checks for possibly missing attributes. ## Why is this bad? Attempting to access a missing attribute will raise an `AttributeError` at runtime. ## Rule status This rule is currently disabled by default because of the number of false positives it can produce. ## Examples ```python class A: if b: c = 0 A.c # AttributeError: type object 'A' has no attribute 'c' ``` # possibly-missing-implicit-call Default level: warn | Stable (since 0.0.1-alpha.22) ## What it does Checks for implicit calls to possibly missing methods. ## Why is this bad? Expressions such as `x[y]` and `x * y` call methods under the hood (`__getitem__` and `__mul__` respectively). Calling a missing method will raise an `AttributeError` at runtime. ## Examples ```python import datetime class A: if datetime.date.today().weekday() != 6: def __getitem__(self, v): ... A()[0] # TypeError: 'A' object is not subscriptable ``` # possibly-missing-import Default level: ignore | Stable (since 0.0.1-alpha.22) ## What it does Checks for imports of symbols that may be missing. ## Why is this bad? Importing a missing module or name will raise a `ModuleNotFoundError` or `ImportError` at runtime. ## Rule status This rule is currently disabled by default because of the number of false positives it can produce. ## Examples ```python # module.py import datetime if datetime.date.today().weekday() != 6: a = 1 # main.py from module import a # ImportError: cannot import name 'a' from 'module' ``` # possibly-missing-submodule Default level: warn | Stable (since 0.0.23) ## What it does Checks for accesses of submodules that might not've been imported. ## Why is this bad? When module `a` has a submodule `b`, `import a` isn't generally enough to let you access `a.b.` You either need to explicitly `import a.b`, or else you need the `__init__.py` file of `a` to include `from . import b`. Without one of those, `a.b` is an `AttributeError`. ## Examples ```python import html html.parser # AttributeError: module 'html' has no attribute 'parser' ``` # possibly-unresolved-reference Default level: ignore | Stable (since 0.0.1-alpha.1) ## What it does Checks for references to names that are possibly not defined. ## Why is this bad? Using an undefined variable will raise a `NameError` at runtime. ## Rule status This rule is currently disabled by default because of the number of false positives it can produce. ## Example ```python for i in range(0): x = i print(x) # NameError: name 'x' is not defined ``` # raw-string-type-annotation Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for raw-strings in type annotation positions. ## Why is this bad? Static analysis tools like ty can't analyze type annotations that use raw-string notation. ## Examples ```python def test(): -> r"int": ... ``` Use instead: ```python def test(): -> "int": ... ``` # redundant-cast Default level: warn | Stable (since 0.0.1-alpha.1) ## What it does Detects redundant `cast` calls where the value already has the target type. ## Why is this bad? These casts have no effect and can be removed. ## Example ```python def f() -> int: return 10 cast(int, f()) # Redundant ``` # redundant-final-classvar Default level: warn | Stable (since 0.0.18) ## What it does Checks for redundant combinations of the `ClassVar` and `Final` type qualifiers. ## Why is this bad? An attribute that is marked `Final` in a class body is implicitly a class variable. Marking it as `ClassVar` is therefore redundant. Note that this diagnostic is not emitted for dataclass fields, where `ClassVar[Final[int]]` has a distinct meaning from `Final[int]`. ## Examples ```python from typing import ClassVar, Final class C: x: ClassVar[Final[int]] = 1 # redundant y: Final[ClassVar[int]] = 1 # redundant ``` # shadowed-type-variable Default level: error | Stable (since 0.0.20) ## What it does Checks for type variables in nested generic classes or functions that shadow type variables from an enclosing scope. ## Why is this bad? Shadowing type variables makes the code confusing and is disallowed by the typing spec. ## Examples ```python class Outer[T]: # Error: `T` is already used by `Outer` class Inner[T]: ... # Error: `T` is already used by `Outer` def method[T](self, x: T) -> T: ... ``` ## References - [Typing spec: Generics](https://typing.python.org/en/latest/spec/generics.html#introduction) # static-assert-error Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Makes sure that the argument of `static_assert` is statically known to be true. ## Why is this bad? A `static_assert` call represents an explicit request from the user for the type checker to emit an error if the argument cannot be verified to evaluate to `True` in a boolean context. ## Examples ```python from ty_extensions import static_assert static_assert(1 + 1 == 3) # error: evaluates to `False` static_assert(int(2.0 * 3.0) == 6) # error: does not have a statically known truthiness ``` # subclass-of-dataclass-with-order Default level: warn | Stable (since 0.0.39) ## What it does Checks for classes that inherit from a dataclass with `order=True`. ## Why is this bad? When a dataclass has `order=True`, comparison methods (`__lt__`, `__le__`, `__gt__`, `__ge__`) are generated that compare instances as tuples of their fields. These methods raise a `TypeError` at runtime when comparing instances of different classes in the inheritance hierarchy, even if one is a subclass of the other. This violates the [Liskov Substitution Principle] because child class instances cannot be used in all contexts where parent class instances are expected. ## Example ```python from dataclasses import dataclass @dataclass(order=True) class Parent: value: int class Child(Parent): # Ty emits a warning here pass # At runtime, this raises TypeError: # Child(1) < Parent(2) ``` Consider using [`functools.total_ordering`][total_ordering] instead, which does not have this limitation. [Liskov Substitution Principle]: https://en.wikipedia.org/wiki/Liskov_substitution_principle [total_ordering]: https://docs.python.org/3/library/functools.html#functools.total_ordering # subclass-of-final-class Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for classes that subclass final classes. ## Why is this bad? Decorating a class with `@final` declares to the type checker that it should not be subclassed. ## Example ```python from typing import final @final class A: ... class B(A): ... # Error raised here ``` # super-call-in-named-tuple-method Default level: error | Stable (since 0.0.1-alpha.30) ## What it does Checks for calls to `super()` inside methods of `NamedTuple` classes. ## Why is this bad? Using `super()` in a method of a `NamedTuple` class will raise an exception at runtime. ## Examples ```python from typing import NamedTuple class F(NamedTuple): x: int def method(self): super() # error: super() is not supported in methods of NamedTuple classes ``` ## References - [Python documentation: super()](https://docs.python.org/3/library/functions.html#super) # too-many-positional-arguments Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for calls that pass more positional arguments than the callable can accept. ## Why is this bad? Passing too many positional arguments will raise `TypeError` at runtime. ## Example ```python def f(): ... f("foo") # Error raised here ``` # type-assertion-failure Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for `assert_type()` and `assert_never()` calls where the actual type is not the same as the asserted type. ## Why is this bad? `assert_type()` allows confirming the inferred type of a certain value. ## Example ```python def _(x: int): assert_type(x, int) # fine assert_type(x, str) # error: Actual type does not match asserted type ``` # unavailable-implicit-super-arguments Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Detects invalid `super()` calls where implicit arguments like the enclosing class or first method argument are unavailable. ## Why is this bad? When `super()` is used without arguments, Python tries to find two things: the nearest enclosing class and the first argument of the immediately enclosing function (typically self or cls). If either of these is missing, the call will fail at runtime with a `RuntimeError`. ## Examples ```python super() # error: no enclosing class or function found def func(): super() # error: no enclosing class or first argument exists class A: f = super() # error: no enclosing function to provide the first argument def method(self): def nested(): super() # error: first argument does not exist in this nested function lambda: super() # error: first argument does not exist in this lambda (super() for _ in range(10)) # error: argument is not available in generator expression super() # okay! both enclosing class and first argument are available ``` ## References - [Python documentation: super()](https://docs.python.org/3/library/functions.html#super) # unbound-type-variable Default level: error | Stable (since 0.0.20) ## What it does Checks for type variables that are used in a scope where they are not bound to any enclosing generic context. ## Why is this bad? Using a type variable outside of a scope that binds it has no well-defined meaning. ## Examples ```python from typing import TypeVar, Generic T = TypeVar("T") S = TypeVar("S") x: T # error: unbound type variable in module scope class C(Generic[T]): x: list[S] = [] # error: S is not in this class's generic context ``` ## References - [Typing spec: Scoping rules for type variables](https://typing.python.org/en/latest/spec/generics.html#scoping-rules-for-type-variables) # undefined-reveal Default level: warn | Stable (since 0.0.1-alpha.1) ## What it does Checks for calls to `reveal_type` without importing it. ## Why is this bad? Using `reveal_type` without importing it will raise a `NameError` at runtime. ## Examples ```python reveal_type(1) # NameError: name 'reveal_type' is not defined ``` # unknown-argument Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for keyword arguments in calls that don't match any parameter of the callable. ## Why is this bad? Providing an unknown keyword argument will raise `TypeError` at runtime. ## Example ```python def f(x: int) -> int: ... f(x=1, y=2) # Error raised here ``` # unresolved-attribute Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for unresolved attributes. ## Why is this bad? Accessing an unbound attribute will raise an `AttributeError` at runtime. An unresolved attribute is not guaranteed to exist from the type alone, so this could also indicate that the object is not of the type that the user expects. ## Examples ```python class A: ... A().foo # AttributeError: 'A' object has no attribute 'foo' ``` # unresolved-global Default level: warn | Stable (since 0.0.1-alpha.15) ## What it does Detects variables declared as `global` in an inner scope that have no explicit bindings or declarations in the global scope. ## Why is this bad? Function bodies with `global` statements can run in any order (or not at all), which makes it hard for static analysis tools to infer the types of globals without explicit definitions or declarations. ## Example ```python def f(): global x # unresolved global x = 42 def g(): print(x) # unresolved reference ``` Use instead: ```python x: int def f(): global x x = 42 def g(): print(x) ``` Or: ```python x: int | None = None def f(): global x x = 42 def g(): print(x) ``` # unresolved-import Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for import statements for which the module cannot be resolved. ## Why is this bad? Importing a module that cannot be resolved will raise a `ModuleNotFoundError` at runtime. ## Examples ```python import foo # ModuleNotFoundError: No module named 'foo' ``` # unresolved-reference Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for references to names that are not defined. ## Why is this bad? Using an undefined variable will raise a `NameError` at runtime. ## Example ```python print(x) # NameError: name 'x' is not defined ``` # unsupported-base Default level: warn | Stable (since 0.0.1-alpha.7) ## What it does Checks for class definitions that have bases which are unsupported by ty. ## Why is this bad? If a class has a base that is an instance of a complex type such as a union type, ty will not be able to resolve the [method resolution order] (MRO) for the class. This will lead to an inferior understanding of your codebase and unpredictable type-checking behavior. ## Examples ```python import datetime class A: ... class B: ... if datetime.date.today().weekday() != 6: C = A else: C = B class D(C): ... # error: [unsupported-base] ``` [method resolution order]: https://docs.python.org/3/glossary.html#term-method-resolution-order # unsupported-bool-conversion Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for bool conversions where the object doesn't correctly implement `__bool__`. ## Why is this bad? If an exception is raised when you attempt to evaluate the truthiness of an object, using the object in a boolean context will fail at runtime. ## Examples ```python class NotBoolable: __bool__ = None b1 = NotBoolable() b2 = NotBoolable() if b1: # exception raised here pass b1 and b2 # exception raised here not b1 # exception raised here b1 < b2 < b1 # exception raised here ``` # unsupported-dynamic-base Default level: ignore | Stable (since 0.0.12) ## What it does Checks for dynamic class definitions (using `type()`) that have bases which are unsupported by ty. This is equivalent to `unsupported-base` but applies to classes created via `type()` rather than `class` statements. ## Why is this bad? If a dynamically created class has a base that is an unsupported type such as `type[T]`, ty will not be able to resolve the [method resolution order] (MRO) for the class. This may lead to an inferior understanding of your codebase and unpredictable type-checking behavior. ## Default level This rule is disabled by default because it will not cause a runtime error, and may be noisy on codebases that use `type()` in highly dynamic ways. ## Examples ```python def factory(base: type[Base]) -> type: # `base` has type `type[Base]`, not `type[Base]` itself return type("Dynamic", (base,), {}) # error: [unsupported-dynamic-base] ``` [method resolution order]: https://docs.python.org/3/glossary.html#term-method-resolution-order # unsupported-operator Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for binary expressions, comparisons, and unary expressions where the operands don't support the operator. ## Why is this bad? Attempting to use an unsupported operator will raise a `TypeError` at runtime. ## Examples ```python class A: ... A() + A() # TypeError: unsupported operand type(s) for +: 'A' and 'A' ``` # unused-awaitable Default level: warn | Preview (since 0.0.21) ## What it does Checks for awaitable objects (such as coroutines) used as expression statements without being awaited. ## Why is this bad? Calling an `async def` function returns a coroutine object. If the coroutine is never awaited, the body of the async function will never execute, which is almost always a bug. Python emits a `RuntimeWarning: coroutine was never awaited` at runtime in this case. ## Examples ```python async def fetch_data() -> str: return "data" async def main() -> None: fetch_data() # Warning: coroutine is not awaited await fetch_data() # OK ``` # unused-ignore-comment Default level: warn | Stable (since 0.0.1-alpha.1) ## What it does Checks for `ty: ignore` directives that are no longer applicable. ## Why is this bad? A `ty: ignore` directive that no longer matches any diagnostic violations is likely included by mistake, and should be removed to avoid confusion. ## Examples ```py a = 20 / 2 # ty: ignore[division-by-zero] ``` Use instead: ```py a = 20 / 2 ``` ## Options Set [`analysis.respect-type-ignore-comments`](https://docs.astral.sh/ty/reference/configuration/#respect-type-ignore-comments) to `false` to prevent this rule from reporting unused `type: ignore` comments. # unused-type-ignore-comment Default level: warn | Stable (since 0.0.14) ## What it does Checks for `type: ignore` directives that are no longer applicable. ## Why is this bad? A `type: ignore` directive that no longer matches any diagnostic violations is likely included by mistake, and should be removed to avoid confusion. ## Examples ```py a = 20 / 2 # type: ignore ``` Use instead: ```py a = 20 / 2 ``` ## Options This rule is skipped if [`analysis.respect-type-ignore-comments`](https://docs.astral.sh/ty/reference/configuration/#respect-type-ignore-comments) to `false`. # useless-overload-body Default level: warn | Stable (since 0.0.1-alpha.22) ## What it does Checks for various `@overload`-decorated functions that have non-stub bodies. ## Why is this bad? Functions decorated with `@overload` are ignored at runtime; they are overridden by the implementation function that follows the series of overloads. While it is not illegal to provide a body for an `@overload`-decorated function, it may indicate a misunderstanding of how the `@overload` decorator works. ## Example ```py from typing import overload @overload def foo(x: int) -> int: return x + 1 # will never be executed @overload def foo(x: str) -> str: return "Oh no, got a string" # will never be executed def foo(x: int | str) -> int | str: raise Exception("unexpected type encountered") ``` Use instead: ```py from typing import assert_never, overload @overload def foo(x: int) -> int: ... @overload def foo(x: str) -> str: ... def foo(x: int | str) -> int | str: if isinstance(x, int): return x + 1 elif isinstance(x, str): return "Oh no, got a string" else: assert_never(x) ``` ## References - [Python documentation: `@overload`](https://docs.python.org/3/library/typing.html#typing.overload) # zero-stepsize-in-slice Default level: error | Stable (since 0.0.1-alpha.1) ## What it does Checks for step size 0 in slices. ## Why is this bad? A slice with a step size of zero will raise a `ValueError` at runtime. ## Examples ```python l = list(range(10)) l[1:10:0] # ValueError: slice step cannot be zero ``` test rule::rule_no_selector ... ok test rule::rule_default_output ... ok test python_environment::src_subdirectory_not_added_as_root_if_src_package_exists ... ok test rule::rule_unknown ... ok test file_selection::explicit_path_overrides_exclude_force_exclude ... ok test python_environment::many_search_paths ... ok test rule_selection::cli_all_rules_warn ... ok test rule_selection::cli_all_rules_precedence ... ok test rule_selection::all_overrides ... ok test python_environment::python_cli_argument_virtual_environment ... ok test rule_selection::configuration_all_rules ... ok test rule_selection::cli_all_rules_ignore ... ok test rule_selection::cli_specific_then_all ... ok test python_environment::python_argument_trapped_in_a_symlink_factory ... ok test python_environment::defaults_to_a_new_python_version ... ok test python_environment::pythonpath_multiple_dirs_is_respected ... ok test python_environment::pythonpath_is_respected ... ok test rule_selection::cli_unknown_rules ... ok test python_environment::python_version_inferred_from_system_installation ... ok test rule_selection::configuration_all_rules_with_rule_sorting_before_all ... ok test rule_selection::overrides_invalid_exclude_glob ... ok test rule_selection::overrides_invalid_include_glob ... ok test rule_selection::overrides_no_actual_overrides ... ok test rule_selection::configuration_unknown_rules ... ok test test_include_hidden_files_by_default ... ok test rule_selection::overrides_all_rules_with_rule_sorting_before_all ... ok test rule_selection::overrides_precedence ... ok test rule_selection::overrides_unknown_rules ... ok test test_run_in_sub_directory ... ok test rule_selection::overrides_basic ... ok test rule_selection::overrides_exclude ... ok test rule_selection::cli_rule_severity_precedence ... ok test rule_selection::overrides_empty_include ... ok test rule_selection::cli_rule_severity ... ok test rule_selection::overrides_inherit_global ... ok test rule_selection::overrides_missing_include_exclude ... ok test test_output_format_env ... ok test rule_selection::configuration_rule_severity ... ok test python_environment::ty_environment_is_only_environment ... FAILED test python_environment::ty_environment_and_active_environment ... ok test python_environment::ty_environment_and_discovered_venv ... ok test test_respect_ignore_files ... ok test user_configuration ... ok test python_environment::ty_system_environment_and_local_venv ... ok test python_environment::check_venv_resolution_with_working_venv ... ok test python_environment::check_venv_resolution_without_working_venv ... ok test test_quiet_output ... ok failures: ---- python_environment::ty_environment_is_only_environment stdout ---- thread 'python_environment::ty_environment_is_only_environment' (23892) panicked at /build/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/insta-cmd-0.6.0/src/spawn.rs:103:27: called `Result::unwrap()` on an `Err` value: Os { code: 26, kind: ExecutableFileBusy, message: "Text file busy" } note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace failures: python_environment::ty_environment_is_only_environment test result: FAILED. 126 passed; 1 failed; 0 ignored; 0 measured; 1 filtered out; finished in 1.51s error: test failed, to rerun pass `--test cli` ==> ERROR: A failure occurred in check(). Aborting... ==> ERROR: Build failed, check /home/alhp/workspace/chroot/build_96120eae-5adc-4377-91c9-9bfde1e2c497/build