Everything written this session that has not been through the device: rounds 43 to 48 (each patch adversarially verified, 43's transient-notice expectation fixed), a partial round 49, the pipeline scripts, the Android Auto design and the icon comparison mock. Also the two harness changes that were never A/B'd — adaptive waits, which may only shorten a declared wait and never lengthen it, and a ship that runs the mock walk and the deploy at the same time. The A/B and its 255-step baseline are in handoff/tools; main stays at what the phone has actually walked.
12 lines
1.1 KiB
Plaintext
12 lines
1.1 KiB
Plaintext
/* the one face of the six that a real build can show without arming
|
|
anything: `__ssMock` does not exist here. One already-terminal row
|
|
goes into the transfer store — the same thing the shade steps above
|
|
do — and comes straight back out. Nothing is downloaded, no room is
|
|
joined, no message is sent, nobody is signed in, and neither the
|
|
config nor the library is written. A `failed` row is not in flight,
|
|
so no notice is posted either. The id is far above the backend's own
|
|
counter and `list()` sorts id-descending, so it is the first row on
|
|
the screen even if Kyle's own session is carrying real failures. */
|
|
{ do: `(function () { __ss.transfers.items[990011] = { id: 990011, username: 'walk_peer', path: 'Walk\\\\walk-c.flac', name: 'walk-c.flac', state: 'failed', queue_place: null, local_path: null, error: 'transfer rejected: File not shared.', received: 0, total: 0 }; __ss.push('transfers', {}); return true; })()`, name: "trouble-xfer", wait: 1400 },
|
|
{ do: `(function () { delete __ss.transfers.items[990011]; __ss.back(); return true; })()`, name: "trouble-xfer-gone", wait: 1000 },
|