UnusableReportsDirectoryError

The Cause

@thymian/plugin-reporter could not create the directory it writes reports into, or the directory exists but is not writable, and at least one formatter is configured. The check runs while the plugin registers — before any workflow runs — so the run stops immediately instead of computing findings that would never reach disk.

Common reasons:

• The directory sits on a read-only mount (EROFS) or the process lacks permission (EACCES) — including a directory that already exists but is read-only.
• A regular file already occupies the path, or one of its parents (ENOTDIR).
• reportsDir points somewhere that does not exist and cannot be created.

This used to be one logged line on stderr and an exit code of 0: the run looked green, and a CI step globbing the report files simply found nothing. It is a hard failure now.

The Solution

Point the reporter at a directory it can create and write to, or fix the one it has. reportsDir is a plugin-level option — one base directory for every formatter:

thymian.config.yaml

plugins:
  '@thymian/plugin-reporter':
    options:
      # Optional. Defaults to .thymian/reports.
      reportsDir: build/reports
      formatters:
        markdown: {}

A relative reportsDir resolves against the run working directory (--cwd), an absolute one is used as-is. Check that nothing else occupies the path:

ls -ld build/reports

If a run should not write report files at all, leave the formatters empty. Nothing is checked and no directory is created:

plugins:
  '@thymian/plugin-reporter':
    options:
      formatters: {}

Note that a failure while a report is being written is logged as an error on stderr but does not fail the run: the exit code still reflects the findings, not the write. By then the findings already exist, and losing them would be worse than an incomplete file. Only this up-front check fails the run.