Pre-Dev-Update Thread! Yay! :D

Development Updates
243

me

/overlyoptimistic4life

5 Likes
244

hmm - but with easter and (including the weekend) 4/7 days being holidays … then there is the day of the update itself Oo … so … 2 days of the week left for development since the last update Oo … let’s hope those where 2 impressing days :smiley:

1 Like
245

From the Github notifications I’ve received this morning and from the past couple of days, the teams seems to still be going full speed ahead and seeing some very exciting things!

:slight_smile: :slight_smile: :slight_smile: :slight_smile:

Might be why I am in such an awesome mood today!

5 Likes
246

okay then! i’m always looking forward to tuesdays!!! :smiley: (how about leaking when the roadmap gets merged into the master branche …? :nerd: i can’t wait to see it online =D )

EDIT: holy moly - i just recognized Oo … did you run the tests on the safe_vaults repo …? Oo

377×679 62.9 KB

[…]

OVERALL PASSED :hugging:

15 Likes
247

4 Likes
248

It didn’t pass last week?

249

here at my pc they always got stuck somewhere in the testing process before today Oo

for you they did pass all the time …?

1 Like
250

Haven’t been playing with it for months, so don’t know. Just curious if it’s something new :slight_smile:

1 Like
251

hahaha - yes ok i understand :smiley:

posting it without it being something new would have been … a little bit funny xD … :nerd: :poop:

252

Haha that’s true :stuck_out_tongue: :stuck_out_tongue:

253

ps: i was a little bit afraid to run the test again … but i did it now … it stopps at the first point “putting immutable data” now :open_mouth: … we’ll see what happens tomorrow … seems like there is good progress anyway :slight_smile:

254

@riddim What platform are you on?

255

ubuntu 14.04lts …

1 Like
256

Thanks. I am getting a compilation error of safe_vault under Windows 7.

PS C:\Users\user\projects\safe_vault> cargo build
Compiling bitflags v0.3.3
Compiling libc v0.1.12
Compiling slab v0.1.3
Compiling bitflags v0.5.0
Compiling xml-rs v0.1.26
Compiling nix v0.4.2
Compiling typeable v0.1.2
Compiling libsodium-sys v0.0.9
Build failed, waiting for other jobs to finish…
error: failed to run custom build command for libsodium-sys v0.0.9
Process didn’t exit successfully: C:\Users\user\projects\safe_vault\target\debu g\build\libsodium-sys-4773428f8ea4b5cb\build-script-build (exit code: 101)
— stderr
thread ‘’ panicked at ‘called Result::unwrap() on an Err value: “Cross
compilation detected. Use PKG_CONFIG_ALLOW_CROSS=1 to override”’, …/src/libcor
e\result.rs:746

Any ideas, anyone?

257

Did you do cargo update ?

1 Like
258

Thanks for your response. I did so just now and the error is exactly the same.

259

Looks like there is an issue with libsodium. Do you know if that is installed as per the README in the repo? https://github.com/maidsafe/QA/blob/master/Documentation/Install%20libsodium%20for%20Windows.md It has caught out a few folks.

260

Thanks! That got me much further (a clear case of RTFM on my part). But now it fails at this point, and I can’t find out anything about “igd”:

PS C:\Users\user\projects\safe_vault> cargo update
Updating registry https://github.com/rust-lang/crates.io-index
PS C:\Users\user\projects\safe_vault> cargo build
Compiling regex-syntax v0.3.1
Compiling socket_addr v0.1.0
Compiling uuid v0.1.18
Compiling kernel32-sys v0.2.1
Compiling term v0.4.4
Compiling fs2 v0.2.3
Compiling url v0.2.38
Compiling config_file_handler v0.2.1
Compiling num v0.1.31
Compiling ctrlc v1.1.1
Compiling time v0.1.34
Compiling lru_time_cache v0.2.7
Compiling cookie v0.1.21
Compiling accumulator v0.2.0
Compiling bincode v0.5.1
Compiling serde v0.6.15
Compiling libsodium-sys v0.0.9
Compiling sodiumoxide v0.0.9
Compiling ws2_32-sys v0.2.1
Compiling net2 v0.2.23
Compiling miow v0.1.2
Compiling mime v0.1.3
Compiling mio v0.5.0
Compiling message_filter v0.3.1
Compiling hyper v0.6.16
Compiling regex v0.1.59
Compiling env_logger v0.3.2
Compiling temp_utp v0.8.0
Compiling maidsafe_utilities v0.4.1
Compiling docopt v0.6.78
Compiling xor_name v0.1.0
Compiling kademlia_routing_table v0.4.0
Compiling service_discovery v0.3.0
Compiling chunk_store v0.3.0
Compiling safe_network_common v0.0.1
Compiling igd v0.4.2
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/m
aster/CONTRIBUTING.md#bug-reports
note: run with RUST_BACKTRACE=1 for a backtrace
thread ‘rustc’ panicked at ‘assertion failed: declare::get_defined_value(ccx, &s
ymbol).is_none()’, …/src/librustc_trans\monomorphize.rs:94
note: Run with RUST_BACKTRACE=1 for a backtrace.

Build failed, waiting for other jobs to finish…
error: Could not compile igd.

261

Ah igd lib (a dependency) did have an issue I heard of earlier. There is a way around it AFAIK, but it means go into your cargo.toml and setting the version to a previous one using the = in front of the version number. Unless you are desperate it may not be worth the effort right now though. IGD will probably upgrade, of course you can make that change if you really want to :wink:

3 Likes
262

Thanks, but it has me stumped:

I cannot stop it downloading and trying to compile igd 0.4.2 (the latest one).

I added igd 0.3.0 as a dependency in the Cargo.toml and deleted igd 0.4.2 from the .cargo folder’s registry folder. Cargo then downloaded igd 0.3.1 (presumably the closest 0.3.x subversion available) and included it in the compile process along with igd 0.4.2!

I searched online and have not been able to find much on specifying earlier crate versions in a compilation. I’ll call it a night tonight.