Commit Graph
14 Commits
Author SHA1 Message Date
donghyeon-kaandClaude Opus 5.5 0f35c985d8 fix(browser-transfer): release the vault slot on every exit of put() and open() (01-07)
Early returns before resolve (invalid input, pre-aborted signal, byte-length
mismatch) left the capability registered, so maxActiveCapabilities: 1 refused
the next issuance. The public methods now release it once in a finally.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-27 13:47:35 +09:00
DongHyeonkaandClaude Opus 5.5 dde0d2b44e perf(browser-transfer): bound concurrent image probes and reuse a passed probe (01-11)
A PRIMARY_REQUIRED resolve() downloaded and decoded the primary candidate on
every call with no concurrency limit. Probes now wait for one of
maxConcurrentProbes slots (default 4) and a passed probe is reused for the
same asset and preset while the capability is valid.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 22:44:32 +09:00
DongHyeonkaandClaude Opus 5.5 b3981f9eb7 fix(browser-transfer): record one UPLOAD_PART per part with an attempt bucket (01-10)
The executor and the runtime both recorded UPLOAD_PART, so a part retried once
became one FAILED and two SUCCEEDED records, and no retry bucket existed. PUT
attempts are now PRESIGNED_TRANSFER; the runtime records the part once with
its attempt count as countBucket.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 22:40:12 +09:00
DongHyeonkaandClaude Opus 5.5 1eee2ac580 fix(browser-transfer): refuse transport byte caps that cannot carry maxPartCount receipts (01-09)
The policy allows 10,000 parts but a 1 MiB request cap overflows near 5,300,
so the upload failed at complete after every part was sent. Given
maxPartCount, the fetch transport now rejects such a combination at
composition using a worst-case receipt size.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 22:36:00 +09:00
DongHyeonkaandClaude Opus 5.5 8f65eabadd fix(browser-transfer): check policy ceilings only when a session is created (01-08)
Resume re-ran the current policy against the stored session, so a build that
lowered maxConcurrency or maxSessionLifetimeMs failed every upload an older
build had started with INTEGRITY_FAILED. Resume now checks the session only
against its checkpoint.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 22:31:41 +09:00
DongHyeonkaandClaude Opus 5.5 b52ca8d69b fix(browser-transfer): release the vault slot of a capability put() or open() did not consume (01-07)
Only consume() removed a vault entry, so a refused, expired or aborted
transfer held a maxActiveCapabilities slot until expiry and later issuance
failed as LIMIT_EXCEEDED. The executor now revokes on every exit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 22:28:57 +09:00
DongHyeonkaandClaude Opus 5.5 c0b7ff1576 fix(browser-transfer): allow maxClockSkewMs on session and capability lifetime ceilings (01-06)
A server lifetime equal to the client ceiling was refused as soon as the
device clock ran slightly behind, and the error did not read as a clock
problem. Both ceilings now allow maxClockSkewMs (default 60 s), as image-cdn
already does; the doc states the server-side lifetime conditions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 22:25:44 +09:00
DongHyeonkaandClaude Opus 5.5 426b6b8eec fix(browser-transfer): map each upload() failure recovery to one caller action (01-05)
ABORT_PENDING and a checkpoint CAS race returned the same failure, and some
recoveries (REISSUE_CAPABILITY, RESTART for a replayed create) named actions
the caller cannot take or that repeat the failure. The port now documents a
five-value recovery table and upload() returns only those values.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 22:22:27 +09:00
DongHyeonkaandClaude Opus 5.5 5a6665a61f fix(browser-transfer): scale transfer deadlines with bytes and add a download idle limit (01-03)
A fixed 30 s attempt deadline never let a 5 MiB part finish below ~1.4 Mbit/s,
and a download had one deadline for its whole body. PUT and download limits
now add bytes / minTransferBytesPerSecond (default 64 KiB/s), and a stalled
download ends at a per-chunk idle limit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 22:16:56 +09:00
DongHyeonkaandClaude Opus 5.5 7b2cefbd32 fix(browser-transfer): keep the resourceId of a completed or lost-complete upload (01-02)
A failed checkpoint cleanup after a committed complete returned a failure and
dropped the resourceId, and abort() on ALREADY_COMPLETED returned no id. The
upload now succeeds, abort() reads the id from status first, and the port and
design doc state the in-progress complete contract (429 + Retry-After).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 22:11:04 +09:00
DongHyeonkaandClaude Opus 5.5 648fe4e9f7 fix(browser-transfer): reissue the part capability after a PUT 401/403 or expiry (01-01)
A single object-store refusal ended the whole upload as PERMISSION_DENIED
with retryable:false. The next attempt already issues a fresh capability, so
REISSUE_CAPABILITY PUT failures now retry within maxRetries; BFF issuance
refusals still stop at once.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 22:03:50 +09:00
DongHyeonkaandClaude Opus 5.5 818cbd3839 fix(browser-transfer): allow a PRIMARY_REQUIRED probe only with an exact-size fit (Q-6.1-7)
The probe accepts a decode only when it matches the primary candidate's
pixel size exactly. fit inside/outside keep the source ratio, so for any
asset whose ratio differs the preset could only fail with
INTEGRITY_FAILED, and PRIVATE_SIGNED forces the probe. Per D-12 the
registry now rejects PRIMARY_REQUIRED unless fit is cover, contain or
fill; ratio-preserving fits stay allowed on presets without the probe.
README and the architecture doc state the rule.

Verified: RED test "allows a PRIMARY_REQUIRED probe only with an
exact-size fit" (inside/outside were accepted) + all gates.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-24 13:32:37 +09:00
DongHyeonkaandClaude Opus 5.5 879ceda3bb fix(browser-transfer): let abort drop an unreadable checkpoint row (Q-6.1-6)
A corrupt row, or one a newer build wrote with an unknown schemaVersion,
failed both upload and abort with CORRUPT_DATA until the whole partition
was deleted. The checkpoint store port gains an optional
removeUnreadable(): in one transaction it deletes the row only if it does
not parse as a checkpoint (a readable row is CONFLICT, an absent row is a
success). Explicit abort calls it on a CORRUPT_DATA read and reports
ORPHANED; the server session is left to expire because the row names no
session. upload() still fails closed on such a row. The port change is
additive (optional method); the architecture doc notes the exception.

Verified: RED tests "removes an unreadable checkpoint row on abort and
reports ORPHANED" (was CORRUPT_DATA) and "removes only an unreadable row
without a revision" (method missing) + all gates.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-24 13:32:37 +09:00
donghyeon-ka 6c52cdb916 feat: 기능 추가 과정중 2026-07-30 15:58:20 +09:00