Scans keep their work through an update, and a quiet peer is reported

A long scan reads your code in passes and then merges what the passes found, step by step. Finished passes were already saved as they went; the merge steps now are too, so a scan that is stoluation now.

An administrator can now stand every background scan down for an update with one command. Each scan is written down with the exact request it was started with, including how many passes it asked for, and a scan in the middle of a pass can be given time to save it first. When the portal starts again, the scans carry on in the order they held, reusing their saved passes and merges. A scan somebody paused stays paused, and nobody is emailed that a scan was killed, because it was not.

When a peer hub has not answered a health check for 15 minutes, the hub emails its administrators, and it emails again when the peer answers, saying how long it was quiet. A machine that is down and one too busy to answer look the same from the hub, and neither is working for the fleet, so both are reported.

Full technical release notes for 7.4.3 are on the changelog, alongside every other Ghost Architect™ Local release.

Ghost Architect™ Local runs on your own hardware.

If you want an evaluation trial, the download page tells you how to get the tarball, verify it, and start the evaluation trial on your own hardware.

Request Ghost Architect™ Local

EJ Wisner, founder of Ghost Architect™. Local pricing is monthly, per team size, with no per-token bill; the numbers are on the pricing page.