Commit Graph
7 Commits
Author SHA1 Message Date
phantomptrandClaude Opus 5.5 7199b2fae2 Remove unused repo files and stale FTX2 doc notes
Deletes tests/install-fallback-hw.mjs, the mobile audit probe and its allowlist,
scripts/requirements.txt, tests/lab/verify-pending.sh, bench/baselines/ and client/icons/
(nothing references them; the bundle icons live in client/src-tauri/icons). audit-scripts
lists fpkg-diff.py as a manual research tool and no longer counts a script naming itself as
a reference. SPEC.md no longer says zip/7z/RAR sources fall back to FTX2.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ub1mez9eaVtTF8pMEFXvA9
2026-10-10 06:24:09 -07:00
PhantomPtrandClaude Opus 5.5 9a6b5571a7 6.6.0: Bug report wizard, event timeline, multi-console fixes, faster builds
- Bug report wizard (4 steps, time range, GitHub/Discord/zip), redacted on both sides.
- Engine event journal + app journal merged into one timeline; helper stderr mirrored from each PS5.
- Results that finish after a console switch land on the console they started on.
- Faster local gate and CI (nextest, parallel lanes, sharded C interop/ASan, cache restore/save).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ub1mez9eaVtTF8pMEFXvA9
2026-10-08 23:31:25 -07:00
phantomptr 90c1a0f058 6.2.2: fan, install, convert and connection fixes 2026-10-06 23:43:06 -07:00
e62e0c4d30 6.2.0: games launch again, installs stop giving up early (#398)
* chore(deps): Bump rustls from 0.23.43 to 0.23.45 in /client/src-tauri

Bumps [rustls](https://github.com/rustls/rustls) from 0.23.43 to 0.23.45.
- [Release notes](https://github.com/rustls/rustls/releases)
- [Changelog](https://github.com/rustls/rustls/blob/main/CHANGELOG.md)
- [Commits](https://github.com/rustls/rustls/compare/v/0.23.43...v/0.23.45)

---
updated-dependencies:
- dependency-name: rustls
  dependency-version: 0.23.45
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

* Install: drop the staged-refusal retry guard and the stream reach pre-check

After the PS5 refused a package from its own storage (0x80b2116f), the app
would no longer run Install on that row again and blocked Retry with Stream
unless the engine had offered it. Install and Retry with Stream now always
go out.

The engine no longer probes whether the console can reach it before handing
over a stream URL. A console that never fetches still gets the firewall /
PS5UPLOAD_PKG_HOST_IP explanation from the post-failure path.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Vq9BzVoith72tgD87LGG2z

* Helper: everything written on the console is 0777

Since 6.0 an upload kept the computer's file modes, so a game folder sent
from Windows landed as 0644 files. The PS5's app loader refuses game files
without world-execute, so those games would not launch until the user ran
chmod 777 by hand. The 5.x helper forced 0777 for this reason.

Uploads, on-console copies and the file manager's writes and new folders
now land as 0777. fs_chmod still sets exactly the mode it is given.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Vq9BzVoith72tgD87LGG2z

* Fix launch refusals, folder permissions, abandoned upload space and overestimated free space

- A launch refused with 0x80940033 now says whether kstuff is missing; with kstuff running,
  a folder game is made 0777 and launched again. Folder games get a Fix permissions button.
- The helper's own ps5upload folders are 0777, and older ones are opened up on start.
- The helper's job cleanup also deletes the half-written copy of an abandoned upload.
- An upload that runs out of room part-way teaches the engine how much of that drive the
  console never allocates; later space checks and Volumes' safe figure leave it out.
- Queue rows that failed because the PS5 could not reach this computer offer the
  Windows firewall fix; FAQ lists the ports and the 0x80B2116F firmwares.
- lf_slots_wedge: a bound that a healthy ASan run fits.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Vq9BzVoith72tgD87LGG2z

* 6.2.0: games launch again, installs stop giving up early

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Vq9BzVoith72tgD87LGG2z

* i18n: add the launch-refusal and fix-permissions strings to en, allowlist them for other locales

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Vq9BzVoith72tgD87LGG2z

* ava1: a finished job counts the bytes still awaiting their Received

bytes_sent grew only on a Received the send loop read, and the loop stops at JobDone. A frame
still in flight then went uncounted although the job holds it: a list upload reported 19000 of
26000 bytes under the coverage build.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Vq9BzVoith72tgD87LGG2z

* ava1: a lane stopped by its LaneDown never picks a frame afterwards

A lane task checked its stop flag only at the top of its loop. One that passed the check just
before LaneDown, and reached its pick after lane_death had swept the lane, charged a frame to
the dead lane: the frame sat in inflight with no lane to carry it, nothing queued, so the stall
rule never fired and the job waited forever (the soak test's resume hung under the coverage
build). The flag is now read again under the sched lock, which lane_death's sweeps take, so a
pick is either swept or sees the stop. The pick moves into pick_for_lane for a deterministic test.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Vq9BzVoith72tgD87LGG2z

* ci(coverage): run the engine tests once for both reports, 60 min limit

scripts/coverage.mjs ran `cargo llvm-cov --lcov` and then `--html`, each a full instrumented
test run. One pass now takes ~34 min, so the second ran into the 40 min limit and the job was
cancelled (it was red on main too). The tests now run once (--no-report) and both reports come
from that run's profiles via `cargo llvm-cov report`; the limit is 60 min for headroom.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Vq9BzVoith72tgD87LGG2z

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>
2026-10-06 10:17:35 -07:00
PhantomPtrandClaude Opus 5.5 9e5c258ad8 6.0.0: CI fixes, upgrade clean-up, docs and version (#377)
* 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>
2026-10-05 07:04:11 -07:00
PhantomPtr 5954c8adde 6.0.0: AVA1 replaces FTX2 — one encrypted connection for everything (#374)
See CHANGELOG.md (6.0.0). Full history of the work: tag ftx2-last and branch history archived in ps5upload-docs.
2026-10-05 00:25:05 -07:00
phantomptrandClaude Opus 5.5 c14782944d PS5Upload v5.35.0
Upload, install, convert and manage PS5 game packages over the network.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-27 04:31:13 -07:00