Pacenote v0.5.1

The upgrade quits the running app first and reopens it. Config and run history are untouched.

Before you upgrade

• This upgrade still quits 0.5.0, which may open and quit again a few times before the new version stays open: the fix has to be in the version being quit. Quitting Pacenote from the menu bar before brew upgrade avoids it. From 0.5.1 on, an upgrade quits the app once.

Upgrades

• Homebrew asks the app to quit again and again until it is gone, and a request that lands just as the app exits makes macOS open it again to deliver it. That copy is told to quit as it starts, and it now quits without a menu bar icon, a window or Pace, where it used to start Pace and stop it a second later, sometimes more than once.
• Once asked to quit, the app starts Pace again for nothing: not a retry, not a startup still on its way, not a Pace elsewhere that stops. The requests that keep coming share one stop.

Settings > Sandbox

• The built-in and Docker choices each say whether they are ready, beside the job they need next: Set up built-in sandbox, or Build sandbox images (Restart proxy while the proxy is down). A sandbox can be set up before it is chosen.
• Under the choices, the job's output, then what the chosen sandbox has: the Linux kernel, init filesystem, image and pacenote-vm, or the Docker engine and images, each worded as what to do rather than "missing".
• The login check sits in the login card, the proxy and Restart proxy in the allowed domains card, and the broker's state, checks and jobs in a Broker card under Ops tools. A job that cannot start says why beside its own button.

Also

• brew trust ashon/tap, once, lets a plain brew upgrade pick up Pacenote: without it Homebrew compares the installed cask with itself, and only brew upgrade --cask pacenote upgrades. The install steps in the README now include it.