Why is there no network yet? I want to play around with it

You can either:

  • wait for the next test network, probably not long now (check the weekly update on Thursdays, so perhaps as soon as tonight)
  • use a mock-routing build (not yet working on some Linux - Ubuntu 17.04 reported as working so maybe others too - but should be OK on windows)
  • run your own local network on a single machine by modifying and building the code yourself - see local test network

EDITED to add note about Ubuntu h/t @JPL

8 Likes
  • Test network didn’t arrive and the message was that it would be opened to a select few.
  • I use Linux and it’s Linux or bust.
  • Local test network it is then.

How about helping yourself?

  • Show willing and you may be among the select few :slightly_smiling_face:
  • Try a different Linux - it works with Ubuntu 17.04 in my experience. Use VirtualBox (works with Arch) to install Ubuntu as a VM
  • Let us know how you get on with the local test network.
2 Likes

I’m not a team of people, so what the maidsafe core devs’ roadmap is, I will be dependent on.
So any mod attempt for a local network should be quick and repeatable.

Or may not be.

[Update]

:frowning: 99.99% of the time such a message means no.

I just noticed that I actually use a mock routing version.

Namely this one: https://github.com/maidsafe/safe_browser/releases/tag/0.2.1

But that one still gives me a “Could not connect to SAFE Network” error.

1 Like

When I built it myself I had the same problem (see this issue). It appears both this and Hunter’s fork have been broken by the latest changes. Hunter is working on a fix.

1 Like

Are you still testing on Arch? There’s no guarantee it will work on that distro. I was going to try it but was struggling to install a GUI on Arch so I gave up.

Yes and I get this error when I try to build it:

