$ /nix/store/vzx1mi9c0xfadmsm9dhd83d005cb1qs9-coreutils-9.8/bin/timeout --kill-after=15s 1800s /nix/store/99b1z08awpxj8b6mzggn59gp1shljnff-nix-2.34.5/bin/nix --extra-experimental-features nix-command --extra-experimental-features flakes --log-format internal-json build --no-link git+https://github.com/sellout/flaky?ref=docs&rev=552f63daf7d895ea0c147ce6bdea3dad53f267df#checks.x86_64-linux.formatter --print-build-logs warning: ignoring untrusted flake configuration setting 'allow-import-from-derivation'. Pass '--accept-flake-config' to trust it warning: ignoring untrusted flake configuration setting 'extra-experimental-features'. Pass '--accept-flake-config' to trust it warning: ignoring untrusted flake configuration setting 'extra-substituters'. Pass '--accept-flake-config' to trust it warning: ignoring untrusted flake configuration setting 'extra-trusted-public-keys'. Pass '--accept-flake-config' to trust it warning: ignoring untrusted flake configuration setting 'sandbox'. Pass '--accept-flake-config' to trust it warning: ignoring untrusted flake configuration setting 'use-registries'. Pass '--accept-flake-config' to trust it error (ignored): SQLite database '/var/cache/private/nix-ci-worker/eval-cache-v6/b807b75a5eb8e309fe9526e3c65a78c9ec5d31e83e8a015c36d4e2b79f1db4b4.sqlite' is busy  Building treefmt-check [treefmt-check] treefmt v2.4.0traversed 66 files [treefmt-check] emitted 52 files for processing [treefmt-check] formatted 52 files (3 changed) in 383ms [treefmt-check]  M docs/CONTRIBUTING.md [treefmt-check]  M docs/CONTRIBUTING/haskell.md [treefmt-check]  M docs/haskell/release-process.md [treefmt-check] diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md [treefmt-check] index 2b499f5..5465a5d 100644 [treefmt-check] --- a/docs/CONTRIBUTING.md [treefmt-check] +++ b/docs/CONTRIBUTING.md [treefmt-check] @@ -25,10 +25,10 @@ All contributions are welcome, we love improvements to docs and tests. [treefmt-check]  ### terminology [treefmt-check]   [treefmt-check]  | generic | Haskell | Nix | Rust | versioned | [treefmt-check] -|------------|---------------|------------|-----------|-----------| [treefmt-check] -| repository | | | | ✔ | [treefmt-check] +| ---------- | ------------- | ---------- | --------- | --------- | [treefmt-check] +| repository | | | | ✔ | [treefmt-check]  | project | Cabal project | flake | workspace | | [treefmt-check] -| package | Cabal package | derivation | crate | ✔ | [treefmt-check] +| package | Cabal package | derivation | crate | ✔ | [treefmt-check]  | component | Cabal stanza | | | | [treefmt-check]   [treefmt-check]  There is usually one project per repository, but sometimes a project may be split across multiple repositories. It’s unlikely that more than one project would be in the same repository. [treefmt-check] diff --git a/docs/CONTRIBUTING/haskell.md b/docs/CONTRIBUTING/haskell.md [treefmt-check] index d62443d..210aff7 100644 [treefmt-check] --- a/docs/CONTRIBUTING/haskell.md [treefmt-check] +++ b/docs/CONTRIBUTING/haskell.md [treefmt-check] @@ -50,7 +50,7 @@ Documentation is very important, but it shouldn’t detract from good naming. Th [treefmt-check]   [treefmt-check]  Documentation is written using [Haddock](https://haskell-haddock.readthedocs.io/), and it’s helpful to add Doctest examples, as described in the “testing” section below. [treefmt-check]   [treefmt-check] -__NB__: Haddock isn’t Markdown! But the similarities can make it easy to forget sometimes. Please try to review your doc changes using [`cabal haddock-project`](https://cabal.readthedocs.io/en/stable/cabal-commands.html#cabal-haddock-project) before submitting them. [treefmt-check] +**NB**: Haddock isn’t Markdown! But the similarities can make it easy to forget sometimes. Please try to review your doc changes using [`cabal haddock-project`](https://cabal.readthedocs.io/en/stable/cabal-commands.html#cabal-haddock-project) before submitting them. [treefmt-check]   [treefmt-check]  #### guidelines [treefmt-check]   [treefmt-check] @@ -93,7 +93,7 @@ name foo [treefmt-check]  library [treefmt-check]  ``` [treefmt-check]   [treefmt-check] -``` cabal [treefmt-check] +```cabal [treefmt-check]  name: foo-hedgehog [treefmt-check]   [treefmt-check]  library [treefmt-check] diff --git a/docs/haskell/release-process.md b/docs/haskell/release-process.md [treefmt-check] index c761703..e08874f 100644 [treefmt-check] --- a/docs/haskell/release-process.md [treefmt-check] +++ b/docs/haskell/release-process.md [treefmt-check] @@ -20,7 +20,7 @@ Don’t lump documentation & testing improvements into a breaking change just be [treefmt-check]   [treefmt-check]  ### format the PR title as a CHANGELOG entry [treefmt-check]   [treefmt-check] -__TODO__: How does this work when there are multiple packages? [treefmt-check] +**TODO**: How does this work when there are multiple packages? [treefmt-check]   [treefmt-check]  ## release updates [treefmt-check]   [treefmt-check] @@ -37,7 +37,6 @@ In as far as the release is automated, the changes should be made in the merge c [treefmt-check]   [treefmt-check]  [^1]: This is delicate, because the CI build matrix doesn’t do a good job of solving for other versions of local packages. [treefmt-check]   [treefmt-check] - [treefmt-check]  ## Hackage info [treefmt-check]   [treefmt-check]  Hackage allows you to optionally tag a release as “preferred” or ”deprecated”. Progress: 0 of 1 built (1 failed) Cannot build '/nix/store/iad39wikzivam092j94zkv7rzng5vllv-treefmt-check.drv'. Reason: builder failed with exit code 1. Output paths: /nix/store/jzhks7mp1s50k50svwd19g5l9zh10zj4-treefmt-check Last 67 log lines: > treefmt v2.4.0traversed 66 files > emitted 52 files for processing > formatted 52 files (3 changed) in 383ms > M docs/CONTRIBUTING.md > M docs/CONTRIBUTING/haskell.md > M docs/haskell/release-process.md > diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md > index 2b499f5..5465a5d 100644 > --- a/docs/CONTRIBUTING.md > +++ b/docs/CONTRIBUTING.md > @@ -25,10 +25,10 @@ All contributions are welcome, we love improvements to docs and tests. > ### terminology >  > | generic | Haskell | Nix | Rust | versioned | > -|------------|---------------|------------|-----------|-----------| > -| repository | | | | ✔ | > +| ---------- | ------------- | ---------- | --------- | --------- | > +| repository | | | | ✔ | > | project | Cabal project | flake | workspace | | > -| package | Cabal package | derivation | crate | ✔ | > +| package | Cabal package | derivation | crate | ✔ | > | component | Cabal stanza | | | | >  > There is usually one project per repository, but sometimes a project may be split across multiple repositories. It’s unlikely that more than one project would be in the same repository. > diff --git a/docs/CONTRIBUTING/haskell.md b/docs/CONTRIBUTING/haskell.md > index d62443d..210aff7 100644 > --- a/docs/CONTRIBUTING/haskell.md > +++ b/docs/CONTRIBUTING/haskell.md > @@ -50,7 +50,7 @@ Documentation is very important, but it shouldn’t detract from good naming. Th >  > Documentation is written using [Haddock](https://haskell-haddock.readthedocs.io/), and it’s helpful to add Doctest examples, as described in the “testing” section below. >  > -__NB__: Haddock isn’t Markdown! But the similarities can make it easy to forget sometimes. Please try to review your doc changes using [`cabal haddock-project`](https://cabal.readthedocs.io/en/stable/cabal-commands.html#cabal-haddock-project) before submitting them. > +**NB**: Haddock isn’t Markdown! But the similarities can make it easy to forget sometimes. Please try to review your doc changes using [`cabal haddock-project`](https://cabal.readthedocs.io/en/stable/cabal-commands.html#cabal-haddock-project) before submitting them. >  > #### guidelines >  > @@ -93,7 +93,7 @@ name foo > library > ``` >  > -``` cabal > +```cabal > name: foo-hedgehog >  > library > diff --git a/docs/haskell/release-process.md b/docs/haskell/release-process.md > index c761703..e08874f 100644 > --- a/docs/haskell/release-process.md > +++ b/docs/haskell/release-process.md > @@ -20,7 +20,7 @@ Don’t lump documentation & testing improvements into a breaking change just be >  > ### format the PR title as a CHANGELOG entry >  > -__TODO__: How does this work when there are multiple packages? > +**TODO**: How does this work when there are multiple packages? >  > ## release updates >  > @@ -37,7 +37,6 @@ In as far as the release is automated, the changes should be made in the merge c >  > [^1]: This is delicate, because the CI build matrix doesn’t do a good job of solving for other versions of local packages. >  > - > ## Hackage info >  > Hackage allows you to optionally tag a release as “preferred” or ”deprecated”. For full logs, run: nix log /nix/store/iad39wikzivam092j94zkv7rzng5vllv-treefmt-check.drv