cabal haddock-project --executables fails

[philderbeast]

Describe the bug
cabal haddock-project --executables fails on this project, on haskell/cabal.

To Reproduce
Steps to reproduce the behavior:

$ ~/.ghcup/bin/cabal --numeric-version
3.16.1.0

$ ~/.ghcup/bin/cabal haddock-project --executables
Warning: haddock-project command is experimental, it might break in the future
Resolving dependencies...
Build profile: -w ghc-9.10.3 -O1
In order, the following will be built (use -v for more details):
 - Cabal-syntax-3.17.0.0 (lib) (configuration changed)
 - cabal-validate-1.0.0 (exe:cabal-validate) (configuration changed)
 - solver-benchmarks-3 (lib) (configuration changed)
 - hackage-security-0.6.3.2 (lib) (configuration changed)
 - cabal-benchmarks-3 (test:cabal-benchmarks) (dependency rebuilt)
 - Cabal-tests-3 (test:rpmvercmp) (dependency rebuilt)
 - Cabal-tests-3 (test:no-thunks-test) (dependency rebuilt)
 - Cabal-3.17.0.0 (lib) (configuration changed)
 - solver-benchmarks-3 (test:unit-tests) (dependency rebuilt)
 - solver-benchmarks-3 (exe:hackage-benchmark) (configuration changed)
 - cabal-install-solver-3.17.0.0 (lib) (configuration changed)
 - Cabal-tree-diff-3.17.0.0 (lib) (configuration changed)
 - Cabal-tests-3 (exe:lang-tests) (configuration changed)
 - Cabal-tests-3 (test:custom-setup-tests) (dependency rebuilt)
 - Cabal-tests-3 (test:check-tests) (dependency rebuilt)
 - Cabal-tests-3 (lib) (configuration changed)
 - Cabal-hooks-3.17 (lib) (configuration changed)
 - Cabal-described-3.17.0.0 (lib) (configuration changed)
 - Cabal-QuickCheck-3.17.0.0 (lib) (configuration changed)
 - cabal-install-solver-3.17.0.0 (test:unit-tests) (dependency rebuilt)
 - cabal-install-3.17.0.0 (lib) (dependency rebuilt)
 - Cabal-tests-3 (test:parser-tests) (dependency rebuilt)
 - Cabal-tests-3 (test:hackage-tests) (dependency rebuilt)
 - cabal-testsuite-3 (lib:cabal-testsuite, exe:cabal-tests, exe:setup, exe:test-runtime-deps) (configuration changed)
 - buildinfo-reference-generator-0 (exe:buildinfo-reference-generator) (configuration changed)
 - Cabal-tests-3 (test:unit-tests) (dependency rebuilt)
 - cabal-install-3.17.0.0 (test:unit-tests) (dependency rebuilt)
 - cabal-install-3.17.0.0 (test:parser-tests) (dependency rebuilt)
 - cabal-install-3.17.0.0 (test:mem-use-tests) (dependency rebuilt)
 - cabal-install-3.17.0.0 (test:long-tests) (dependency rebuilt)
 - cabal-install-3.17.0.0 (test:integration-tests2) (dependency rebuilt)
 - cabal-install-3.17.0.0 (exe:cabal) (dependency rebuilt)
Configuring library for Cabal-syntax-3.17.0.0...
...
Preprocessing executable 'cabal-tests' for cabal-testsuite-3...
Running Haddock on executable 'cabal-tests' for cabal-testsuite-3...
Warning: The documentation for the following packages are not installed. No
links will be generated to these packages: mtl-compat-0.2.2
[1 of 1] Compiling Main             ( main/cabal-tests.hs, nothing )
main/cabal-tests.hs:130:9: error: [GHC-83865]
    • Couldn't match type ‘optparse-applicative-0.18.1.0:Options.Applicative.Types.Parser’
                     with ‘Parser’
      Expected: Parser CommonArgs
        Actual: optparse-applicative-0.18.1.0:Options.Applicative.Types.Parser
                  CommonArgs
      NB: ‘Parser’
            is defined in ‘Options.Applicative.Types’
                in package ‘optparse-applicative-0.18.1.0’
          ‘optparse-applicative-0.18.1.0:Options.Applicative.Types.Parser’
            is defined in ‘Options.Applicative.Types’
                in package ‘optparse-applicative-0.18.1.0’
    • In the second argument of ‘(<*>)’, namely ‘commonArgParser’
      In the first argument of ‘(<*>)’, namely
        ‘MainArgs
           <$>
             option
               auto
               (help "Number of threads to run"
                  <>
                    short 'j' <> showDefault <> value numCapabilities <> metavar "INT")
           <*> many (argument str (metavar "FILE"))
           <*>
             switch
               (long "hide-successes"
                  <> help "Do not print test cases as they are being run")
           <*> switch (long "verbose" <> short 'v' <> help "Be verbose")
           <*>
             switch
               (long "quiet" <> short 'q' <> help "Only output stderr on failure")
           <*>
             optional
               (option
                  str
                  (help "Dist directory we were built with"
                     <> long "builddir" <> metavar "DIR"))
           <*> optional cabalLibSpecParser
           <*> commonArgParser’
      In the expression:
        MainArgs
          <$>
            option
              auto
              (help "Number of threads to run"
                 <>
                   short 'j' <> showDefault <> value numCapabilities <> metavar "INT")
          <*> many (argument str (metavar "FILE"))
          <*>
            switch
              (long "hide-successes"
                 <> help "Do not print test cases as they are being run")
          <*> switch (long "verbose" <> short 'v' <> help "Be verbose")
          <*>
            switch
              (long "quiet" <> short 'q' <> help "Only output stderr on failure")
          <*>
            optional
              (option
                 str
                 (help "Dist directory we were built with"
                    <> long "builddir" <> metavar "DIR"))
          <*> optional cabalLibSpecParser
          <*> commonArgParser
          <*> tastyArgParser
    |
130 |     <*> commonArgParser
    |         ^^^^^^^^^^^^^^^

load' failed
Documentation created:
/home/.../cabal/dist-newstyle/build/x86_64-linux/ghc-9.10.3/cabal-install-solver-3.17.0.0/doc/html/cabal-install-solver
Error: [Cabal-7125]
Failed to build documentation for cabal-testsuite-3.

[philderbeast]

Same failure with cabal haddock cabal-testsuite --haddock-executables whereas cabal haddock cabal-testsuite builds docs just fine:

[philderbeast]

Here's the reportedly expected and actual types laid out so as to highlight the difference (is there any?):

-                                                         ‘Parser’ is defined in ‘Options.Applicative.Types’
+ ‘optparse-applicative-0.18.1.0:Options.Applicative.Types.Parser’ is defined in ‘Options.Applicative.Types’
in package ‘optparse-applicative-0.18.1.0’

[geekosaur]

Yeh, I saw that and it made me wonder if there's some Haddock "home module" thing in play preventing it from recognizing as ghc does that they resolve to the same type.