It completes frequencies given without a band and has to fit the taken station's bands, so it belongs to the station and not to the operator.
Written-by: Claude Fable 5.2
Stage 2 is implemented and manually checked. What was worth keeping is in the commit messages, the spec and docs/PROJECT_CONTEXT.md.
Written-by: Claude Fable 5.2
The manual named too few conditions for Finish, and spec and project context read as if a skipped page of a new station were not written. It is: only a station left unchanged is written page by page.
Written-by: Claude Fable 5.2
On a station left unchanged the summary read the log page's answers, which cannot express a DX cluster server or a frequency source running without a log source; it said no while Save left both on. The summary now shows the stored switches until the log page is part of the run. Ports, names, host and identifiers are reloaded on a source change, like the antenna values.
Written-by: Claude Fable 5.2
setStn_pstRotatorPort stores 1..65534 and replaces anything else by 12000, so the wizard must not accept 65535. And antenna values typed for a new station stayed in the summary after the operator chose to keep the station, where they are not written.
Written-by: Claude Fable 5.2
Stage 1 is implemented and manually checked. What was worth keeping is in the commit messages, the spec and docs/PROJECT_CONTEXT.md.
Written-by: Claude Fable 5.2
rerunSetupWizard set the one-shot request before it tried to obtain the switch, and cleared it when the switch was refused. A second confirmed call during the first one's window teardown therefore removed the first call's request: the session ended and the profile restarted without the wizard. The request is now set only by the call that owns the switch.
Written-by: Claude Fable 5.2
Finish now requires every mandatory answer, since a summary without locator, band and category could not be saved. Adds an optional step for antenna and power values that feed the path analysis.
Written-by: Claude Fable 5.2
Describes a first-start assistant for unconfigured operator profiles: what it asks, how it covers multi-operator and multi-station setups, and why it writes preferences.xml before the runtime is built instead of going through the settings draft.
Written-by: Claude Fable 5.2
Written-by: Codex (GPT-6.2 Sol)
Written-by: Gemini 4 Hydrogen (Antigravity)
Written-by: DeepSeek V4 Pro
Apply beacon checkbox changes at runtime and keep the aggregate status chip synchronized.
Improve explicit station-map navigation, spatial filter overlays, overlay legend, selected-path contrast, and the documented map screenshot.
* test: print all threads when a test times out
The rare CI hang in SelectedStationMessageUiVisualRenderingTest blocks on a
monitor in SnapshotStateObserver.observeReads (line 643 is the monitorenter
of observedScopeMapsLock in Compose 1.8.2). The timed-out thread's stack
shows where it waits but not which thread holds the lock. With the thread
dump enabled, JUnit prints every thread to the test's standard output, which
ends up in the XML report of the test-results artifact.
Claude-Session: https://claude.ai/code/session_01FJBfPYm6rCH4zD6T7bcC7Y
* test: render every ImageComposeScene on the AWT event thread
The rare CI hang is a lock-order deadlock in Compose Multiplatform 1.8.2,
shown by the thread dump of run 40299943329:
- the test thread renders the scene and holds the FlushCoroutineDispatcher
runLock while LazyListState.scrollToItem measures and wants the
SnapshotStateObserver's observedScopeMapsLock;
- the AWT event thread sends the global snapshot notifications and holds
observedScopeMapsLock in drainChanges while a re-read derived state wakes
the scene's snapshotFlow collector, whose dispatch wants runLock.
The application renders on the event thread, where both monitors are simply
re-entered. The tests now do the same: onEventThread builds, renders and
closes each scene there and rethrows what the block throws.
Claude-Session: https://claude.ai/code/session_01FJBfPYm6rCH4zD6T7bcC7Y
Strip HTML tags and XML comments until the text no longer changes, so that
nested input cannot reassemble a tag or comment after a single pass
(js/incomplete-multi-character-sanitization in website/.eleventy.js and
website/scripts/validate-version-info.js).
Limit the GITHUB_TOKEN of the PR compile check and the test version-XML
workflow to read access (actions/missing-workflow-permissions).
Claude-Session: https://claude.ai/code/session_01FJBfPYm6rCH4zD6T7bcC7Y
The kst4contest and kst4contest-git packages built jpackage's launcher
with Arch's openjdk, which links libapplauncher.so against the shared
libstdc++. That build aborts now and then on exit with "pure virtual
method called" in a static destructor (SIGABRT, core dump), the failure
Debian describes for non-static libstdc++ builds. Temurin links
libstdc++ statically, like the CI-built packages.
Both PKGBUILDs now fetch a pinned Temurin 21.0.13+9 through
source_x86_64, so aur-publish.yml's rewrite of the sha256sums= line
leaves it alone, and point the Gradle toolchain at it alone.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Nightly #303 named the hanging test, SelectedStationMessageUiVisual-
RenderingTest at scene.render(), but the short exception format showed
only that line, not the call that blocked below it. The job timeout
cancels the run, and the test reports were kept only on failure().
Failed tests now print their full stack, causes included, and the
reports are uploaded on cancelled() as well.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Nightly #302 and the PR check for #147 hung in :app-desktop:test for
over an hour, and the log named only the task. Thirteen reruns of the
same commit passed, so the hang is rare and still unidentified.
Every test now gets a two-minute JUnit timeout in a separate thread, so
even an uninterruptible hang fails with the test's name and the stack
where it stood. The test jobs are capped at 20 minutes for a hang
outside any test.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>