Assertion failure on `cabal build/haddock --enable-doc`

[andreasabel]

Using GHC 9.2.3 and cabal master:

$ cabal haddock --haddock-for-hackage --enable-doc
Warning: this is a debug build of cabal-install with assertions enabled.
Resolving dependencies...
Build profile: -w ghc-9.2.3 -O0
In order, the following will be built (use -v for more details):
 - OneTuple-0.3.1 (lib) (requires build)
 ...
 - generically-0.1 (lib) (requires build)
Assertion failed
CallStack (from HasCallStack):
  assert, called at src/Distribution/Client/ProjectPlanning.hs:246:5 in cabal-install-3.9.0.0-inplace:Distribution.Client.ProjectPlanning

Also triggered by cabal build --enable-doc.

It is this assertion

cabal/cabal-install/src/Distribution/Client/ProjectPlanning.hs

Lines 242 to 248 in 2353627

	-- either a package is being built inplace, or the
	-- 'installedPackageId' we assigned is consistent with
	-- the 'hashedInstalledPackageId' we would compute from
	-- the elaborated configured package
	. assert (elabBuildStyle == BuildInplaceOnly ||
	elabComponentId == hashedInstalledPackageId
	(packageHashInputs sharedConfig elab))

Here is the packed up directory in which I can reproduce the bug:
cabal-assertion-failed.zip
(I hope it can be reproduced even without my .cabal directory...)

[Mikolaj]

Possibly related: #6659, #6006 and the tickets mentioned in the latter.

[andreasabel]

Indeed, looks like #6006. The new thing is that even a plain cabal haddock fails, since it includes --enable-documentation by default now.

[andreasabel]

Could we have a flag --ingore-assertions to force cabal to continue?

[Mikolaj]

Could we have a flag --ingore-assertions to force cabal to continue?

We'd need our own assert, but yes, should not be hard. This is in a dev build with assertions enabled, right? Not 3.8RC1?

[andreasabel]

This is in a dev build with assertions enabled, right? Not 3.8RC1?

Yes, it is 3.9.0.0.

[ulysses4ever]

Fail to repro with the current master (dd312ec). It does reproduces still.

[andreasabel]

Fail to repro with the current master (dd312ec).

@ulysses4ever : I can reproduce this with latest master and also GHC 9.2.4. Did you unzip my project and tried it there?

[ulysses4ever]

I tried to build OneTuple and generically. What is "your project"?