Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S StreamChain Prototype
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • zistvan-public
  • StreamChain Prototype
  • Repository
  • streamchain
  • core
  • chaincode
  • handler.go
Find file BlameHistoryPermalink
  • Matthew Sykes's avatar
    [FAB-11487] always propagate send fail errors · e1fff803
    Matthew Sykes authored Aug 09, 2018
    
    
    Errors encountered while sending a message from the peer to chaincode
    were not handled consistently. This CR adopts the philosophy that send
    failures should be treated consistently.
    
    Change-Id: I49893e7db0376c0b78d1f654c7dc94e6eeabb38d
    Signed-off-by: default avatarMatthew Sykes <sykesmat@us.ibm.com>
    e1fff803