$ NODE_ENV=dev npm i
...
> beaker-plugin-safe-app@0.1.0 build-protocol /home/folatt/workspace/MaidSafe/safe_browser-0.2.1/app/node_modules/beaker-plugin-safe-app
[0] > cross-env NODE_ENV=production node -r babel-register ./node_modules/webpack/bin/webpack --config webpack.config.protocol.js --progress --profile --colors
[0] 
[1] 
[1] > beaker-plugin-safe-app@0.1.0 build-api /home/folatt/workspace/MaidSafe/safe_browser-0.2.1/app/node_modules/beaker-plugin-safe-app
[1] > cross-env NODE_ENV=production node -r babel-register ./node_modules/webpack/bin/webpack --config webpack.config.api.js --progress --profile --colors
[1] 
[1] module.js:487
[1]     throw err;
[1]     ^
[1] 
[1] Error: Cannot find module '/home/folatt/workspace/MaidSafe/safe_browser-0.2.1/app/node_modules/beaker-plugin-safe-app/webpack.config.api.js'
[1]     at Function.Module._resolveFilename (module.js:485:15)
[1]     at Function.Module._load (module.js:437:25)
[1]     at Module.require (module.js:513:17)
[1]     at require (internal/module.js:11:18)
[1]     at requireConfig (/home/folatt/workspace/MaidSafe/safe_browser-0.2.1/app/node_modules/beaker-plugin-safe-app/node_modules/webpack/bin/convert-argv.js:96:18)
[1]     at /home/folatt/workspace/MaidSafe/safe_browser-0.2.1/app/node_modules/beaker-plugin-safe-app/node_modules/webpack/bin/convert-argv.js:109:17
[1]     at Array.forEach (native)
[1]     at module.exports (/home/folatt/workspace/MaidSafe/safe_browser-0.2.1/app/node_modules/beaker-plugin-safe-app/node_modules/webpack/bin/convert-argv.js:107:15)
[1]     at Object.<anonymous> (/home/folatt/workspace/MaidSafe/safe_browser-0.2.1/app/node_modules/beaker-plugin-safe-app/node_modules/webpack/bin/webpack.js:153:40)
[1]     at Module._compile (module.js:569:30)
[0] module.js:487
[0]     throw err;
[0]     ^
[0] 
[0] Error: Cannot find module '/home/folatt/workspace/MaidSafe/safe_browser-0.2.1/app/node_modules/beaker-plugin-safe-app/webpack.config.protocol.js'
[0]     at Function.Module._resolveFilename (module.js:485:15)
[0]     at Function.Module._load (module.js:437:25)
[0]     at Module.require (module.js:513:17)
[0]     at require (internal/module.js:11:18)
[0]     at requireConfig (/home/folatt/workspace/MaidSafe/safe_browser-0.2.1/app/node_modules/beaker-plugin-safe-app/node_modules/webpack/bin/convert-argv.js:96:18)
[0]     at /home/folatt/workspace/MaidSafe/safe_browser-0.2.1/app/node_modules/beaker-plugin-safe-app/node_modules/webpack/bin/convert-argv.js:109:17
[0]     at Array.forEach (native)
[0]     at module.exports (/home/folatt/workspace/MaidSafe/safe_browser-0.2.1/app/node_modules/beaker-plugin-safe-app/node_modules/webpack/bin/convert-argv.js:107:15)
[0]     at Object.<anonymous> (/home/folatt/workspace/MaidSafe/safe_browser-0.2.1/app/node_modules/beaker-plugin-safe-app/node_modules/webpack/bin/webpack.js:153:40)
[0]     at Module._compile (module.js:569:30)
[0] npm
[0]  ERR! code ELIFECYCLE
[0] npm ERR! errno 1
[0] npm ERR! beaker-plugin-safe-app@0.1.0 build-protocol: `cross-env NODE_ENV=production node -r babel-register ./node_modules/webpack/bin/webpack --config webpack.config.protocol.js --progress --profile --colors`
[0] npm ERR!
[0]  Exit status 1
[0] npm ERR! 
[0] npm ERR! Failed at the beaker-plugin-safe-app@0.1.0 build-protocol script.
[0] npm ERR!
[0]  This is probably not a problem with npm. There is likely additional logging output above.
[0] 
[0] npm ERR! A complete log of this run can be found in:
[0] npm ERR!     /home/folatt/.npm/_logs/2017-07-09T09_11_51_739Z-debug.log
[1] npm ERR! code ELIFECYCLE
[1] npm ERR! errno 1
[1] npm ERR! beaker-plugin-safe-app@0.1.0 build-api: `cross-env NODE_ENV=production node -r babel-register ./node_modules/webpack/bin/webpack --config webpack.config.api.js --progress --profile --colors`
[1] npm ERR! Exit status 1
[1] npm ERR! 
[1] npm ERR! Failed at the beaker-plugin-safe-app@0.1.0 build-api script.
[1] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[1] 
[1] npm ERR! A complete log of this run can be found in:
[1] npm ERR!     /home/folatt/.npm/_logs/2017-07-09T09_11_51_743Z-debug.log
[0] npm run build-protocol exited with code 1
[1] npm run build-api exited with code 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! beaker-plugin-safe-app@0.1.0 build: `concurrently "npm run build-protocol" "npm run build-api"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the beaker-plugin-safe-app@0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/folatt/.npm/_logs/2017-07-09T09_11_51_803Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ build-safe-app: `cd ./app/node_modules/beaker-plugin-safe-app && npm i && npm run build`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @ build-safe-app script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/folatt/.npm/_logs/2017-07-09T09_11_51_843Z-debug.log

I suspect the issue is as @happybeing describes above, but it could be something to do with Arch. I have found that it doesn’t work on all Linuxes. It’s only supported on the versions that the devs use for now.

I tried the hunter one as well. I got as far as step 4.

$ npm run pack-authenticator
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})


> beaker-plugin-safe-authenticator@0.1.0 build-libs /home/folatt/workspace/MaidSafe/safe_browser/authenticator
> npm run init-submodule && node ./build_libs.js "--features=mock-routing"



> beaker-plugin-safe-authenticator@0.1.0 init-submodule /home/folatt/workspace/MaidSafe/safe_browser/authenticator
> git submodule update --init --recursive



> beaker-plugin-safe-authenticator@0.1.0 build-libs:mock /home/folatt/workspace/MaidSafe/safe_browser/authenticator
> npm run build-native-mock && npm run build-system-uri




> beaker-plugin-safe-authenticator@0.1.0 build-native-mock /home/folatt/workspace/MaidSafe/safe_browser/authenticator
> cd ./native/safe_authenticator && cargo update && cargo build --release --features "use-mock-routing" && cd ../../



    Updating registry `https://github.com/rust-lang/crates.io-index`


    Updating git repository `https://github.com/maidsafe/self_encryption.git`


    Updating git repository `https://github.com/maidsafe/routing.git`


   Compiling traitobject v0.0.1


   Compiling winapi-build v0.1.1
   Compiling itoa v0.3.1


   Compiling linked-hash-map v0.3.0


error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

thread 'rustc' panicked at 'called `Result::unwrap()` on an `Err` value: "read_option: expected 0 for None or 1 for Some"', /checkout/src/libcore/result.rs:859
note: Run with `RUST_BACKTRACE=1` for a backtrace.



error: Could not compile `traitobject`.

Build failed, waiting for other jobs to finish...


error: internal compiler error: unexpected panic



note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

