panic with %<number> is fixed

[kareigu]

Hi,

Unsure if this belongs here or should be reported at the erlang repo.
Running pylyzer on a python script I'm working on always panics during the checking phase.

Log for running standalone:

thread 'pylyzer' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/erg_compiler-0.6.27/ty/mod.rs:3665:13:
%84 is fixed
stack backtrace:
   0: rust_begin_unwind
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/std/src/panicking.rs:597:5
   1: core::panicking::panic_fmt
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/panicking.rs:72:14
   2: erg_compiler::ty::Type::destructive_link
   3: erg_compiler::context::unify::Unifier<L>::sub_unify
   4: erg_compiler::context::register::<impl erg_compiler::context::Context>::assign_subr
   5: erg_compiler::lower::GenericASTLowerer<A>::lower_subr_block
   6: erg_compiler::lower::GenericASTLowerer<A>::lower_def
   7: erg_compiler::lower::GenericASTLowerer<A>::lower_chunk
   8: erg_compiler::lower::GenericASTLowerer<A>::lower
   9: erg_compiler::build_hir::GenericHIRBuilder<ASTBuilder>::check
  10: erg_compiler::build_package::GenericPackageBuilder<ASTBuilder,HIRBuilder>::build_root
  11: pylyzer::analyze::PythonAnalyzer::analyze
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Thread panicked: Any { .. }

Log when run inside neovim:

[START][2023-12-20 10:26:10] LSP logging initiated
[ERROR][2023-12-20 10:26:10] .../vim/lsp/rpc.lua:31 "rpc"   "/home/<username>/.local/bin/pylyzer"   "stderr"    "thread 'pylyzer' panicked at "
[ERROR][2023-12-20 10:26:10] .../vim/lsp/rpc.lua:31 "rpc"   "/home/<username>/.local/bin/pylyzer"   "stderr"    "/root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/erg_compiler-0.6.27/ty/mod.rs:3665:13:\n%172 is fixed\nstack backtrace:\n"
[ERROR][2023-12-20 10:26:10] .../vim/lsp/rpc.lua:31 "rpc"   "/home/<username>/.local/bin/pylyzer"   "stderr"    "   0: rust_begin_unwind\n             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/std/src/panicking.rs:597:5\n   1: core::panicking::panic_fmt\n             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/panicking.rs:72:14\n   2: erg_compiler::ty::Type::destructive_link\n   3: erg_compiler::context::unify::Unifier<L>::sub_unify\n   4: erg_compiler::context::register::<impl erg_compiler::context::Context>::assign_subr\n   5: erg_compiler::lower::GenericASTLowerer<A>::lower_subr_block\n   6: erg_compiler::lower::GenericASTLowerer<A>::lower_def\n   7: erg_compiler::lower::GenericASTLowerer<A>::lower_chunk\n   8: erg_compiler::lower::GenericASTLowerer<A>::lower\n   9: erg_compiler::build_hir::GenericHIRBuilder<ASTBuilder>::check\n  10: erg_compiler::build_package::GenericPackageBuilder<ASTBuilder,HIRBuilder>::build_root\n  11: pylyzer::analyze::PythonAnalyzer::analyze\n  12: els::diagnostics::<impl els::server::Server<Checker,Parser>>::check_file\n  13: els::server::Server<Checker,Parser>::run\nnote: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.\n"
[ERROR][2023-12-20 10:26:10] .../vim/lsp/rpc.lua:31 "rpc"   "/home/<username>/.local/bin/pylyzer"   "stderr"    "Thread panicked: Any { .. }\n"

Under neovim I've seen a few different numbers being reported in the panic message, running standalone always gives the same number.

Thank you for your time.