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
{{ message }}
Repository navigation
Commit 56bcc47
Browse filesBrowse the repository at this point in the historyBrowse files
fix: opt predict_version into SQLITE_RESULT_SUBTYPE; harden CI subtype check
The Windows (MinGW) CI job surfaced a real latent bug, not a platform
quirk: predict_version() calls sqlite3_result_subtype() to tag its JSON
result, but SQLite 3.45+ refuses that call unless the function was
registered with SQLITE_RESULT_SUBTYPE. macOS shipped an older SQLite that
never enforced it, so local tests passed; MSYS2's newer sqlite3 CLI
returned 'misuse of sqlite3_result_subtype()'.
- Register predict_version with SQLITE_RESULT_SUBTYPE (guarded #ifdef so
a header bump either direction stays safe; scoped to the one function
that sets a subtype).
- Compile the static test builds (soak, asan, wasm, fuzz) with
-DSQLITE_STRICT_SUBTYPE=1 and exercise predict_version()/predict_debug()
in the soak, so this bug class now fails under our own ASan/valgrind/
wasm runs instead of only on Windows CI.
- wasm job: install emscripten directly from emscripten-core/emsdk
instead of an unresolvable third-party action.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: mstrathman <matthew.strathman@gmail.com>
0 commit comments