Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • cameo cameo
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 43
    • Issues 43
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • 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
  • CameoCameo
  • cameocameo
  • Issues
  • #2
Closed
Open
Issue created Apr 05, 2017 by yannick legoc@legocOwner

Timeouts

Every blocking call must be able to return after a timeout. For a blocking call like waitFor, periodical tests should be provided.

Zeromq reliability: http://zguide.zeromq.org/php:chapter4

Failure example: remote app starts but a network failure happens before the setResult. The change of state is ok but not the starter which blocks on getResult in the recv call.

Server initialization must throw a ConnectionTimeout or return boolean in case of timeout.

Edited Feb 24, 2022 by yannick legoc
Assignee
Assign to
Time tracking