Yeah, I started seeing this yesterday too, after a cabal update. Looks like a new version of streaming-commons was released without the module, and I guess later versions of warp don't use it?

I'm 👍 on this, though I've been wondering, what's the usual way of making cabal's life easier (without increasing max-backjumps)? Is it to just have fewer dependencies and narrower version ranges?

In fact in this case also --reorder-goals helps solver to find a valid install plan.

Opened an issue here.