You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Summary
Currently, if you build something like `duckdb-bench` cargo will rebuild
`vortex-duckdb` once before it'll be satisfied that it doesn't need to
rebuild it. The root cause is that cargo's fingerprinting can't
accurately track files that are created **during** the build.
This change is fine because we still track our own changes, the only
external change will be something like a duckdb version upgrade which
will change `build.rs` and re-trigger the build as expected.
Signed-off-by: Adam Gutglick <adam@spiraldb.com>
0 commit comments