Rushmore Mushambi
Rushmore Mushambi
Personally I don't have any problem with moving the server into the `surrealdb` crate @phughk. The new dependencies that the server needs will still be under the relevant feature flag...
@phisch is right. @spence the issue you are looking for [is this one](https://github.com/surrealdb/surrealdb/issues/2338).
Looks like this is now fixed upstream as of ulid v1.1.2 (the current latest). Are you still running into this on `surrealdb-nightly`?
Closing as this is already possible. SurrealDB itself can be used directly in Rust-based Wasm applications. For Wasm environments, you can use `surrealdb.wasm` (https://github.com/surrealdb/surrealdb.wasm).
Looks like I misunderstood the issue @limcheekin. We use `wasm_bindgen_futures::spawn_local` to spawn futures on Wasm. I'm guessing that's the issue. Would you mind describing how to reproduce the issue @limcheekin?...
Which runtime do you typically use to spawn futures in those environments? Do you just use `tokio::spawn`?
How do you use them to spawn futures? After a quick search, none of them seem to have a spawn function.
@ansarizafar I don't think this is a bug so I have changed the label to make it a feature request. The reason being that we do return an error for...
@gguillemas Would you mind taking a look at this?
> @mehcode wrote: > > All Futures are fallible in that there is an associated Error type. Meaning in general usage you'll never have a await!( ... ) without being...