* docs: 6.0.0 changelog, README, FAQ and contributor docs
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* Release prep: version 6.0.0
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(ci): keep the leaked test pools reachable for LSan; skip the tiny-file floor under coverage
- ava1-ctest diag/mgmt_fs: the &'static Pool each test leaks for
AvaTransport::with_pool is now held in a static list, so LeakSanitizer sees
it (and the sessions on its threads) as reachable instead of reporting
~140 KB of indirect leaks the frame-name suppression could never match.
Verified under clang ASan+LSan in Linux Docker: diag 13/13, mgmt_fs 40/40.
- download.rs tiny-file throughput floor is skipped when cargo-llvm-cov runs
(CARGO_LLVM_COV set): instrumentation slows every call several times over.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(test): data_rust servers use the clients' fast timing
Five folder-host tests gave the client fast timing (dead after 500 ms) but
left the server on the default (ping every 2 s). On a slow runner a half-second
gap made the client drop healthy lanes and the job stalled until the 36 s
progress limit (both CI runs on #374/#377). The ordered-download tests already
set both ends; these now do too. The app uses one timing on both ends.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(test): the C lane socket-buffer test accepts Linux's wmem_max cap
Same cap as the Rust lane test: Linux CI gives the send side 416 KiB, so the
1 MiB floor failed under ASan in CI. 128 KiB is still far above a default.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(ci): gcc unused-result in the FTP selftest, serial ctest in make test, sender state on failure
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(ava1): flush a partial bundle after any reader message, not only a record
The last small-file record could arrive while a large file's chunk or root
was still queued behind it: the flush saw a non-empty channel, the next
message was not a record, and the records sat unsent until the receiver
cut the job as stalled (CI-only flake; 7/36 under local parallel load, 0/48 after).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(validate): run the C interop tests serially in make ci too
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(ava1): a resumed file goes in one-group pieces so a flapping link still makes progress
With kills every 2 s, the 4 MiB tail piece was cut before it was durable on every
attempt and the upload retried the same 28 MiB mark until it timed out (1 in 3
locally, CI coverage). Resumed files now send 1 MiB pieces: 5/5 in ~6 s.
Also: make docker-engine uses the repo root as context (as CI); governor
classification asserts are skipped under the sanitizers, where the C is the bottleneck.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(test): single-instance gate tests hold the C-server lock; relay test cap leaves margin
Coverage runs the C tests in parallel; the two gate tests stop the one global C server.
The relay order test's 4 MiB/s cap finished in 5.9 s on CI against its >6 s precondition.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(test): periodic-kill bound widened under coverage; tiny-file floor relaxed on CI runners
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(test): lane-kill test kills until a resend; periodic-kill liveness race skipped under coverage
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(test): a hung relay fails its test at the bound instead of hanging the CI job
The dest-ends relay test ran the relay under spawn_blocking: on a hang the timeout
panicked but the runtime then waited forever for the blocking thread (27 min on CI).
It now runs on a plain thread. The engine test steps get a 25-minute bound.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(test): dest-ends relay test in its own binary on small files; relay logs its silent retries
The test hung a CI job twice inside the shared relay binary (behind the 384 MiB relays'
lock) and never reproduced locally or in Linux Docker. It now runs alone, on 4x32 MiB
(still twice the relay buffer), ~3 s. The relay's open-dropped and retry paths now say
so on stderr instead of looping silently. Governor classification asserts also skip
under coverage, where the instrumented sender is the bottleneck.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(test): the partly-durable relay test caps its first attempt so it can be interrupted
On a fast runner the uncapped relay finished all 160 MiB before the first durable
report was observed. The first attempt now reads A through a 32 MiB/s proxy (~5 s);
the resume runs uncapped.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* feat: one-time 6.0 upgrade clean-up that keeps every setting
Host (engine, once per data dir): pre-5.x files no 5.41/6.0 code reads (api_token,
ps5upload.ini, ps5upload_profiles.ini/.json, app-config.json) move to ~/.ps5upload/legacy-5x/.
App (desktop, once): the 1.x/2.x config.json/profiles.json move to legacy-5x/; the cached
ezremote-dpi.elf nothing loads is deleted. Client: the retired upload-streams key is dropped.
Console (once per console, on its first 6.0 helper answer): the FTX2 /data/ps5upload/tx and
/spool folders are deleted; a failure retries later. The health check no longer lists those
folders (its fix would have recreated them). Nothing current is moved or reset.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(test): the download periodic-kill race is skipped under coverage, like its upload twin
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(test): the tiny-zip floor only catches a stall on CI runners
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(test): 'other calls still answer during launches' is a state check, not a wall-clock bound
Both mgmt_t6 tests asserted a sub-300 ms answer while a slow Sony call ran; on a loaded
runner that separates nothing. They now assert the answer arrived while the slow call
was still in flight.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
* fix(ci): reword the 6.0 migration comments for check-no-ftx2
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XR8fQMhp7Rdgq2e4U9oDff
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix: installs the PS5 declined, Docker images that work, Payload Manager as a backup loader (5.41.0)
Installs
- A package the console serves itself (Upload & install, USB, the phone app)
is refused on FW 13.60 with 0x80B2116F (Sony's DbgGetPatchInfo/DbgCancelPatch
path, especially over an installed app). The unified install now re-serves
the console's copy from the engine (ps5:// read back through the helper) and
a refused link through the engine's link proxy. HW-verified on a 13.60 Pro:
stream, Upload & install fresh and over an installed app, USB.
- Installer 1.2.0: fixed past Last-Modified, logs to /data/ps5upload/installer.log.
- NET_REACH (frame 148/149): the console checks it can reach the engine before
a stream install and names a firewall/isolation cause in seconds.
- Staged-route refusals get their own reason and message (staged_refused).
- Folder-game register on 13.x: sceAppInstUtilAppInstallAll fallback,
/system_ex rw remount on EROFS, repeated uninstall for its two records.
- Removed the incorrect "no fake packages above FW 11.60" warnings.
Loaders
- itsPLK Payload Manager (:8084) fallback: starts the installer, recovers a
wedged elfldr (HW-verified) and puts the helper back when :9021 is dead.
Only ever uses its own ps5upload-* folders.
- Setup wizard skips payloads already running; "Send only ps5upload".
Engine / self-hosting
- Engine clients ignore proxy env vars; errors carry the real cause.
- Docker: writable /tmp and /data (also under a user: override), HEALTHCHECK
via --healthcheck, PS5UPLOAD_ALLOW_IP takes CIDR ranges, actionable 403,
bridge-network warning, engine/compose.yaml, scripts/docker-smoke.sh run in
the PR gate and before every release push.
- Desktop app with a remote engine browses the engine's disk; From this device
uploads first. Android engine listens on the LAN so the phone can stream.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test: accept Windows' timeout as the probe's underlying cause
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* style: rustfmt the probe test
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* chore(android): run-android foregrounds and reuses the emulator; faster emulator
- ensure reuses a running or still-booting emulator instead of booting a
second; run-android brings its window to the front and reopens a headless
one with a window; run-android-background leaves it headless.
- A stopped emulator is waited on until it has really exited (forced after
60s), so a restart no longer mistakes it for one that is booting.
- Windowed emulators render on the host GPU instead of software, with 4 GB
RAM and up to 6 cores.
- Android dev serves Vite on 1430/1431 (PS5UPLOAD_VITE_PORT), so it can run
alongside desktop dev on 1420.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(android): software rendering by default; host GPU is opt-in
-gpu host froze the Android 16 image within minutes on an M1 Max (the
emulator warns its guest GL layer is unstable above API 35), with or
without Guest ANGLE. PS5UPLOAD_EMU_GPU=host opts back in.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(docker): the web UI image bundles the FAQ and Changelog
Since the FAQ and Changelog screens bundle ../FAQ.md and ../CHANGELOG.md,
the web UI image's frontend stage failed: it built the client at /src
and .dockerignore excluded every *.md. The stage now keeps the repo
layout (/repo/client) and copies the two files in.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(scripts): the audit counts a script's node:test file as used
scripts:check runs every *.test.mjs by pattern, so the test beside
stale-client-lib.mjs is named nowhere and the strict audit called it an
orphan (repo scripts failed on all three OSes).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
kill-stale-client did `pkill -f ps5upload-engine`, which SIGTERMed
every engine on the machine — a standalone one on another port died 70
minutes into a package build. It now stops only an engine listening on
19113 (an engine whose app is gone exits by itself). The decision is a
small pure module with node:test cases, which scripts:check now runs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
release-posts.js
- Reads whole changelog groups (bold heading + wrapped bullets), not just
the first line of each bullet.
- X: link counted as 23 chars, replies packed to fit 280, markdown stripped.
- Discord: full bullets when they fit 2000 chars, short ones otherwise;
Reddit: real markdown sections instead of a code block.
- Says "pre-release" when GitHub does (gh), --prerelease/--stable to
override; --only and --out to pick a platform and write files.
- make release-post calls it directly; the .sh wrapper is gone.
Removed (outdated)
- ps5-install-trace.py, ps5-install-watch.py, fpkg-mount-test.py: drove
/api/pkg/install/start and the dpi-* routes, which no longer exist.
- gather-fakelibs.py: superseded by the app's Backport scan.
- pull_ps5_debug.py: pulled a debug dir the helper no longer writes to.
hw-test-loop.sh ran cargo from the repo root (no workspace there); it now
points at engine/Cargo.toml.
README: a Highlights section up top (unified install, Convert to FPKG,
sleep and wake), Android/web in the platforms badge, tested firmware 5.10 &
9.60.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
