close() delivers the tail pack; flush() and stop() return on time while the store or catalog stalls by zaoxing · Pull Request #162 · ProjectDMX/DMI

Stage the sink's open pack when the ring releases it

zaoxing

committed

648f6ce

Let a cancel cut uploads short: abort the transfer, wake the backoff

zaoxing

committed

fa250a1

Return flush(timeout) on time, and stop() promptly while an upload stalls

zaoxing

committed

5f882cd

Say what close() drains, and what its budget does and does not bound

zaoxing

committed

af4f4f2

Bound a sink flush by its own timeout while another is in flight

zaoxing

committed

7a60f35

Cut index reads at stop() and past a flush; end a pass at an unanswered read

zaoxing

committed

b13c7ec

Start no index batch past a flush's deadline but the first

zaoxing

committed

0121538

Run no loop cycle between a flush and the stop() after it

zaoxing

committed

efe9279

Say what close() and flush() now overrun their budget by

zaoxing

committed

90d00b0

Do not hash the spool in a flush that is out of time

zaoxing

committed

15db912

Book an upload as cancelled only when the cancel ended it

zaoxing

committed

b61db70

Keep the lease test's last cycle busy with work stop() cannot cut

zaoxing

committed

7189a15

Refuse, not hold, the connection a closed switch still accepts

zaoxing

committed

7a6617d

Pin that a cancel wakes both upload backoffs, not just ends them

zaoxing

committed

4d90b5a

Test that the release backstop is bounded and fails soft

zaoxing

committed

f9807ce

Pin that a flush never runs the reconcile, only the loop does

zaoxing

committed

53c9c2b

Test the cancel paths a stop and a restart go through

zaoxing

committed

80df337

Say that close()'s stop can wait for a renewal, and drop "within"

zaoxing

committed

58453c8

Stop a spool listing between packs at stop() or a flush's deadline

zaoxing

committed

5fecd88

Index a full batch first, not the remainder, past a flush's deadline

zaoxing

committed

f563341

Drop the flush-out-of-time spool check the cancelled listing replaced

zaoxing

committed

7a4b312

Upload and index a chunk at a time, so a cut cycle owes one chunk at most

zaoxing

committed

d677f07

Start no index batch once the reads are cut, and no reconcile query

zaoxing

committed

9acff4d

Book a failed index read as cancelled only when the cancel cut it

zaoxing

committed

e49739f

Pin that a cut PUT or part on the last attempt books a cancel

zaoxing

committed

41398b8

Loosen the listing-cut test's time bound to what it has to separate

zaoxing

committed

2172aea

Assert that a reconcile listing stop() cuts ends quietly

zaoxing

committed

301cdb2

Say, and pin, that a cut multipart upload's abort outlasts a request timeout

zaoxing

committed

8bc3fb7

Say close() drains with a budget of close_flush_timeout_s, not within it

zaoxing

committed

bb774c4

Say in cancel.h that the service owns two Cancellations

zaoxing

committed

7525aac

Name the S3 retries the client actually makes, and its backoff cap

zaoxing

committed

1303d85

Cap the S3 backoff's shift, not only its result

zaoxing

committed

119cea8

Reflow three lines the chunking and read-cancel commits left long

zaoxing

committed

8044c5e

Navigation Menu

Repository navigation

close() delivers the tail pack; flush() and stop() return on time while the store or catalog stalls - #162

close() delivers the tail pack; flush() and stop() return on time while the store or catalog stalls#162
zaoxing merged 33 commits into
mainfrom
feat/close-flush-backstop

Commits on Sep 29, 2026

Stage the sink's open pack when the ring releases it

Let a cancel cut uploads short: abort the transfer, wake the backoff

Return flush(timeout) on time, and stop() promptly while an upload stalls

Say what close() drains, and what its budget does and does not bound

Bound a sink flush by its own timeout while another is in flight

Cut index reads at stop() and past a flush; end a pass at an unanswered read

Start no index batch past a flush's deadline but the first

Run no loop cycle between a flush and the stop() after it

Say what close() and flush() now overrun their budget by

Do not hash the spool in a flush that is out of time

Book an upload as cancelled only when the cancel ended it

Keep the lease test's last cycle busy with work stop() cannot cut

Refuse, not hold, the connection a closed switch still accepts

Pin that a cancel wakes both upload backoffs, not just ends them

Test that the release backstop is bounded and fails soft

Pin that a flush never runs the reconcile, only the loop does

Test the cancel paths a stop and a restart go through

Say that close()'s stop can wait for a renewal, and drop "within"

Stop a spool listing between packs at stop() or a flush's deadline

Index a full batch first, not the remainder, past a flush's deadline

Drop the flush-out-of-time spool check the cancelled listing replaced

Upload and index a chunk at a time, so a cut cycle owes one chunk at most

Start no index batch once the reads are cut, and no reconcile query

Book a failed index read as cancelled only when the cancel cut it

Pin that a cut PUT or part on the last attempt books a cancel

Loosen the listing-cut test's time bound to what it has to separate

Assert that a reconcile listing stop() cuts ends quietly

Say, and pin, that a cut multipart upload's abort outlasts a request timeout

Say close() drains with a budget of close_flush_timeout_s, not within it

Say in cancel.h that the service owns two Cancellations

Name the S3 retries the client actually makes, and its backoff cap

Cap the S3 backoff's shift, not only its result

Reflow three lines the chunking and read-cancel commits left long