openethereum/js-old
Marek Kotewicz fa6a0a6b60 Backports to beta (#7660)
* Improve handling of RocksDB corruption (#7630)

* kvdb-rocksdb: update rust-rocksdb version

* kvdb-rocksdb: mark corruptions and attempt repair on db open

* kvdb-rocksdb: better corruption detection on open

* kvdb-rocksdb: add corruption_file_name const

* kvdb-rocksdb: rename mark_corruption to check_for_corruption

* Hardening of CSP (#7621)

* Fixed delegatecall's from/to (#7568)

* Fixed delegatecall's from/to, closes #7166

* added tests for delegatecall traces, #7167

* Light client RPCs (#7603)

* Implement registrar.

* Implement eth_getCode

* Don't wait for providers.

* Don't wait for providers.

* Fix linting and wasm tests.

* Problem: AttachedProtocols don't get registered (#7610)

I was investigating issues I am having with Whisper support. I've
enabled Whisper on a custom test network and inserted traces into
Whisper handler implementation (Network<T> and NetworkProtocolHandler
for Network<T>) and I noticed that the handler was never invoked.

After further research on this matter, I found out that
AttachedProtocol's register function does nothing:
https://github.com/paritytech/parity/blob/master/sync/src/api.rs#L172
but there was an implementation originally:
99075ad#diff-5212acb6bcea60e9804ba7b50f6fe6ec and it did the actual
expected logic of registering the protocol in the NetworkService.

However, as of 16d84f8#diff-5212acb6bcea60e9804ba7b50f6fe6ec ("finished
removing ipc") this implementation is gone and only the no-op function
is left.

Which leads me to a conclusion that in fact Whisper's handler never gets
registered in the service and therefore two nodes won't communicate
using it.

Solution: Resurrect original non-empty `AttachedProtocols.register`
implementation

Resolves #7566

* Fix Temporarily Invalid blocks handling (#7613)

* Handle temporarily invalid blocks in sync.

* Fix tests.
2018-01-23 12:32:34 +01:00
..
assets Update branding on UI (#7370) 2018-01-02 09:48:41 +01:00
scripts [beta] Trigger js-precompiled (#7535) 2018-01-11 13:27:01 +01:00
src Backports to beta (#7660) 2018-01-23 12:32:34 +01:00
test Update mocha import stubs (#7191) 2017-12-05 09:03:30 +01:00
wasm Integrate old UI. 2017-10-17 16:09:43 +02:00
webpack Upgrade markdown-loader & marked (#7467) 2018-01-05 10:59:35 +01:00
.babelrc Integrate old UI. 2017-10-17 16:09:43 +02:00
.codeclimate.yml Integrate old UI. 2017-10-17 16:09:43 +02:00
.editorconfig Integrate old UI. 2017-10-17 16:09:43 +02:00
.eslintrc.json Integrate old UI. 2017-10-17 16:09:43 +02:00
.gitignore Integrate old UI. 2017-10-17 16:09:43 +02:00
.istanbul.yml Integrate old UI. 2017-10-17 16:09:43 +02:00
.npmignore Integrate old UI. 2017-10-17 16:09:43 +02:00
.npmrc Integrate old UI. 2017-10-17 16:09:43 +02:00
.stylelintrc.json Integrate old UI. 2017-10-17 16:09:43 +02:00
build.rs Integrate old UI. 2017-10-17 16:09:43 +02:00
Cargo.precompiled.toml Integrate old UI. 2017-10-17 16:09:43 +02:00
Cargo.toml Integrate old UI. 2017-10-17 16:09:43 +02:00
LICENSE Integrate old UI. 2017-10-17 16:09:43 +02:00
package-lock.json Update package-lock in js-old (#7494) 2018-01-08 09:45:07 +01:00
package.json Upgrade markdown-loader & marked (#7467) 2018-01-05 10:59:35 +01:00
README.md Integrate old UI. 2017-10-17 16:09:43 +02:00

parity.js

JavaScript APIs and UIs for Parity.

development

  1. Install Node if not already available
  2. Change to the js directory inside parity/
  3. Install the npm modules via npm install
  4. Parity should be run with parity --ui-no-validation [...options] (where options can be --chain testnet)
  5. Start the development environment via npm start
  6. Connect to the UI