vortex-data/vortex - CodSpeed

vortex

Blog Docs Changelog

Performance History

Latest Results

ci: exclude changelog/ci from release notes Signed-off-by: Joe Isaacs <joe.isaacs@live.co.uk> Signed-off-by: Claude <noreply@anthropic.com>

claude/laughing-rubin-gUBXV

27 minutes ago

fix(vortex-duckdb): satisfy clippy::absolute_paths in Windows build.rs Use a #[cfg(unix)] import for std::os::unix::fs::symlink instead of the fully-qualified path, which tripped the repo's denied clippy::absolute_paths lint. The cfg gate keeps the symbol out of the Windows build. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Joe Isaacs <joe.isaacs@live.co.uk>

feat/windows-arm64-build

14 hours ago

fix(vortex-duckdb): make build.rs cross-platform for Windows The DuckDB extension build script was unix-only, which broke the Windows build of the duckdb-vortex extension (E0433: `std::os::unix` not found): - Drop the unconditional `use std::os::unix::fs::symlink`. The symlink of the extracted source into `crate_dir/duckdb` is only a dev/tooling convenience (the build uses the extracted `inner_dir` directly), so move it into a `#[cfg(unix)]` helper that is a no-op elsewhere. - Add the Windows targets (x86_64/aarch64-pc-windows-msvc) to the prebuilt-libduckdb download match; DuckDB ships libduckdb-windows-amd64 /-arm64.zip. Recognise duckdb.dll as a build artifact. - In compile_cpp, gate the GCC/Clang `-W*`/`-isystem` flags behind a non-MSVC check and use `/W4` + a normal include on MSVC (`cl` rejects the GNU-style flags). - Skip the `-Wl,-rpath` link arg on Windows (MSVC's linker rejects it; the DLL is resolved via PATH instead). Platform conditionals use CARGO_CFG_TARGET_OS/ENV (the build target), not `cfg!()`, which in a build script reflects the host. This lets vortex-duckdb build on windows_amd64 and windows_arm64 so the duckdb-vortex extension can opt those CI targets in. (The aws-lc-sys ARM64 assembly link failure that previously blocked windows_arm64 no longer applies: the TLS stack now resolves to rustls + ring.) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Joe Isaacs <joe.isaacs@live.co.uk>

feat/windows-arm64-build

14 hours ago

ci(musl): mark bind-mounted workspace as git safe.directory The musl container bind-mounts the host runner's checkout at /work, owned by a different uid than the container root. git then rejects it as 'dubious ownership' and 'git rev-parse HEAD' returns empty. vortex-bench (GIT_COMMIT_ID) and the benchmarks website (build.rs VORTEX_BENCH_BUILD_SHA) embed that SHA in insta snapshots, redacted to <commit-sha>/<build-sha>; an empty SHA breaks the redaction and fails 10 snapshot tests. Marking /work safe lets git resolve the SHA so the snapshots match. Signed-off-by: Joe Isaacs <joe.isaacs@live.co.uk> Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

claude/elegant-ptolemy-VxJVN

14 hours ago

ci: move musl to its own workflow and fix Alpine timezone test failures Split the x86_64-unknown-linux-musl test job out of the unified rust-test-other matrix into a dedicated .github/workflows/musl.yml so its container-based, hand-provisioned execution model is no longer coupled to the glibc test runners. The check name 'Rust tests (linux-musl)' is unchanged. Add tzdata to the Alpine package set: without /usr/share/zoneinfo the datetime tests fail with 'failed to find time zone UTC since there is no time zone database configured' (38 failures). Signed-off-by: Joe Isaacs <joe.isaacs@live.co.uk> Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

claude/elegant-ptolemy-VxJVN

14 hours ago

ci: allow changelog/ci changelog label Signed-off-by: Joe Isaacs <joe.isaacs@live.co.uk> Signed-off-by: Claude <noreply@anthropic.com>

claude/laughing-rubin-gUBXV

15 hours ago

ci(fuzz): give the reusable fixer its own concurrency group fuzzer-issue-autofix.yml (the issues-triggered caller) uses concurrency group `fuzzer-fix-<issue>` to collapse the duplicate opened+labeled events GitHub emits. The reusable fuzzer-fix-automation.yml used the *same* group name. Because a reusable workflow runs inside its caller's run, entering the identical group with cancel-in-progress made the fixer cancel its own parent: the run failed after the gate job with no fix job ever starting, and no fix PR was produced for issues filed via the label trigger. Namespace the reusable workflow's group as `fuzzer-fix-automation-<issue>` so it no longer collides with the caller. Direct workflow_dispatch invocations are still deduped per issue. Signed-off-by: Joe Isaacs <joe.isaacs@live.co.uk>

ji/fix-fuzzer-autofix-concurrency

15 hours ago

ci(fuzz): label auto-generated fuzzer-fix PRs Tag the draft PRs the fixer opens with two labels: - `fuzzer-fix` — identifies the PR as auto-generated from a fuzzer issue. - `changelog/fix` — satisfies the required "Validate Changelog Label" check, which expects every PR to carry exactly one `changelog/*` label. These automated PRs previously carried none, so that check would fail. The owned `fuzzer-fix` label is created if missing so a fresh repo/fork doesn't error; `changelog/fix` is a curated repo label and is not recreated. Signed-off-by: Joe Isaacs <joe.isaacs@live.co.uk>

ji/label-fuzzer-fix-prs

15 hours ago

Latest Branches

-4%

ci: allow changelog/ci label#8205

28 minutes ago

44c35a0

claude/laughing-rubin-gUBXV

-4%

fix(vortex-duckdb): make build.rs cross-platform for Windows#8206

14 hours ago

4cd6b6b

feat/windows-arm64-build

-4%

Add x86_64-unknown-linux-musl target to CI#8199

14 hours ago

bd0e8c5

claude/elegant-ptolemy-VxJVN

© 2026 CodSpeed Technology

Home Terms Privacy Docs