thread 'rustc' panicked at 'called `Result::unwrap()` on an `Err` value: "read_option: expected 0 for None or 1 for Some"', /checkout/src/libcore/result.rs:859
note: Run with `RUST_BACKTRACE=1` for a backtrace.



error: Could not compile `winapi-build`.


Build failed, waiting for other jobs to finish...


error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports


thread 'rustc' panicked at 'called `Result::unwrap()` on an `Err` value: "read_option: expected 0 for None or 1 for Some"', /checkout/src/libcore/result.rs:859
note: Run with `RUST_BACKTRACE=1` for a backtrace.



error: Could not compile `itoa`.

Build failed, waiting for other jobs to finish...


error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.


note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

thread 'rustc' panicked at 'called `Result::unwrap()` on an `Err` value: "read_option: expected 0 for None or 1 for Some"', /checkout/src/libcore/result.rs:859
note: Run with `RUST_BACKTRACE=1` for a backtrace.



error: build failed


npm
 ERR! code ELIFECYCLE
npm ERR! errno 101
npm 
ERR! beaker-plugin-safe-authenticator@0.1.0 build-native-mock: `cd ./native/safe_authenticator && cargo update && cargo build --release --features "use-mock-routing" && cd ../../`

npm ERR!
 Exit status 101

npm ERR!
 
npm
 ERR!
 Failed at the beaker-plugin-safe-authenticator@0.1.0 build-native-mock script.
npm
 ERR!
 This is probably not a problem with npm. There is likely additional logging output above.




npm ERR! A complete log of this run can be found in:
npm ERR!     /home/folatt/.npm/_logs/2017-07-09T12_16_00_590Z-debug.log


npm
 ERR! code ELIFECYCLE
npm ERR! errno 101
npm ERR! beaker-plugin-safe-authenticator@0.1.0 build-libs:mock: `npm run build-native-mock && npm run build-system-uri`
npm ERR! Exit status 101
npm ERR! 
npm ERR!
 Failed at the beaker-plugin-safe-authenticator@0.1.0 build-libs:mock script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.




npm ERR! A complete log of this run can be found in:
npm ERR!     /home/folatt/.npm/_logs/2017-07-09T12_16_00_612Z-debug.log


Build Authenticator exited with code 101

npm
 
ERR!
 
code
 ELIFECYCLE
npm ERR! errno 101

npm
 ERR!
 beaker-plugin-safe-authenticator@0.1.0 build-libs: `npm run init-submodule && node ./build_libs.js "--features=mock-routing"`
npm 
ERR!
 Exit status 101

npm 
ERR!
 

npm
 ERR!
 Failed at the beaker-plugin-safe-authenticator@0.1.0 build-libs script.

npm 
ERR!
 This is probably not a problem with npm. There is likely additional logging output above.



npm ERR! A complete log of this run can be found in:
npm ERR!     /home/folatt/.npm/_logs/2017-07-09T12_16_00_655Z-debug.log

npm
 ERR!
 missing script: copy-bin:unix



npm ERR! A complete log of this run can be found in:
npm ERR!     /home/folatt/.npm/_logs/2017-07-09T12_16_01_220Z-debug.log

npm
 ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ pack-authenticator:unix: `sh ./scripts/pack_authenticator.sh ""`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @ pack-authenticator:unix script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.


npm
 ERR! A complete log of this run can be found in:
npm ERR!     /home/folatt/.npm/_logs/2017-07-09T12_16_01_261Z-debug.log

Pack Authenticator exited with code 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ pack-authenticator: `node ./scripts/main.js --authenticator`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @ pack-authenticator script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/folatt/.npm/_logs/2017-07-09T12_16_01_303Z-debug.log

Are you on rustc stable? See my post for the versions I’m using, which got further than this.

I’m using rustup 1.5.0-1
rustc 1.18.0 (03fc9d622 2017-06-06)

I don’t think that’s rustc stable, so check.

My 2 cents see if you can be added to invite list. Otherwise just wait for more tests.

I have a local network running since yesterday and I’m slowly building my small site :slight_smile: .

5 Likes

See there ya go buddy :wink:

Is there anything we may be able to see on this?

1 Like

How you did that? Can you share?

1 Like

This currently requires modifying the source code, building it yourself, and using binaries currently only available in private testing. I think that maidsafe intend to make this easier for developers who need it though, so keep an eye on the developer updates (every Thursday by about 20:00 GMT, unless David keeps @Krishna_Kumar & @Shankar up through the night like last week, when 11pm for us meant 4am for them!)

4 Likes

I made a safe_vault fork allowing local networks. See instructions here.

To get the client binaries to access the network you need to reach the trust level 2 in this forum.

4 Likes