Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 19 16:16
    dvdplm synchronize #11178
  • Oct 19 16:16

    dvdplm on fix

    Fix tests (compare)

  • Oct 19 16:06
    dvdplm edited #11178
  • Oct 19 13:05
    niklasad1 edited #11184
  • Oct 19 12:16
    niklasad1 milestoned #11184
  • Oct 19 12:16
    niklasad1 labeled #11184
  • Oct 19 12:16
    niklasad1 labeled #11184
  • Oct 19 12:16
    niklasad1 labeled #11184
  • Oct 19 12:15
    niklasad1 edited #11184
  • Oct 19 12:15
    niklasad1 opened #11184
  • Oct 19 12:14

    dvdplm on na-bump-jsonrpc

    (compare)

  • Oct 19 12:14

    dvdplm on master

    [dependencies]: jsonrpc `14.0.1… (compare)

  • Oct 19 12:14
    dvdplm closed #11183
  • Oct 19 12:14
    dvdplm closed #11169
  • Oct 19 12:14
    dvdplm commented #11183
  • Oct 19 12:01
    niklasad1 labeled #11183
  • Oct 19 12:01
    niklasad1 commented #11183
  • Oct 19 12:01
    niklasad1 commented #11183
  • Oct 19 10:35
    afck synchronize #10928
  • Oct 19 10:33
    niklasad1 labeled #11183
Bob Summerwill
@bobsummerwill
C++ gitbook and TurboEthereum content being moved to:
http://docs.ethereum.org/en/latest/ethereum-clients/cpp-ethereum/index.html
Nikhil M
@niksmac
yes, though we're still finishing off the underlying jsonrpc interface, so some parts of web3.js may not yet work
thanks ...
markrtgh
@markrtgh
Previous build was working fine for syncing with mainnet and testnet but got this after git pull, cargo update then cargo build --release
   Compiling ethcore-util v0.9.99 (file:///Users/me/Documents/rust/parity)
util/src/lib.rs:19:49: 19:55 error: can't find crate for `clippy` [E0463]
util/src/lib.rs:19 #![cfg_attr(all(nightly, feature="dev"), plugin(clippy))]
                                                                   ^~~~~~
error: aborting due to previous error
Build failed, waiting for other jobs to finish...
Could not compile `ethcore-util`.
Tomasz Drwięga
@tomusdrw
We've changed a setup a little bit. Building on nightly requires additional flag --features dev-clippy
Try cargo build --release --features dev-clippy
markrtgh
@markrtgh
Thanks, that got clippy but then got new errors, first one
   Compiling clippy v0.0.44
/Users/me/.multirust/toolchains/nightly/cargo/registry/src/github.com-88ac128001ac3a9a/clippy-0.0.44/src/utils/hir.rs:171:15: 171:27 error: unresolved enum variant, struct or const `Box` [E0419]
/Users/me/.multirust/toolchains/nightly/cargo/registry/src/github.com-88ac128001ac3a9a/clippy-0.0.44/src/utils/hir.rs:171             (&PatKind::Box(ref l), &PatKind::Box(ref r)) => {
                                                                                                                                                ^~~~~~~~~~~~
snip

error: aborting due to 22 previous errors
Build failed, waiting for other jobs to finish...
Could not compile `clippy`
Tomasz Drwięga
@tomusdrw
So you are using latest nightly and we have old version of clippy in dependencies. I will prepare a PR to update clippy dependency to build on latest nightly.
markrtgh
@markrtgh
OK
Tomasz Drwięga
@tomusdrw
For now you either need to build on beta, use older nightly or modify Cargo.toml a bit
Removing [dev-dependencies] section from Cargo.toml and building without features flag should work.
markrtgh
@markrtgh
Removing [dev-dependencies] section worked. Syncing now into dir v5.1-sec-archive in .parity instead of v5.1-sec-pruned.
Gav Wood
@gavofyork
yeah - we've changed the default behaviour from pruning to archive
if you want to continue using pruning, you can run with --pruning
however, it should be considered experimental
rollick
@rollick
I am getting the following when building master:

Build failed, waiting for other jobs to finish... failed to run custom build command forlibrocksdb-sys v0.2.2 (https://github.com/arkpar/rust-rocksdb.git#a4f89fea)`
Process didn't exit successfully: /root/parity/target/release/build/librocksdb-sys-769b437c49d7a014/build-script-build (exit code: 1)
--- stdout
cargo:rustc-flags=-l stdc++
cargo:rustc-link-lib=static=rocksdb

