When using cluFlock on a wa

To recreate the errors: Create a new <a href="https://tauri.ap

To implement this, could we use the <a href="https://wiki.bash-hackers.org/howto/mutex

Thanks for reaching out, please post a minimal example with the <code class="notransla

`FlockElement` and `WaitFlockUnlock` not implemented for `File` for `wasm32-unknown-unknown` build target about cluflock HOT 3 OPEN

clucompany commented on September 23, 2024

`FlockElement` and `WaitFlockUnlock` not implemented for `File` for `wasm32-unknown-unknown` build target

from cluflock.

Comments (3)

bicarlsen commented on September 23, 2024 1

To recreate the errors:

Create a new Tauri app
a. Select Cargo as the package manager
b. Select Yew as the UI template
In the workspace's Cargo.toml (top level), add dependencies
a. getrandom = { version="0.2", features = ["js"] }
b. settings_manager = "0.0.1"
Run the app with cargo tauri dev, this should reproduce the errors.

from cluflock.

bicarlsen commented on September 23, 2024 1

To implement this, could we use the mkdir strategy for web_sys::File? Something similar to Node's proper-lockfile.

from cluflock.

denisandroid commented on September 23, 2024

Thanks for reaching out, please post a minimal example with the settings_manager library for the Tauri platform in order to reproduce the bug and fix it.

At the moment, I have no idea about the implementation of flock for the wasm32-unknown-unknown platform, since under linux these are specific calls from libc, under windows from winapi, and under wasm I have no idea.

from cluflock.

Recommend Projects