Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Waystone Waystone
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 18
    • Issues 18
    • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Ind.ie Projects
  • WaystoneWaystone
  • Issues
  • #53

Closed
Open
Created Aug 14, 2015 by Aral Balkan@aralMaintainer

Radical Restarts refactor: unify Pulse restart handling

We’re handing Pulse restarts differently in several places and it is causing unpredictable and unstable behaviour.

So, it’s time for a ‘Radical Restarts’ refactor, where we manage restarts only from one place, the PulseProcess class:

  1. Set env var on STNORESTART when starting Pulse

  2. On 'close' event, restart Pulse.

  3. The only way to really, truly, actually kill Pulse is to call the .stop() method on Pulse Process.

Then, everywhere else, where we are calling restart() on the Pulse API, call shutdown() instead.

This should fix:

  • The multiple Pulse processes issue.
  • The Pulse dying and not coming back to life issue.
Assignee
Assign to
Time tracking

Like this? Fund us! Your patronage helps keep us independent and going.