Skip to main content

2023-q4

Admins can restrict sign-in to a list of users or groups, and projects spread over many repositories can share one templated configuration. Runs are matched with the reference more accurately, and output menus show compute times and the reference's directory.

Admins

Restrict who can sign in

With QABOARD_LOGIN_RESTRICTED=true and a YAML file set in QABOARD_LOGIN_RESTRICTED_YAML, only listed users can sign in, matched by user name, email or any attribute from the authentication provider. User details from the provider are now saved on each login.

Learn more →
Project integration

Shared configuration across repositories

project.name and project.url can use {root_path} and {project_path} placeholders, so many repositories can include the same qaboard.yaml. Submodules can set storage.artifacts.subproject to keep their artifacts organized.

Learn more →
Users

More accurate run matching

When comparing with a reference, runs are matched by input database and path, and still by input path alone when databases differ. Exports name files after the database when a batch mixes several.

Web app​

  • The output menu shows the run's compute time (for example "1h2min3s"), and offers to copy or open the reference's output directory, in titled sections.
  • The date range filter no longer needs both a start and an end date.
  • Deleting several batches skips milestones and batches that no longer exist.
  • Tuning warnings are shown as callouts, and more errors are displayed instead of failing silently.
  • Fixed state issues when the URL contains encoded characters.

CLI and project setup​

  • qa check-bit-accuracy compares RAW and HEX images by their attributes and pixel data, and warns and falls back to file hashes when attributes are missing.
  • Batches can change labels while their runs are ongoing.
  • Fixed submodule projects that used their parent's repository, and errors when LSF jobs had already finished.

Server and administration​

  • Git pushes no longer create commits ahead of time, which bloated the database of monorepos with hundreds of projects. Commits are recorded with their configuration and metrics when their first batch is posted.
  • New projects work whether their default branch is main or master.
  • Supports GitLab 16 sign-in.
  • Database JSON columns now use JSONB (with a migration).
  • The web app can report errors to Sentry with source maps and send product analytics to PostHog. Both are optional, enabled with build arguments.
  • pgAdmin is served under /pgadmin4/, and Flower can display pickled task data.
  • The docs and the dev setup now use docker compose instead of docker-compose.
  • Fixed race conditions in the image pixel API and when creating inputs, and errors when deleting the same run twice.

Documentation​