Eventual-Inc/Daft - CodSpeed

Daft

Blog Docs Changelog

Performance History

Latest Results

fix(telemetry): keep SSL context setup best-effort Addresses review: building the shared SSLContext happens on the main thread (in track_import_on_scarf / track_runner_on_scarf), outside the worker's try/except. If create_default_context() fails (e.g. system CA store cannot be loaded), the error would propagate into the user's import or query execution, breaking telemetry's best-effort contract. Wrap the setup in try/except and skip the telemetry event on failure (return no thread), instead of raising. Add a test asserting that an SSL setup failure is swallowed and no request thread is started. Signed-off-by: fanng <“fanng@apache.org”>

FANNG1:fix/telemetry-exit-segfault

5 hours ago

fix(telemetry): prevent interpreter-shutdown segfault from Scarf telemetry The Scarf telemetry worker runs in a daemon thread that makes HTTPS requests via urllib. At interpreter shutdown that thread can still be inside the SSL/OpenSSL stack (creating an SSLContext and loading CA certificates) while the main thread finalizes, and the two race on OpenSSL global state, crashing the process with SIGSEGV *after* all user work has already completed successfully. It reproduces with plain repeated daft usage (e.g. a few `DataFrame.write_lance` / `read_*` calls in one process) and is easy to hit on interpreters that statically link OpenSSL, such as the python-build-standalone builds used by uv/pyenv. It surfaces as exit code 139, which CI and batch schedulers treat as a failure even though the data was written correctly. Fix: build the SSLContext once on the main thread and reuse it for the telemetry requests, so the daemon worker never initializes OpenSSL global state itself and cannot race teardown. Also pass an explicit request timeout so a slow or unreachable endpoint can't keep the worker alive inside the SSL stack. Telemetry stays non-blocking (still a daemon thread), so process shutdown is not slowed. Opting out via DAFT_ANALYTICS_ENABLED=0 / DO_NOT_TRACK=1 also avoids it. Signed-off-by: fanng <“fanng@apache.org”>

FANNG1:fix/telemetry-exit-segfault

7 hours ago

Update the tests

lhoestq:document-s3-alternative-for-cc

19 hours ago

perf(video): tracking doc for read_video_frames streaming gaps

yk/video-read-frames-perf

23 hours ago

Add end to end tests

arpatilmh:abhijeet/deltalake-s3-conditional-put

24 hours ago

Merge branch 'main' into abhijeet/deltalake-s3-conditional-put

arpatilmh:abhijeet/deltalake-s3-conditional-put

1 day ago

YuangGao:feat/transformers-vision-prompter

1 day ago

feat(io): export GooseFSConfig from daft.io Register GooseFSConfig alongside the other connector configs so users can write `from daft.io import IOConfig, GooseFSConfig` (matching the pattern used by S3Config, CosConfig, etc.), and add the missing pyi stubs so mypy and IDEs can see the type. Follow-up to #7192 (rename GoosefsConfig -> GooseFSConfig).

XuQianJin-Stars:feat/export-goosefs-config

2 days ago

Latest Branches

0%

fix(telemetry): prevent interpreter-shutdown segfault from Scarf telemetry#7203

6 hours ago

c92024d

FANNG1:fix/telemetry-exit-segfault

0%

feat: Use HF Bucket as as alternative for Common Crawl#7103

19 hours ago

589b0b5

lhoestq:document-s3-alternative-for-cc

0%

perf(video): close the read_video_frames streaming gaps (tracking)#7201

1 day ago

f445b4b

yk/video-read-frames-perf

© 2026 CodSpeed Technology

Home Terms Privacy Docs