Avatar for the Eventual-Inc user
Eventual-Inc
Daft
BlogDocsChangelog

Performance History

Latest Results

fix(daft-distributed): remove unused hash_map_macro feature gate (#6981) ## What Remove the `#![feature(hash_map_macro)]` feature gate from `daft-distributed/src/lib.rs`. ## Why The `hash_map_macro` feature was [removed from Rust after 1.91](https://github.com/rust-lang/rust/issues/87853) and does not exist in stable Rust 1.95.0+. `daft-distributed` declares the feature gate but never uses the `hash_map!` macro anywhere in the crate, so the gate can be safely removed. This eliminates one unnecessary nightly-only feature gate, making it easier to compile daft on stable Rust. ## Testing - Verified that `hash_map!` is not used anywhere in `daft-distributed`: ``` grep -rn "hash_map!" src/daft-distributed/ # no results ``` We've also built 0.7.14 with Rust 1.95 in our own build system. Signed-off-by: Mike DePaulo <mikedep333@redhat.com>
main
28 minutes ago
fix(flotilla): silence noisy logs from distributed-limit cancellation PR #6942 surfaced three categories of confusing output during limit cancellation. None changed query results; all are removed here. - `ray.cancel(result_handle)` on every non-contributor task marked them FAILED in Ray's task table. Replaced with `actor.cancel_input.remote(...)`, which closes the per-input result channel inside the worker's `NativeExecutor` so `run_plan` drains and returns FINISHED. - `claim` / `start_task` on the torn-down counter actor used to raise `ActorDiedError`, propagate out of `DistributedLimitSink::execute`, and tear down the worker's run loop. They now swallow that error as a residual-race safety net (`LimitNode` drains task cancels first, so this only fires when a sink call is mid-flight). - "Plan execution task has died; cannot enqueue new input" was the downstream symptom of the previous two on concurrent inputs sharing a plan; no longer reproducible. Mechanism: 1. `NativeExecutor` exposes `cancel_input(fingerprint, input_id)`. It sends through a new unbounded channel; `run_execution_loop` drops the per-input result sender, ending the Python iteration cleanly. 2. `TaskResultHandle::cancel_callback` now returns a `Future`. The Ray impl awaits the Python `actor.cancel_input.remote(...)` ack so the scheduler can sequence post-cancel teardown. 3. `LimitNode::limit_execution_loop` drains `running_tasks` after firing `parent_cancel.cancel()` and before `teardown_limit_counter_actor`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
colin/fix-distributed-limit-cancel-noise
19 hours ago

Latest Branches

CodSpeed Performance Gauge
0%
fix(daft-distributed): remove unused hash_map_macro feature gate#6981
3 hours ago
b1c59de
mikedep333:remove-hash_map_macro
CodSpeed Performance Gauge
0%
8 days ago
856a3f9
rohit/test/checkpoint-s3-routable-fixtures
CodSpeed Performance Gauge
0%
fix(io): use checked_shl and saturating_mul in retry jitter calculation#6949
7 hours ago
90fef74
ARDA7787:patch-1
© 2026 CodSpeed Technology
Home Terms Privacy Docs