Skip to content

Runs: delete a launch that has ended #155

Description

@harenome

Priority

extreme. The change is in execution and sends one command to each run host. Workspaces and the judgement store change too.

Components

  • app/nullius (backend)
  • app/web (routes)
  • templates and static files
  • docs and the site
  • catalogue (benchmarks, agents, capabilities)
  • the standard (ports, kits, relay, runs)
  • CI, workflows and skills

Today

You cannot delete a launch from the page or from the command line. A launch is the block that Runs, By launch, shows with its agents and its task checks (nop, oracle). A Run from Review makes one run, or one run per machine when the launch is split in shards. Each run stays in the data directory under runs/<name>/ (run.json, the log, jobs/). Each workspace that holds the launch keeps its job roots and its judgements of the launch's trials. On each host, ~/.nullius/runs/<name> stays.

The only workaround is to delete the folders by hand. After that, each workspace still has the roots, and the judgements and parsed jobs of the launch stay in the workspace directory.

Wanted

On the block of a launch that has ended, in Runs, By launch, a Delete launch action that asks first, in a dialog. A launch split over several machines is one launch: Delete takes all of its runs. The question names the launch by the title its block shows and lists its rows by the names the table shows (shards counted per participant). It also gives the total size of its folders, the number of judgements, the workspaces that hold the launch, and one box per host that has a copy (ticked by default).

The launch goes as one. Its runs ran the same tasks, its task checks check them for every agent, and a run cannot be added back to it later. So there is no delete for one job. The job page links to the dialog of its launch, and does not delete the job alone.

For each run, Delete removes the run folder, its roots and parsed jobs in each workspace that holds it, the judgements of its trials in those workspaces and, when its host is ticked, ~/.nullius/runs/<name> on that host. Nothing else changes.

Only a launch whose rows all come from runs that Nullius made can be deleted. Each run is a folder directly in the runs directory, with its run.json. A launch with jobs opened from elsewhere has no Delete. If a run of the launch is preparing, running, paused or stopping, the delete is refused with one line: stop it first.

Acceptance

  • In Runs, By launch, the block of a launch that has ended has Delete launch, for one machine or several. A launch with a run still going has none, and a delete request for it is refused with one line that names the run and says to stop it first. All runs has no Delete.
  • Delete launch asks first, in a dialog. The dialog names the launch by its title, its rows by the names the table shows, the size of its folders, the number of judgements, the workspaces that hold it, and each host with a copy.
  • Yes deletes every run of the launch: its folder, its roots and parsed jobs in every workspace that holds it, and the judgements of its trials there. Other roots and their judgements stay. The notice names the launch.
  • For each ticked host, ~/.nullius/runs/<name> of the run on that host is deleted. If the host does not answer, the notice says that the copy stays.
  • If a run folder cannot be removed, the notice says which run stays, and that run keeps its jobs and judgements.
  • The job page has no delete of its own. Its link opens the dialog of its launch on the Runs page.
  • A launch with jobs that Nullius did not run has no Delete.
  • A name that is not a run folder in the runs directory (a path, .., a link, a folder without run.json) is refused.
  • The request needs the form token and a browser on the application host, as Stop does.
  • After a delete, no page shows the launch.
  • Backend and route tests cover the above.

Dependencies and related

Activity

  1. added
    enhancementNew feature or request
    P2Planned: limited in scope, has a way around it, or a missing feature
    on Nov 16, 2026
  2. added theissue type on Nov 16, 2026
  3. added a commit that references this issue on Nov 17, 2026
    b11083b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Planned: limited in scope, has a way around it, or a missing featureenhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions