Skip to content
  1. Feb 02, 2021
  2. Feb 01, 2021
    • Pierre Krieger's avatar
      de838f94
    • Alexander Popiak's avatar
      49e853c1
    • Max Inden's avatar
      client/network: Use request response for light client requests (#7895) · 30061009
      Max Inden authored
      * client/network: Re-enable light_client_handler.rs unit tests
      
      * client/network: Add scaffolding for light client using req-resp
      
      * client/network: Make it compile
      
      * client/network: Rename OutEvent SendRequest
      
      * client/network: Restructure light client request client and handler
      
      * client/network: Rename light client request client to sender
      
      * client/network: Remove light client prepare_request
      
      * client/network/src/light: Rework configuration
      
      * client/network: Formatting
      
      * client/network/light: Remove RequestId
      
      * client/network/light: Make request functions methods
      
      * client/network/light: Refactor request wrapping
      
      * client/network/light: Fix warnings
      
      * client/network/light: Serialize request in method
      
      * client/network/light: Make returning response a method
      
      * client/network/light: Depend on request response to timeout requests
      
      * client/network: Fix test compilation
      
      * client/network/light: Re-enable connection test
      
      * client/network/light: Re-enable timeout test
      
      * client/network/light: Re-enable incorrect_response test
      
      * client/network/light: Re-enable wrong_response_type test
      
      * client/network/light: Re-enable retry_count_failures test
      
      * client/network/light: Re-enable issue_request tests
      
      * client/network/light: Re-enable send_receive tests
      
      * client/network/light: Deduplicate test logic
      
      * client/network/light: Remove unused imports
      
      * client/network/light: Handle request failure
      
      * client/network/light: Move generate_protocol_config
      
      * client/network: Fix test compilation
      
      * client/network: Rename light client request client to sender
      
      * client/network: Handle too-many-requests error
      
      * client/network: Update outdated comments
      
      * client/network/light: Choose any peer if none has best block defined
      
      * .maintain: Replace sentry-node with local-docker-test-network
      
      Sentry nodes are deprecated. Thus there is no need for
      `.maintain/sentry-node` to spin up a sentry node test environment.
      Instead this commit rewrites the setup to contain two full-connected
      validators and one light client.
      
      With the steps below one can now spin up a local test network with
      two validators, one light-client, Prometheus and Grafana.
      
      - cargo build --release
      - sudo docker-compose -f .maintain/local-docker-test-network/docker-compose.yml up
      
      * client/network/light: Handle oneshot cancellation
      
      * client/network/light: Do not reduce retry count on missing peer
      
      * client/network/request-response: Assert in debug request id to be unique
      
      * client/network/light: Choose same limit as block request protocol
      
      * client/network: Report reputation changes via response
      
      Allow request response protocol handlers to issue reputation changes, by
      sending them back along with the response payload.
      
      * client/network: Remove resolved TODOs
      30061009
    • Alexander Popiak's avatar
      make AllModules public (#8017) · c83bca67
      Alexander Popiak authored
      * make AllModules public
      
      * add doc comments for AllModules
      c83bca67
    • Bastian Köcher's avatar
      Fix tracing spans are not being forwarded to spawned task (#8009) · c42d756f
      Bastian Köcher authored
      * Fix tracing spans are not being forwarded to spawned task
      
      There is a bug that tracing spans are not forwarded to spawned task. The
      problem was that only the telemetry span was forwarded. The solution to
      this is to use the tracing provided `in_current_span` to capture the
      current active span and pass the telemetry span explictely. We will now
      always enter the span when the future is polled. This is essentially the
      same strategy as tracing is doing with its `Instrumented`, but now
      extended for our use case with having multiple spans active.
      
      * More tests
      c42d756f
    • yjh's avatar
      chore: fix typos (#8013) · 4da880ed
      yjh authored
      4da880ed
  3. Jan 29, 2021
  4. Jan 28, 2021
  5. Jan 27, 2021
  6. Jan 26, 2021
  7. Jan 25, 2021
  8. Jan 24, 2021
  9. Jan 22, 2021
    • cheme's avatar
      Allow transaction for offchain indexing (#7290) · 878f7ccf
      cheme authored
      
      
      * Moving offchain change set to state machine overlay change set,
      preparing use of change set internally.
      
      * Make change set generic over key and value, and use it for offchain
      indexing.
      
      * test ui change
      
      * remaining delta
      
      * generating with standard method
      
      * Remove 'drain_committed' function, and documentation.
      
      * Default constructor for enabling offchain indexing.
      
      * Remove offchain change specific iterators.
      
      * remove pub accessor
      
      * keep previous hierarchy, just expose iterator instead.
      
      * Update primitives/state-machine/src/overlayed_changes/mod.rs
      
      Co-authored-by: default avatarTomasz Drwięga <[email protected]>
      
      * fix line break
      
      * missing renamings
      
      * fix import
      
      * fix new state-machine tests.
      
      * Don't expose InnerValue type.
      
      * Add test similar to set_storage.
      
      * Remove conditional offchain storage (hard to instantiate correctly).
      
      * fix
      
      * offchain as children cannot fail if top doesn't
      
      Co-authored-by: default avatarAddie Wagenknecht <[email protected]>
      Co-authored-by: default avatarTomasz Drwięga <[email protected]>
      878f7ccf
  10. Jan 21, 2021
    • Jon Häggblad's avatar
      Cleaner GRANDPA RPC API for proving finality (#7339) · 20f40fbd
      Jon Häggblad authored
      
      
      * grandpa: persist block number for last block of authority set
      
      * grandpa: fix authority_set_changes field in tests
      
      * grandpa: fix date on copyright notice
      
      * grandpa-rpc: implement cleaner api for prove finality rpc
      
      * grandpa-rpc: replace the old prove_finality with the new one
      
      * grandpa: undo accidental whitespace change
      
      * grandpa-rpc: start work on redo of the finality_proof RPC API
      
      * grandpa: manual impl of Decode for AuthoritySet
      
      * grandpa: add comment about appending changes for forced changes
      
      * grandpa: flip order in set changes, tidy up some comments
      
      * grandpa: update some of the doc comments
      
      * grandpa: store authority set changes when applying forced changes
      
      * grandpa: simplify finality_proof.rs
      
      * grandpa: move checks and extend tests in finality_proof
      
      * grandpa: address first set of review comments
      
      * grandpa: check that set changes have well-defined start
      
      * grandpa: rework prove_finality and assocated tests
      
      * grandpa: make AuthoritySetChanges tuple struct
      
      * grandpa: add assertions for tracking auth set changes
      
      * grandpa: remove StorageAndProofProvider trait
      
      * grandpa: return more informative results for unexpected input to RPC
      
      * grandpa: tiny tweak to error msg
      
      * grandpa: fix tests
      
      * grandpa: add error specific to finality_proof
      
      * grandpa: fix review comments
      
      * grandpa: proper migration to new AuthoritySet
      
      * grandpa: fix long lines
      
      * grandpa: fix unused warning after merge
      
      Co-authored-by: default avatarAndré Silva <[email protected]>
      20f40fbd