Matthew Pickering

This seems to confirm what @TeofilC suggested about time profiling events interrupting the writing of other events and leading to corruption

Seems like things are mostly working as expected here. 1. When you write `cabal repl all` you are not loading both units (you need `--enable-tests` as well to make `all`...

I think you could write a similar ticket to this for other features which affect the store hash as well. For instance, if you decide you want to build your...

Did you consider modifying `validatedTargets`, in particular the `selectPackageTargets` function? That seems likely to be more correct to me than this ad-hoc manipulation of target strings.

Let me know if you need some help with this @philderbeast

@philderbeast I run the test which is failing ``` -----BEGIN CABAL OUTPUT----- Resolving dependencies... -----END CABAL OUTPUT----- Assertion failed CallStack (from HasCallStack): assert, called at src/Distribution/Client/ProjectOrchestration.hs:1061:3 in cabal-install-3.17.0.0-inplace:Distribution.Client.ProjectOrchestration ``` which...

> > I run the test which is failing > > Interesting. Shouldn't all CI runs have a backtrace that points to the same location for the failing assertion? >...

@philderbeast I reproduced and fixed the issue with assertions not showing a source location ``` {-# LANGUAGE LambdaCase #-} {-# LANGUAGE RankNTypes #-} {-# LANGUAGE ScopedTypeVariables #-} +{-# LANGUAGE ImplicitParams...

I'm struggling a bit to do a proper review without diving in and understanding all the details myself. So I am also happy to merge what you have done already...

@geekosaur Package distributed with `ghc` are reinstallable unless the build plan contains `ghc`. The reason that already installed packages are preferred is #9669 which is unrelated to this ticket as...