Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

"parity account new" errors when executed as a subprocess #3355

Closed
jesuscript opened this issue Nov 10, 2016 · 0 comments
Closed

"parity account new" errors when executed as a subprocess #3355

jesuscript opened this issue Nov 10, 2016 · 0 comments
Assignees
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust.

Comments

@jesuscript
Copy link
Contributor

test.js

var newAccount = require("child_process").spawn("parity", ["account","new"]) //, ["account", "new"])

newAccount.stdout.on("data", function(data){
  console.log("out:", data.toString())
})
newAccount.stderr.on("data", function(data){
  console.log("err:", data.toString())
})
$ node test.js 
out: Please note that password is NOT RECOVERABLE.
Type password: 
err: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 102, message: "Operation not supported on socket" } }', ../src/libcore/result.rs:788
stack backtrace:
   1:        0x10f9e7759 - std::sys::backtrace::tracing::imp::write::h00e948915d1e4c72
   2:        0x10f9ee640 - std::panicking::default_hook::_{{closure}}::h7b8a142818383fb8
   3:        0x10f9ed4a0 - std::panicking::default_hook::h41cf296f654245d7
   4:        0x10f9edb26 - std::panicking::rust_panic_with_hook::h4cbd7ca63ce1aee9
   5:        0x10f9ed974 - std::panicking::begin_panic::h93672d0313d5e8e9
   6:        0x10f9ed8d2 - std::panicking::begin_panic_fmt::hd0daa02942245d81
   7:        0x10f9ed837 - rust_begin_unwind
   8:        0x10fa1b610 - core::panicking::panic_fmt::hbfc935564d134c1b
   9:        0x10ee726e5 - core::result::unwrap_failed::h5143d39947ff2959
  10:        0x10efb5886 - parity::helpers::password_prompt::h2a453c1785756296
  11:        0x10efde01e - parity::execute::h80f1f82d966d99e4
  12:        0x10efe697d - parity::main::h76ea6e55af3730d3
  13:        0x10f9eec2a - __rust_maybe_catch_panic
  14:        0x10f9ecf6e - std::rt::lang_start::h53bf99b0829cc03c
@jesuscript jesuscript added the F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. label Nov 10, 2016
@rphmeier rphmeier added the M4-core ⛓ Core client code / Rust. label Nov 10, 2016
@tomusdrw tomusdrw self-assigned this Nov 11, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust.
Projects
None yet
Development

No branches or pull requests

3 participants