Pass Ormolu cradle flags & default-extensions

[Avi-D-coder]

Take 2

[fendor]

@Avi-D-coder Shall we wait for an hie-bios release before merging this?

[Avi-D-coder]

@fendor When is the next hie-bios release planed? I would like to get this pr in today, so I can send in ormolu 0.0.3.1 and range formats on top of it and only have to rebase once. If hie-bios needs more time I would prefer to temporarily add the initializeFlagsWithCradleWithMessage and remove it when hie-bios is updated.

[fendor]

I would plan to update hie-bios before the HIE release, if possible. However, adressing the remaining issue, then merging and creating an issue is fine for me

[alanz]

When is the next hie-bios release planed?

Probably the weekend of 1 Feb

[fendor]

Why not? The cradle cache should also contain current cradle, no?

[Avi-D-coder]

No idea, I added this as a warning, because I had expected it to be in the cache.

[fendor]

If you are already at it, could you extend documentation for this, too?

[Avi-D-coder]

Can someone who uses cabal tell me why its not trying ormolu-0.0.3.1?

Resolving dependencies...
cabal: Could not resolve dependencies:
[__0] trying: haskell-ide-engine-1.0.0.0 (user goal)
[__1] next goal: ormolu (dependency of haskell-ide-engine)
[__1] rejecting: ormolu-0.0.3.0, ormolu-0.0.2.0, ormolu-0.0.1.0 (conflict:
haskell-ide-engine => ormolu>=0.0.3.1)
[__1] fail (backjumping, conflict set: haskell-ide-engine, ormolu)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: haskell-ide-engine, ormolu

[fendor]

@Avi-D-coder maybe you need to update your hackage index, e.g. cabal v2-update?

[Avi-D-coder]

@fendor no luck both on circleci and locally

cabal v2-clean
cabal v2-update
cabal v2-configure 

[fendor]

Last remark :)

[Avi-D-coder]

Anyone else have a objection before CI finishes and I merge?

[Avi-D-coder]

All the azure errors are unrelated.