1. 25 Dec, 2020 1 commit
  2. 07 Dec, 2020 1 commit
  3. 03 Dec, 2020 1 commit
  4. 24 Nov, 2020 1 commit
  5. 20 Nov, 2020 1 commit
    • Peter Goodspeed-Niklaus's avatar
      Add tracing support to node (#1940) · f7ea3d07
      Peter Goodspeed-Niklaus authored
      * drop in tracing to replace log
      
      * add structured logging to trace messages
      
      * add structured logging to debug messages
      
      * add structured logging to info messages
      
      * add structured logging to warn messages
      
      * add structured logging to error messages
      
      * normalize spacing and Display vs Debug
      
      * add instrumentation to the various 'fn run'
      
      * use explicit tracing module throughout
      
      * fix availability distribution test
      
      * don't double-print errors
      
      * remove further redundancy from logs
      
      * fix test errors
      
      * fix more test errors
      
      * remove unused kv_log_macro
      
      * fix unused variable
      
      * add tracing spans to collation generation
      
      * add tracing spans to av-store
      
      * add tracing spans to backing
      
      * add tracing spans to bitfield-signing
      
      * add tracing spans to candidate-selection
      
      * add tracing spans to candidate-validation
      
      * add tracing spans to chain-api
      
      * add tracing spans to provisioner
      
      * add tracing spans to runtime-api
      
      * add tracing spans to availability-distribution
      
      * add tracing spans to bitfield-distribution
      
      * add tracing spans to network-bridge
      
      * add tracing spans to collator-protocol
      
      * add tracing spans to pov-distribution
      
      * add tracing spans to statement-distribution
      
      * add tracing spans to overseer
      
      * cleanup
      f7ea3d07
  6. 17 Nov, 2020 1 commit
    • Andronik Ordian's avatar
      update most of the dependencies (#1946) · 31fb8fed
      Andronik Ordian authored
      * update tiny-keccak to 0.2
      
      * update deps except bitvec and shared_memory
      
      * fix some warning after futures upgrade
      
      * remove useless package rename caused by bug in cargo-upgrade
      
      * revert parity-util-mem *
      
      * remove unused import
      
      * cargo update
      
      * remove all renames on parity-scale-codec
      
      * remove the leftovers
      
      * remove unused dep
      31fb8fed
  7. 09 Nov, 2020 1 commit
  8. 02 Nov, 2020 1 commit
    • Bastian Köcher's avatar
      Adder collator improvements (#1896) · 96465b04
      Bastian Köcher authored
      * Fixes bug that collator wasn't sending `Declare` message
      
      * Set authority discovery config
      
      * Fixes bug that collator wasn't sending `Declare` message
      
      * Adds real overseer feature and makes the wasm_validation fail with a
      proper error
      
      * Adds README
      
      * Remove debug stuff
      
      * Add feature
      
      * Make adder collator use the correct parent when building a new block
      96465b04
  9. 27 Oct, 2020 1 commit
  10. 25 Oct, 2020 1 commit
  11. 21 Oct, 2020 1 commit
  12. 16 Oct, 2020 1 commit
  13. 08 Oct, 2020 1 commit
    • Peter Goodspeed-Niklaus's avatar
      Remove old service, 3rd try (#1776) · ba0d1a32
      Peter Goodspeed-Niklaus authored
      * Remove old service, 3rd try
      
      i.e.
      Revert "Revert "Remove Old Service, 2nd try (#1732)" (#1758)"
      
      This reverts commit c80f7b6b.
      
      Closes #1757.
      
      We now have some evidence that the polkadot validator was producing
      blocks after all; the reason the blocks_constructed metric was 0 was
      that as a new metric it hadn't yet been incorporated into that
      branch's codebase. See
      https://github.com/paritytech/polkadot/issues/1757#issuecomment-700977602
      
      
      
      As this PR is based on a newer `master` branch than the previous one,
      that should hopefully no longer be an issue.
      
      * paras trait now has an Origin type
      
      * initial work running a two node local net
      
      * use the right incantations so the nodes produce blocks together
      
      * improve internal documentation
      
      Co-authored-by: Bastian Köcher's avatarBastian Köcher <git@kchr.de>
      ba0d1a32
  14. 28 Sep, 2020 2 commits
  15. 18 Sep, 2020 2 commits
    • Peter Goodspeed-Niklaus's avatar
      c68aee35
    • Peter Goodspeed-Niklaus's avatar
      Remove service, migrate all to service-new (#1630) · af14ea54
      Peter Goodspeed-Niklaus authored
      * import rococo into chain-spec
      
      * make a few stabs at moving forward
      
      * wip: rococo readme
      
      * remove /service crate
      
      - Move the chain-spec files to node-service
      - update sufficient cargo files that polkadot-service-new builds
      - not everything else builds yet
      
      * wip: chase down some build errors in polkadot-cli
      
      There's a lot more to go, but some progress has happened.
      
      * make more progress getting polkadot-cli to build
      
      * don't ignore polkadot.json within the res directory
      
      * don't recreate pathbufs
      
      * Prepare Polkadot to be used by Cumulus
      
      This begins to make Polkadot usable from Cumulus.
      
      * Remove old test
      
      * migrate new_chain_ops fix from /service
      
      * partially remove node/test-service
      
      * Reset some changes
      
      * Revert "partially remove node/test-service"
      
      This reverts commit 7b8f9ba5.
      
      * WIP: replace v0 ParachainHost impl with v1 for test runtime
      
      This is necessary because one of the current errors when building
      the test service boils down to:
      
      the trait bound `polkadot_test_runtime::RuntimeApiImpl<...>`:
        `polkadot_primitives::v1::ParachainHost<...>` is not satisfied
      
      This is WIP because it appears to be causing some std leakage into
      the wasm environment, or something; the compiler is currently
      complaining about duplicate definitions of `panic_handler` and `oom`.
      Presumably I have to identify all std types (Vec etc) and replace
      them with sp_std equivalents.
      
      * fix test runtime build
      
      it wasn't std leakage, after all
      
      * bump westend spec version
      
      * use service-new as service within cli
      
      * to revert: demo that forwarding the test runtime to the real impl blows up
      
      * Revert "to revert: demo that forwarding the test runtime to the real impl blows up"
      
      This reverts commit 68d2f385.
      
      * Revert "Revert "to revert: demo that forwarding the test runtime to the real impl blows up""
      
      This reverts commit 04cb1cbf.
      
      Might have just forgotten to disable default features
      
      * More reverts
      
      * MOARE
      
      * plug in the runtime as the generic instantiation
      
      This feels closer to a solution, but it still has problems: in particular,
      it's assumed that Runtime implements all appropriate Trait traits,
      which this one apparently does not.
      
      * implement necessary traits to get the test runtime compiling
      
      This is almost certainly not correct in some way; it really
      looks like I need to mess with the construct_runtime! macro
      somehow, to inject the inclusion trait's event type as a Event
      variant. Still, better lock down this changeset while it all
      compiles.
      
      * add inclusion::Event as variant into Event enum
      
      * implement unimplemented bits in kusama
      
      * implement unimplemented bits in polkadot runtime
      
      * implement unimplemented bits in westend runtime
      
      * migrate client upgrades from master
      
      * update test service with new node changes
      
      * package metadata--that wasn't intended to be removed
      
      * add parachains v1 modules to each runtime
      
      It's not clear what precisely this does, but it's probably the right
      thing to do.
      
      * enable cli to opt out of full node features
      
      * adjust rococo chainspec per example
      
      https://github.com/paritytech/polkadot/blob/26f1fa47f7836ab4bee5d4aad127ebce748320dd/service/src/chain_spec.rs#L362
      
      
      
      * try to fix Cargo.lock
      
      Co-authored-by: Bastian Köcher's avatarBastian Köcher <git@kchr.de>
      Co-authored-by: Andronik Ordian's avatarAndronik Ordian <write@reusable.software>
      af14ea54
  16. 24 Aug, 2020 1 commit
  17. 13 Aug, 2020 1 commit
  18. 09 Jul, 2020 1 commit