Benchmark failure: goosefs-sdk 0.1.6 missing CString import (corrected report)

[westonpace]

The lance-bench FTS index job fails while building Lance at commit 31a1e5006bf3fc3279bb0f7c041fb6e5cb086605.

Benchmark run: https://github.com/lancedb/lance-bench/actions/runs/29415334699
Job: bench-fts-index / benchmark
Failed step: Build benchmark

The benchmark updates its Lance git dependencies to the tested SHA and runs:

cd benchmarks/train_fts_index
cargo build --release

Build output:

Compiling goosefs-sdk v0.1.6
error[E0433]: cannot find type `CString` in this scope
  --> .../goosefs-sdk-0.1.6/src/cache/store/uring/store.rs:314:23
   |
314 |         let cstring = CString::new(path)
   |                       ^^^^^^^ use of undeclared type `CString`
   |
help: consider importing this struct
   |
12 + use std::ffi::CString;

error: could not compile `goosefs-sdk` (lib) due to 1 previous error
Process completed with exit code 101.

The resolver selected goosefs-sdk v0.1.6 while compiling Lance 9.0.0-beta.24. This blocks the FTS index benchmark before benchmark code runs. The relevant CI environment uses Rust 1.97.0 and a freshly generated lockfile (Locking 714 packages to latest Rust 1.97.0 compatible versions).

Reproduction hint: from lance-bench main, update the Lance revisions in benchmarks/train_fts_index/Cargo.toml to 31a1e5006bf3fc3279bb0f7c041fb6e5cb086605, remove/regenerate the benchmark lockfile as CI does, then run cargo build --release in that directory.

Likely remediation is to pin/upgrade/patch the GooseFS dependency or disable the affected feature until an upstream release contains the missing std::ffi::CString import.

Duplicate checks: searched open and closed Lance issues for goosefs, CString, benchmark goosefs CString, and bench-fts-index; no matching build-failure issue was found.