Skip to content
Snippets Groups Projects
  1. Jul 29, 2020
    • Pierre Krieger's avatar
      Add a back-pressure-friendly alternative to NetworkService::write_notifications 🎉 (#6692) · 1ab77193
      Pierre Krieger authored
      
      * Add NetworkService::send_notifications
      
      * Doc
      
      * Doc
      
      * API adjustment
      
      * Address concerns
      
      * Make it compile
      
      * Start implementation
      
      * Progress in the implementation
      
      * Change implementation strategy again
      
      * More work before weekend
      
      * Finish changes
      
      * Minor doc fix
      
      * Revert some minor changes
      
      * Apply suggestions from code review
      
      * GroupError -> NotifsHandlerError
      
      * Apply suggestions from code review
      
      Co-authored-by: default avatarRoman Borschel <romanb@users.noreply.github.com>
      
      * state_transition_waker -> close_waker
      
      * Apply suggestions from code review
      
      Co-authored-by: default avatarRoman Borschel <romanb@users.noreply.github.com>
      
      * Finish renames in service.rs
      
      * More renames
      
      * More review suggestsions applied
      
      * More review addressing
      
      * Final change
      
      * 512 -> 2048
      
      Co-authored-by: default avatarRoman Borschel <romanb@users.noreply.github.com>
      1ab77193
    • Max Inden's avatar
      client/network: Adjust wording (#6755) · e674d64a
      Max Inden authored
      Rename `NetworkWorker::from_worker` to `NetworkWorker::from_service` as
      it is a channel from the `NetworkService` to the `NetworkWorker`.
      e674d64a
    • Alexander Theißen's avatar
      seal: Add benchmarks for dispatchables (#6715) · a2163420
      Alexander Theißen authored
      * seal: Fix syntax that confuses rust-analyzer
      
      * seal: Add benchmarks for Dispatchables
      
      These are only the benchmarks for the dispatchables of
      the pallet. Those are not listed in the Schedule because
      we do not want to pull the Schedule from storage before
      dispatching.
      
      This OK because those costs are not related to actual contract
      execution. Those costs (instruction costs, ext_* costs) will
      be benchmarked seperatly and entered into the default Schedule.
      
      * seal: Add a maximum code size
      
      * Fix comments from review
      
      * Removed SEED constant
      a2163420
  2. Jul 28, 2020
  3. Jul 27, 2020
  4. Jul 26, 2020
  5. Jul 24, 2020
  6. Jul 23, 2020
  7. Jul 22, 2020
  8. Jul 21, 2020
Loading