Set bounds for retrie by ghc

[jneira]

• To be backported to 1.3.0-hackage (See July 2021 monthly release (1.3.0) with limited ghc 9.0 support (needs hackage release) #1990)

[pepeiborra]

This shouldn't be necessary, ghcide doesn't care, it's the Cabal solver job to find a working set of versions right?

[jneira]

This shouldn't be necessary, ghcide doesn't care, it's the Cabal solver job to find a working set of versions right?

yep, but it is not able to do it in this case, will try increasing max-backjumps but the package should be built with the default one 😟

[pepeiborra]

This shouldn't be necessary, ghcide doesn't care, it's the Cabal solver job to find a working set of versions right?

yep, but it is not able to do it in this case, will try increasing max-backjumps but the package should be built with the default one 😟

It is able to do it in CI just fine except in the new workflow. Why?

[jneira]

It is able to do it in CI just fine except in the new workflow. Why?

I've tried to reproduce locally, following the workflow steps verbatim and i am not able to reproduce neither, even with a fresh new cabal config and cache. The main diff is i am on windows.

[jneira]

Aaaand https://github.com/haskell/haskell-language-server/actions/runs/1216111548 has built ghcide without the change of this pr but adding a upper bound to extras, wonderful

Will close eyes and the pr 😛