Skip to content

fix(httpfs): make openFileWithImmutability available in WASM builds - #66

Closed
adsharma wants to merge 1 commit into
duckdb_relfrom
fix-wasm-openfilewithimmutability
Closed

fix(httpfs): make openFileWithImmutability available in WASM builds#66
adsharma wants to merge 1 commit into
duckdb_relfrom
fix-wasm-openfilewithimmutability

Conversation

@adsharma

Copy link
Copy Markdown
Contributor

Summary

  • HTTPFileSystem::openFileWithImmutability() was declared under #if HTTPFS_REMOTE_READ_OPTIMIZATIONS, which is 0 for __WASM__ builds, but XetFileSystem::openFile (xetfs.cpp) calls it unconditionally. This broke the wasm build:
xetfs.cpp:134:28: error: no member named 'openFileWithImmutability' in 'lbug::httpfs_extension::HTTPFileSystem'
  • Move the declaration into the always-compiled public section of HTTPFileSystem. The implementation in httpfs.cpp was never guarded, so only the declaration needed to move. The immutableContent flag remains a no-op in builds without remote read optimizations.

Testing

  • CI: Build and Deploy workflow with wasm only (all other targets skipped).

openFileWithImmutability() was declared under
#if HTTPFS_REMOTE_READ_OPTIMIZATIONS, which is 0 for __WASM__ builds,
but XetFileSystem::openFile calls it unconditionally. This broke the
wasm build in the httpfs extension source target.

Move the declaration into the always-compiled public section of
HTTPFileSystem. The immutableContent flag remains a no-op in builds
without remote read optimizations.
@adsharma
adsharma deleted the branch duckdb_rel August 28, 2026 01:21
@adsharma adsharma closed this Aug 28, 2026
@adsharma
adsharma deleted the fix-wasm-openfilewithimmutability branch August 28, 2026 03:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant