Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • O orchestra
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 9
    • Issues 9
    • 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
  • PERE Alexandre
  • orchestra
  • Issues
  • #24
Closed
Open
Issue created Sep 11, 2019 by PERE Alexandre@apereOwner

Fix Broken Ctrl-C

Ctrl-C handling seem broken:

  • Threads that were spawned before setting the ctrl-c handler seem to stop directly when ctrl-c is hit. This can be see in current releases, as all execution forwarding stops. It can also be seen in older release, where hitting ctrl-c breaks the ssh transport and generates -43 errors.
  • Scheduler command receives the SIGINT, while it should not.
  • Finally, we want to be able to modify the ctrl-c behavior as the program changes. Indeed, at first, no allocation is made, reason why we shouldn't try to cancel it.
Edited Oct 22, 2019 by PERE Alexandre
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking