tried on ubuntu 20.04LTS build the essential installed rust and then exec bash to refresh the terminal and then
cargo install vdash
get two errors
error[E0599]: no function or associated item named `new_immediate` found for trait object `dyn Watcher` in the current scope
--> /home/smoothie/.cargo/registry/src/github.com-1ecc6299db9ec823/linemux-0.1.3/src/events.rs:61:64
|
61 | let inner: notify::RecommendedWatcher = NotifyWatcher::new_immediate(move |res| {
| ^^^^^^^^^^^^^ function or associated item not found in `dyn Watcher`
error[E0308]: mismatched types
--> /home/smoothie/.cargo/registry/src/github.com-1ecc6299db9ec823/linemux-0.1.3/src/events.rs:90:20
|
88 | fn watch(watcher: &mut notify::RecommendedWatcher, path: impl AsRef<Path>) -> io::Result<()> {
| ---------------- this type parameter
89 | watcher
90 | .watch(path, notify::RecursiveMode::NonRecursive)
| ^^^^ expected `&Path`, found type parameter `impl AsRef<Path>`
|
= note: expected reference `&Path`
found type parameter `impl AsRef<Path>`
error[E0308]: mismatched types
--> /home/smoothie/.cargo/registry/src/github.com-1ecc6299db9ec823/linemux-0.1.3/src/events.rs:95:25
|
94 | fn unwatch(watcher: &mut notify::RecommendedWatcher, path: impl AsRef<Path>) -> io::Result<()> {
| ---------------- this type parameter
95 | watcher.unwatch(path).map_err(notify_to_io_error)
| ^^^^ expected `&Path`, found type parameter `impl AsRef<Path>`
|
= note: expected reference `&Path`
found type parameter `impl AsRef<Path>`
Some errors have detailed explanations: E0308, E0599.
For more information about an error, try `rustc --explain E0308`.
error: could not compile `linemux` due to 3 previous errors
warning: build failed, waiting for other jobs to finish...
error: failed to compile `vdash v0.6.3`, intermediate artifacts can be found at `/tmp/cargo-installaNeulF`
Caused by:
build failed
I thought it might be good to have a room for vdash chat: https://matrix.to/#/#vdash:matrix.org (once there you can sign-in or sign-up if you aren’t already).
Collaborate (& Learn Rust If you like)
I don’t have much time for code now so happy for people to fork and chip in or take this forward yourself. I’ll help you learn along the way too when I have time.
To start, see how far you can get by forking the repo, building and setting up a development environment if you don’t have one yet. Then let me know what you’ve managed and anything you need help with.
vdash v0.7.0 has been released and now works again with all test networks. There’s more work to do and I’m not sure how reliable what it shows you is yet but it is ready to try out.
Note:
nodes must be started with: RUST_LOG=sn_node=trace safe node join #etc
same when starting a local test network
logfiles must be in default format (text not JSON)
Feedback and help updating welcome in exchange for free Rust coaching (free and worth every penny ). See the OP for more:
willie@gagarin:~/projects/maidsafe/ELK$ cargo install dash
Updating crates.io index
Downloaded dash v0.1.0
Downloaded 1 crate (4.6 KB) in 1.00s
Installing dash v0.1.0
error: failed to compile `dash v0.1.0`, intermediate artifacts can be found at `/tmp/cargo-installJGScfL`
Caused by:
failed to select a version for the requirement `clap = "~2.19.0"`
candidate versions found which didn't match: 3.0.14, 3.0.13, 3.0.12, ...
location searched: crates.io index
required by package `dash v0.1.0`
Some issues for anyone wanting to learn a bit of Rust while helping out with vdash:
There’s also some relatively simple refactoring to do, but the things I’ve made issues should be more fun because they are enhancements, rather than refactoring.
This has minimal changes but should once again display some useful information taken from the logfiles. I’ll be interested if anyone tries it out, to tell me what is still not displayed as I’ve done very little testing. Also useful if you tell me what it does seem to display correctly! I’ve seen it show ‘role’ (e.g. ‘Elder’), PUTS an ERRORS.
For newbies or general information about vdash, see the OP
I am assuming the errors are coming from the faceful of OTLP errors that are getting spewed everywhere for now.
THis is with the release from a day or so back, I am not on the latest release yet - and if I was, I believe safe node run-baby-fleming would not work as expected?
On a std 11 node baby-fleming, every node is reported as an Elder of age zero. I am unsure if this is all or partially down to vdash.
The chunk bar top centre/right always shows 100%, however the storage figure next to it looks plausible.
Role appears as always Elder, Age is zero and no values for Name and Section. But I cant remember how much of this worked last time anyway. ISTR Role and Age being accurate though…
Values for Device Space Avail and Free are all zero and the Load values are also zero.
You seem to have the same results as I did but only ran briefly, put a handful of files. Let’s see if anything improves with a split and running for longer. I think some more info should start to be shown, so let me know if you see anything improve.
I’m not sure if the ‘run-baby-fleming’ issue is real or not. I did the install using the MaidSafe script and manual install of the relevant node version but can’t see how the problem would arise looking at the source. So
). See the OP for more:
makes not watching even more fun 
