Some hackers had issues with running examples on Windows. For example, in aqua-ipfs-example aqua npm package calls shell script on npm install command, which leads to unexpected problems

WLS

An error occurred while building the project

kevin@LAPTOP-42HSF5M2:/mnt/d/blockchain/fluence$ fluence init hello-world-20240413
? Select template quickstart
Using local blockchain environment
Error: No such file or directory (os error 2)
Error: Command: /home/kevin/.fluence/cargo/marine/0.19.7/bin/marine build -p myService --release exited with code 1
kevin@LAPTOP-42HSF5M2:/mnt/d/blockchain/fluence$

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Datasource	Name	Replacement PR?
npm	@fluencelabs/aqua
npm	@fluencelabs/fluence
npm	@fluencelabs/js-client.api
npm	@fluencelabs/js-client.node

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update fluence js (@fluencelabs/aqua-ipfs, @fluencelabs/aqua-lib, @fluencelabs/fluence-network-environment, @fluencelabs/js-client)
• fix(deps): update marine rust sdk (marine-rs-sdk, marine-rs-sdk-test)

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Almost all service examples here use obsolete mem_pages_count setting in a Marine config. We need to replace them with superseeded max_heap_size instead to provide fully functional up-to-date examples.

Hi,

I find the examples the best spot to learn the Aqua, Marine, and overall Fluence protocol. Due to the recent(good) improvements on Nodejs, it would be great to:

1. Update project README.md to exclusively tell the user what versions of Nodejs, and Rust to use. This is super helpful to help people know what exact version of the tooling they should use.

So that a significant amount of time is not spent resolving incompatibilities and resolving breaking things.

Best,
Naftali

hi

I did comands
1 git clone https://github.com/fluencelabs/examples
2 cd examples/quickstart/1-browser-to-browser
3 npm install

[email protected] postinstall /home/kirill/fluence/test/examples/quickstart/1-browser-to-browser
copy-avm-public public

ensure directory exists: /home/kirill/fluence/test/examples/quickstart/1-browser-to-browser/public
copying AVM wasm
from: /home/kirill/fluence/test/examples/quickstart/1-browser-to-browser/node_modules/@fluencelabs/avm/dist/avm.wasm
to: /home/kirill/fluence/test/examples/quickstart/1-browser-to-browser/public/avm.wasm
done!
ensure directory exists: /home/kirill/fluence/test/examples/quickstart/1-browser-to-browser/public
copying avm runner script
from: /home/kirill/fluence/test/examples/quickstart/1-browser-to-browser/node_modules/@fluencelabs/avm-runner-background/dist/runnerScript.web.js
to: /home/kirill/fluence/test/examples/quickstart/1-browser-to-browser/public/runnerScript.web.js
done!
ensure directory exists: /home/kirill/fluence/test/examples/quickstart/1-browser-to-browser/public
copying marine-js wasm
from: /home/kirill/fluence/test/examples/quickstart/1-browser-to-browser/node_modules/@fluencelabs/marine-js/dist/marine-js.wasm
to: /home/kirill/fluence/test/examples/quickstart/1-browser-to-browser/public/marine-js.wasm
done!
npm WARN @testing-library/[email protected] requires a peer of @testing-library/dom@>=7.21.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of ajv@^6.9.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of puppeteer@>= 1.5.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of node-fetch@* but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

audited 1911 packages in 15.762s

190 packages are looking for funding
run npm fund for details

found 23 vulnerabilities (10 low, 13 moderate)
run npm audit fix to fix them, or npm audit for details

4 npm run compile-aqua

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'compile-aqua' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'precompile-aqua', 'compile-aqua', 'postcompile-aqua' ]
5 info lifecycle [email protected]precompile-aqua: [email protected]
6 info lifecycle [email protected]compile-aqua: [email protected]
7 verbose lifecycle [email protected]compile-aqua: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]compile-aqua: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/kirill/fluence/test/examples/quickstart/1-browser-to-browser/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle [email protected]compile-aqua: CWD: /home/kirill/fluence/test/examples/quickstart/1-browser-to-browser
10 silly lifecycle [email protected]compile-aqua: Args: [ '-c', 'aqua -i ./aqua/ -o ./src/_aqua' ]
11 silly lifecycle [email protected]compile-aqua: Returned: code: 1 signal: null
12 info lifecycle [email protected]compile-aqua: Failed to exec compile-aqua script
13 verbose stack Error: [email protected] compile-aqua: aqua -i ./aqua/ -o ./src/_aqua
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/share/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess. (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid [email protected]
15 verbose cwd /home/kirill/fluence/test/examples/quickstart/1-browser-to-browser
16 verbose Linux 5.13.0-35-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "compile-aqua"
18 verbose node v10.19.0
19 verbose npm v6.14.4
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] compile-aqua: aqua -i ./aqua/ -o ./src/_aqua
22 error Exit status 1
23 error Failed at the [email protected] compile-aqua script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

I trying to run browser-to-browser example in devcontainer (without vscode), but it fails.

1. I pulled fluencelabs/devcontainer (image ID 8345668a42fe )

2. I started it: docker run --rm -it fluencelabs/devcontainer. Working directory is the root directory.

3. I executed git clone --depth 1 https://github.com/fluencelabs/examples.git examples, the first line from /download_examples.sh script. Current commit 013ceb6.

4. In directory /examples/quickstart/1-browser-to-browser I issued npm install, as recommended by the tutorial.

5. The command finished successfully (exit code 0), albeit with warnings and update notifications.

6. I issued npm start, as recommended by the tutorial.

7. I saw Starting the development server..., then

   Failed to compile.
   
   ./src/App.tsx
   Module not found: Can't resolve './_aqua/getting-started' in '/examples/quickstart/1-browser-to-browser/src'
   

Expected: it starts listening development server on port 3000, as per the tutorial.

8. As a workaround attempt, I exited (Ctrl+C) the npm start and did this command: mkdir src/_aqua && aqua-cli --input aqua/getting-started.aqua --output src/_aqua (not taken from the tutorial). It had finished successfully and produced getting-started.ts file, but npm start still does not work:

   Failed to compile.
   
   ./src/App.tsx
   Attempted import error: 'registerHelloPeer' is not exported from './_aqua/getting-started'.
   

Does devcontainer and tutorial really support VSCode-less experimentation?