diff options
| author | blasty <peter@haxx.in> | 2026-08-14 00:26:27 +0200 |
|---|---|---|
| committer | blasty <peter@haxx.in> | 2026-08-14 00:26:27 +0200 |
| commit | 43874ce87c86d69de1a0f1f770908e35189ec0e8 (patch) | |
| tree | 1667c8260ab6193b92daead2ff1661186aec6193 /uv.lock | |
| parent | Port to the ida-codemode 0.5.3+ public API (diff) | |
| download | ida-tui-43874ce87c86d69de1a0f1f770908e35189ec0e8.tar.gz ida-tui-43874ce87c86d69de1a0f1f770908e35189ec0e8.tar.xz ida-tui-43874ce87c86d69de1a0f1f770908e35189ec0e8.zip | |
Re-check the upstream findings report against 0.6.1
Items 4, 8 and 9 are fixed (loader switches on reopen, package exports,
py.typed), so the report and the skill no longer claim 4-9 are all open. Item 7
is partial: DatabaseManager grew a DatabaseEventCallback, but there is still
nothing an external caching client can observe, which was the point. 5 and 6
are untouched.
The "are these files byte-identical" re-check recipe is removed: it named
client.py/registry.py/resolver.py, which 0.5.x renamed, so it would have
reported "unchanged" forever. The replacement is a diff of __all__ and the
DatabaseOpenOptions fields, both of which the contract suite now asserts
whenever the library is importable.
Also records two things that cost time here: the loader-switch strip needs
input_path != source, so an .i64 passed directly alongside load options still
fatals; and an editable checkout does not enforce its own dependency floors, so
a `git pull` to 0.6.1 leaves ida-domain/zeromcp silently too old.
Diffstat (limited to 'uv.lock')
0 files changed, 0 insertions, 0 deletions