--- stderr
build failed:
make: No rule to make target 'include/rocksdb/delete_scheduler.h', needed by 'db/db_impl.o'. Stop.
make:
Waiting for unfinished jobs....
`

Hmm, formatting fail...
Oh, it looks like I did a cargo update at some point. Ignore me...
Nikhil M
@niksmac

yes, though we're still finishing off the underlying jsonrpc interface, so some parts of web3.js may not yet work

some part means? is it documented anywhere so that i can have a look? please let me know

@gavofyork ?
Nick MORTER
@Nock-zz
Is there a javascript console. If so what command do I sue to start it.
*use
Also I have tried to use the rpc interface, some methods work but a number do not e.g.
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getBalance","params”:[“<my account>“, "latest"],"id":1}' http://127.0.0.1:<myport>
Gav Wood
@gavofyork
yes - @debris is still finishing up on the jsonrpc - if there are any in particular you need, let us know here and we'll do our best to get them in sooner
we don't yet have a javascript interface, however it should be possible to use eth console or geth console to connect to a running parity client
i haven't tried that yet, though...
Gav Wood
@gavofyork
@niksmac @debris can state precisely which parts are implemented. the mining methods are done, as are those which are required for netstats to work
the rest is WiP, but we're aiming for full compatibility in the 1.0 series.
Nate Geier
@nategeier
Is there a Parity hello world anywhere? I have it running, but not sure where to go next.
Gav Wood
@gavofyork
not really; we'll be putting up some tutorials once version 1.0 is out, but right now the closest you'll get to a hello world is inspecting parity's main.rs
there's code there that sets up a client
but we're still finishing up some of the important groundwork for 1.0, so there's no final developer API except the JSONRPC API
rollick
@rollick
I am trying to build master but getting the following:
failed to run custom build command for `librocksdb-sys v0.2.1 (https://github.com/arkpar/rust-rocksdb.git#2156621f)`
Process didn't exit successfully: `/root/parity/target/release/build/librocksdb-sys-e8861db500492e45/build-script-build` (exit code: 1)
--- stdout
cargo:rustc-flags=-l stdc++
cargo:rustc-link-lib=static=rocksdb

--- stderr
build failed:
make: *** No rule to make target 'util/sst_file_manager_impl.h', needed by 'db/compaction_job.o'.  Stop.
make: *** Waiting for unfinished jobs....
rollick
@rollick
I am on cargo 0.9.0-nightly (8fc3fd8 2016-02-29)
Gav Wood
@gavofyork
a fix is on its way. current workaround is rm -rf ~/.multirust/toolchains/*/cargo/git/checkouts/rust-rocksdb-*
rollick
@rollick
Cool and should I be sticking with master?
Gav Wood
@gavofyork
yeah - beta has a known issue that is fixed in master
we'll be releasing 1.0pre1 in the near future
Bob Summerwill
@bobsummerwill
Would you like me to link to 1.0pre1 from https://ethereum-homestead.readthedocs.org/en/latest/using-ethereum-the-basics/installing-a-client.html when that comes out, @gavofyork?
Also just about to create stub content at https://ethereum-homestead.readthedocs.org/en/latest/ethereum-clients/parity/parity.html. We're doing a paragraph summary plus links for each client, at least.
Nick MORTER
@Nock-zz
Thank you for your reply [yes - @debris is still finishing up on the jsonrpc - if there are any in particular you need, let us know here and we'll do our best to get them in sooner
we don't yet have a javascript interface, however it should be possible to use eth console or geth console to connect to a running parity client] For jsonrpc, my first preference is for "eth_getBalance". As for geth console I have tried: geth attach rpc:http://127.0.0.1:<my parity rpc port> and this fails with invalid response. When I tried on geth with: geth attach rpc:http://127.0.0.1:<my geth rpc port> then this works. I do not see a .ipc file for parity so I have not tried: geth attach ipc:some path
Gav Wood
@gavofyork
yes - we do not presently support geth's IPC; that is a stretch goal for our civility release, an approximately two months' time.
Gav Wood
@gavofyork
@bobsummerwill yes please - we're still working hard on getting the 1.0pre release done - i'll be sure to mention it here once it's ready :)
Gav Wood
@gavofyork
regarding attacjing a javascript console, i haven't yet tried with geth attach, but eth attach works fine.
Fernando Paredes García
@develCuy
is parity binary compatible with client-go ?
I wont like to download blockchain again
Gav Wood
@gavofyork
the database is not compatible - redownloading the blockchain is necessary at present, though it's a lot faster (less than an hour on a modern computer).
Sax Cottingham
@saxis
Will parity be Mist compatible eventually?