catarrh
9411fd775d
The decoded view is the client-side EF decoder's table over the raw read's bytes. The collapsed "pySim JSON (server)" block was an unrelated second decode - opening it ran another /api/read with mode 'decoded' (pySim's read_binary_decoded/read_records_decoded on the card) - and it existed only when our decoder covered the file, so it could not serve as a cross-check where one would matter. /api/read keeps mode 'decoded' for API callers. Help, READMEs and the project notes now state the table is built in the browser from the same raw bytes; ef_decode.test.js pins the view's output and that no mode 'decoded' read remains in the PWA. 1016 Python + 955 frontend green; simple-v465.
142 lines
6.8 KiB
Markdown
142 lines
6.8 KiB
Markdown
# Changelog
|
||
|
||
All notable changes to SIMple (the PWA and `pysim-simple-server`).
|
||
The format follows [Keep a Changelog](https://keepachangelog.com/);
|
||
versions use `MAJOR.MINOR.PATCH` (see the README).
|
||
|
||
History before the first packaged release (v3.31.1) lives in the git log —
|
||
every change carries a descriptive commit message.
|
||
|
||
## [Unreleased]
|
||
|
||
## [3.32.7] — 2026-10-23
|
||
|
||
### Removed
|
||
|
||
- The file manager's decoded view no longer carries the collapsed **pySim JSON
|
||
(server)** disclosure — the view is the client-side EF decoder's table only. The
|
||
disclosure was an unrelated *second* decode: opening it issued another `/api/read` with
|
||
`mode: 'decoded'` to run pySim's `read_binary_decoded`/`read_records_decoded`, and it
|
||
was reachable only when our decoder covered the file (`Read decoded` is decoder-gated),
|
||
so the one case where a second opinion would matter — a file our decoders do not
|
||
cover — never offered it. `/api/read` keeps `mode: 'decoded'` for API callers; the
|
||
help, READMEs and project notes now say the decoded table is built in the browser from
|
||
the same raw bytes. `ef_decode.test.js` pins the view's output and the absence of the
|
||
lookup.
|
||
|
||
## [3.32.6] — 2026-10-23
|
||
|
||
### Fixed
|
||
|
||
- The empty amber **preset-mismatch banner** no longer flashes on the SCP80/RAM view.
|
||
`ramOpChanged()` (v3.28.0) un-hid `#ram-preset-warning` by the operation kind, but the
|
||
banner's text *and* visibility belong to `spPresetWarningRender()` (which also handles
|
||
the batch suppression): with no warning text the empty bordered box stayed visible until
|
||
the next status poll re-hid it — on every RAM view and operation switch. The visibility
|
||
is content-driven again; `frontend/tests/ram.test.js` pins it (the pre-fix code fails
|
||
the test).
|
||
|
||
## [3.32.5] — 2026-10-21
|
||
|
||
### Fixed
|
||
|
||
- A card removed during the **startup initialization** no longer leaves the server
|
||
reporting a phantom equipped card. The init caught the PC/SC error (and printed a
|
||
traceback) but kept the card object it had already built, so `card_present` and
|
||
`_CARD_CONNECTED` stayed True — and the auto-equip then skipped every later insertion
|
||
(its `_CARD_CONNECTED` early return), leaving only a manual Equip or a restart. A
|
||
PC/SC error now prints one line (`INIT: card removed during initialization …`), drops
|
||
the half-initialized session and lets the presence monitor equip the next card.
|
||
|
||
## [3.32.4] — 2026-10-21
|
||
|
||
### Fixed
|
||
|
||
- The auto-equip's captured traceback now always includes the **exception line**: cmd2
|
||
renders a rich-box traceback longer than the logged head, so the actual error was cut
|
||
off. The tail is appended after a `...` marker; the "releasing the old link failed"
|
||
message now says it continues with a fresh link (a removed card's dead PC/SC handle
|
||
always fails to disconnect).
|
||
- A card insertion now marks the PC/SC link for a rebuild, so the **first** auto-equip
|
||
attempt already uses a fresh link. On Windows the old link cannot connect after a
|
||
swap — v3.32.2 recovered it, but only on the second attempt, after a failed init, a
|
||
2–4 s delay and a traceback in the log. A link created at a cardless startup has
|
||
never connected either, which the same mark covers. The rebuild still runs in the
|
||
equip worker (never in the pyscard monitor thread) and `_ensure_transport` releases
|
||
the old link first.
|
||
|
||
## [3.32.2] — 2026-10-21
|
||
|
||
### Fixed
|
||
|
||
- **The auto-equip loop after a card swap on Windows.** A failed initialization with
|
||
the card still present was reported as "card gone during initialization" and treated
|
||
as a no-op success — so the three retries never ran and the watchdog re-armed every
|
||
few seconds forever. It is a failure now, and **every failed attempt marks the
|
||
PC/SC transport for a rebuild**, so the retry starts from a fresh link (the release
|
||
of the old link happens first, so it cannot inherit a stale card handle). The error
|
||
pySim swallowed is printed as `AUTO-EQUIP: init output:` with its traceback.
|
||
|
||
## [3.32.1] — 2026-10-21
|
||
|
||
### Added
|
||
|
||
- **"Start counter value"** in the outfile import: the counter every created keyset
|
||
starts from. It defaults to the store's value (`1`); raise it for cards whose
|
||
counters are already past it. The API takes `start_counter` (1–10 hex digits;
|
||
a bad value is a 400), and the preview carries the value.
|
||
|
||
## [3.32.0] — 2026-10-21
|
||
|
||
### Added
|
||
|
||
- **Updating a packaged install** — `update.sh` / `update.bat` (and `tools/update.py`
|
||
beneath them): downloads the latest release package, replaces the application files
|
||
in place and re-installs the app into the **existing `.venv`**. pysim and its
|
||
prerequisites (the slow part: pyscard builds from source on Linux) are kept, so an
|
||
update takes seconds. `--check` reports the current and latest versions, `--version`
|
||
picks a specific release, `--zip` updates from a local package (offline), `--no-pip`
|
||
refreshes the files only, `--force` re-applies the same version.
|
||
- The release workflow now takes the release notes from this file's matching version
|
||
section (falling back to generated notes when it is missing).
|
||
|
||
### Changed
|
||
|
||
- Installs made from the v3.31.x packages have no updater yet: copy `update.sh`,
|
||
`update.bat` and `tools/update.py` from this package once (or re-run `setup` from it).
|
||
Later updates use `update.sh` / `update.bat` — or `git pull` for a clone.
|
||
|
||
## [3.31.2] — 2026-10-20
|
||
|
||
### Changed
|
||
|
||
- The **SCP81 TLS-PSK listener states its Python requirement**: it needs Python 3.13+
|
||
(`ssl`'s PSK callbacks exist only since 3.13). Below that it raises a clear error
|
||
instead of `AttributeError`, and the PSK tests are skipped (they run on 3.13+).
|
||
- The READMEs and the setup scripts: **Windows strongly recommends Python 3.13**
|
||
(pyscard has wheels up to 3.13; on 3.14 pyscard and some pysim dependency wheels are
|
||
unavailable and build from source with MSVC).
|
||
|
||
## [3.31.1] — 2026-10-20
|
||
|
||
The first packaged release (`simple-3.31.1.zip`).
|
||
|
||
### Added
|
||
|
||
- **EF_PBR (phonebook reference) support** — the PBR is decoded in the decoded file
|
||
views (the `A8`/`A9`/`AA` containers, the `C0`–`CC` kinds, the master EF), and the
|
||
phonebook files it references (they are not in pySim's model) are added to the file
|
||
tree server-side, selectable and readable.
|
||
- **In-app dialogs** — the native alert/confirm/prompt dialogs are replaced by a shared
|
||
modal (queued, keyboard-aware, focus-trapped, ARIA-labelled).
|
||
- **Windows console encoding guard** — the `start.bat` PowerShell pipe can no longer
|
||
kill the server on a character the ANSI code page lacks.
|
||
- **GPL-2.0-or-later licensing** (`LICENSE`, `THIRD-PARTY-NOTICES`), matching pysim.
|
||
- The curated **release package** (`tools/build_release.py`) and the tag-triggered
|
||
`.github/workflows/release.yml`.
|
||
|
||
### Changed
|
||
|
||
- `setup.sh` / `setup.bat` and the READMEs: on Linux `pyscard` builds from source and
|
||
needs the PC/SC headers (`libpcsclite-dev`).
|