Xuanwo commented on issue #3887: URL: https://github.com/apache/incubator-opendal/issues/3887#issuecomment-1873226461
Current progress: ```shell :( NAPI_TARGET=wasm32-unknown-unknown pnpm run build > [email protected] build /home/xuanwo/Code/apache/incubator-opendal/bindings/nodejs > napi build --platform --features "${NAPI_FEATURES:-}" --target "${NAPI_TARGET:-}" --release --js generated.js --dts generated.d.ts && node ./scripts/header.js Compiling napi v2.14.1 warning: variable does not need to be mutable --> core/src/raw/http_util/client.rs:81:18 | 81 | pub fn build(mut builder: reqwest::ClientBuilder) -> Result<Self> { | ----^^^^^^^ | | | help: remove this `mut` | = note: `#[warn(unused_mut)]` on by default warning: constant `DEFAULT_CONNECT_TIMEOUT` is never used --> core/src/raw/http_util/client.rs:36:7 | 36 | const DEFAULT_CONNECT_TIMEOUT: Duration = Duration::from_secs(60); | ^^^^^^^^^^^^^^^^^^^^^^^ | = note: `#[warn(dead_code)]` on by default warning: missing documentation for a type alias --> core/src/raw/futures_util.rs:31:1 | 31 | pub type BoxedFuture<T> = futures::future::LocalBoxFuture<'static, T>; | ^^^^^^^^^^^^^^^^^^^^^^^ | note: the lint level is defined here --> core/src/lib.rs:67:9 | 67 | #![warn(missing_docs)] | ^^^^^^^^^^^^ warning: `opendal` (lib) generated 3 warnings (run `cargo fix --lib -p opendal` to apply 1 suggestion) Compiling opendal-nodejs v0.44.1 (/home/xuanwo/Code/apache/incubator-opendal/bindings/nodejs) error: future cannot be sent between threads safely --> bindings/nodejs/src/lib.rs:772:1 | 772 | #[napi] | ^^^^^^^ future created by async block is not `Send` | = help: the trait `std::marker::Send` is not implemented for `(dyn futures::Future<Output = (std::string::String, std::result::Result<opendal::Metadata, opendal::Error>)> + 'static)` note: captured value is not `Send` because `&mut` references cannot be sent unless their referent is `Send` --> bindings/nodejs/src/lib.rs:772:1 | 772 | #[napi] | ^^^^^^^ has type `&mut Lister` which is not `Send`, because `Lister` is not `Send` note: required by a bound in `execute_tokio_future` --> /home/xuanwo/.cargo/registry/src/index.crates.io-6f17d22bba15001f/napi-2.14.1/src/tokio_runtime.rs:121:18 | 119 | pub fn execute_tokio_future< | -------------------- required by a bound in this function 120 | Data: 'static + Send, 121 | Fut: 'static + Send + Future<Output = Result<Data>>, | ^^^^ required by this bound in `execute_tokio_future` = note: this error originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info) error: could not compile `opendal-nodejs` (lib) due to previous error (node:30467) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead. (Use `node --trace-deprecation ...` to show where the warning was created) Internal Error: Command failed: cargo build --release --target wasm32-unknown-unknown at genericNodeError (node:internal/errors:956:15) at wrappedFn (node:internal/errors:510:14) at checkExecSyncError (node:child_process:890:11) at Object.execSync (node:child_process:962:15) at BuildCommand.<anonymous> (/home/xuanwo/Code/apache/incubator-opendal/bindings/nodejs/node_modules/.pnpm/@[email protected]/node_modules/@napi-rs/cli/scripts/index.js:11555:30) at Generator.next (<anonymous>) at /home/xuanwo/Code/apache/incubator-opendal/bindings/nodejs/node_modules/.pnpm/@[email protected]/node_modules/@napi-rs/cli/scripts/index.js:3552:69 at new Promise (<anonymous>) at __awaiter$1 (/home/xuanwo/Code/apache/incubator-opendal/bindings/nodejs/node_modules/.pnpm/@[email protected]/node_modules/@napi-rs/cli/scripts/index.js:3548:10) at BuildCommand.execute (/home/xuanwo/Code/apache/incubator-opendal/bindings/nodejs/node_modules/.pnpm/@[email protected]/node_modules/@napi-rs/cli/scripts/index.js:11325:16) ELIFECYCLE Command failed with exit code 1. ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
