Skip to content

Ensure release checksums are verifiable#1886

Merged
oferchen merged 1 commit into
masterfrom
implement-ci-for-cross-compilation-and-tests
Nov 1, 2025
Merged

Ensure release checksums are verifiable#1886
oferchen merged 1 commit into
masterfrom
implement-ci-for-cross-compilation-and-tests

Conversation

@oferchen
Copy link
Copy Markdown
Owner

@oferchen oferchen commented Nov 1, 2025

Summary

  • update the release packaging step to record SHA256 files with stable basenames
  • stage and verify per-target checksum files when aggregating release artifacts
  • upload individual .sha256 files alongside the tarballs and consolidated SHA256SUMS

Testing

  • not run (workflow changes only)

https://chatgpt.com/codex/tasks/task_e_69063558f6848323b482d8f5ae02c816

@oferchen oferchen merged commit 02c734f into master Nov 1, 2025
@oferchen oferchen deleted the implement-ci-for-cross-compilation-and-tests branch November 1, 2025 16:34
oferchen added a commit that referenced this pull request May 5, 2026
Designs two complementary improvements to BoundedReorderBuffer (#1885,
#1886): per-buffer queue/peak/stall counters with debug_log + JSON
emission, and a wire-order bypass mode active when --delay-updates is
off. Metrics first to gate the bypass on measured evidence.
oferchen added a commit that referenced this pull request May 13, 2026
#3988)

* feat(transfer): bypass ReorderBuffer when delay-updates is off (#1886)

Add passthrough mode to both ReorderBuffer (engine) and
BoundedReorderBuffer (transfer) that skips sequence-based reordering.
When --delay-updates is disabled, files are committed immediately upon
completion, making strict file-list ordering unnecessary. The bypass
eliminates per-item ring buffer and BTreeMap overhead by routing items
through a lightweight FIFO queue.

Wire the bypass through DeltaConsumer::spawn_bypass(),
ParallelDeltaPipeline::new_bypass(), and
ThresholdDeltaPipeline::new_bypass() so callers can opt in based on
transfer configuration.

* fix(transfer): remove unused bypass_queue field from BoundedReorderBuffer
oferchen added a commit that referenced this pull request May 13, 2026
…#4015)

Audit confirms that ThresholdDeltaPipeline::new_bypass routes through
ParallelDeltaPipeline::new_bypass -> DeltaConsumer::spawn_bypass ->
ReorderBuffer::passthrough end-to-end, statically avoiding the
spill-aware ordered path designed for task #1884. The constructor
choice at the dispatcher boundary is the single decision point, and
selecting it based on ServerConfig::write::delay_updates is the
correct caller-side signal.
oferchen added a commit that referenced this pull request May 18, 2026
Designs two complementary improvements to BoundedReorderBuffer (#1885,
#1886): per-buffer queue/peak/stall counters with debug_log + JSON
emission, and a wire-order bypass mode active when --delay-updates is
off. Metrics first to gate the bypass on measured evidence.
oferchen added a commit that referenced this pull request May 18, 2026
#3988)

* feat(transfer): bypass ReorderBuffer when delay-updates is off (#1886)

Add passthrough mode to both ReorderBuffer (engine) and
BoundedReorderBuffer (transfer) that skips sequence-based reordering.
When --delay-updates is disabled, files are committed immediately upon
completion, making strict file-list ordering unnecessary. The bypass
eliminates per-item ring buffer and BTreeMap overhead by routing items
through a lightweight FIFO queue.

Wire the bypass through DeltaConsumer::spawn_bypass(),
ParallelDeltaPipeline::new_bypass(), and
ThresholdDeltaPipeline::new_bypass() so callers can opt in based on
transfer configuration.

* fix(transfer): remove unused bypass_queue field from BoundedReorderBuffer
oferchen added a commit that referenced this pull request May 18, 2026
…#4015)

Audit confirms that ThresholdDeltaPipeline::new_bypass routes through
ParallelDeltaPipeline::new_bypass -> DeltaConsumer::spawn_bypass ->
ReorderBuffer::passthrough end-to-end, statically avoiding the
spill-aware ordered path designed for task #1884. The constructor
choice at the dispatcher boundary is the single decision point, and
selecting it based on ServerConfig::write::delay_updates is the
correct caller-side signal.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant