Use Cardano Haskell package repository ("CHaP")

[andreabedini]

This PR replaces most source-repository-package stanzas in cabal.project with packages fetched from our Cardano Haskell package repository.

Unfortunately some packages in CHaP still have broken version bounds so we need to manually specify a bunch of constraints to make sure we have a plan we can build.

I still need to revisit the documentation in CONTRIBUTING.

[michaelpj]

Great stuff, hopefully the constraints will die in due course.

[andreabedini]

the failure doesn't seem to have anything to do with CHaP

unpacking sources
unpacking source archive /nix/store/0fhy2yp7avaaxcvvk7iw9y4zz9zzxbsp-plutus-apps-root-playground-common-test-playground-common-test-root
source root is plutus-apps-root-playground-common-test-playground-common-test-root
patching sources
building
all tests
  Auth.TypesSpec
    OAuthToken JSON handling
      should be able to parse a github response: FAIL
        Exception: /nix/store/swckk3qwxhhii52wird3gb61698gwc4l-playground-common-test-playground-common-test-1.0.0.0-data/share/ghc-8.10.7/x86_64-linux-ghc-8.10.7/playground-common-1.0.0.0/test/oAuthToken1.json: openBinaryFile: does not exist (No such file or directory)
        Use -p '/should be able to parse a github response/' to rerun this test only.
  Schema
    toSchema
      Encoding of various types:                 OK
    toArgument
      Encoding of various types:                 OK
  TH
    Schemas compile as expected:                 OK
  mkKnownCurrencies
    Serialisation:                               OK

1 out of 5 tests failed (0.04s)```

[koslambrou]

the failure doesn't seem to have anything to do with CHaP

That's the same error as #757 which tries to bump haskell.nix and hackage.nix. Is using CHaP making us use a more recent version of those packages?

[michaelpj]

Andrea just bumped haskell.nix in this PR also, so it probably has the same bug as that one. Needs a newer haskell.nix. Ideally we just fix that other PR soon!

[andreabedini]

WUT? I force pushed and GitHub closed the PR. 🤷 I cannot reopen it. I'll open a new PR.

Edit: oh I see what happened, git commit failed with the ususal No .pre-commit-config.yaml file was found and I didn't notice, so when I force-pushed I had reset the branch to the same commit as main. Which GitHub took as "closing the PR". 🤷

[michaelpj]

🙈

[andreabedini]

Adding insult to the injury, cardano-ledger just got a new release out and that feature is not included 😭

[koslambrou]

Well, their new release is based on functionality that was done on August. Not really up to date. Don't know why though.

[andreabedini]

I had to reintroduce a srp for cardano-node because cardano-git-rev cardano-submit-api trace-dispatcher trace-resources trace-forward were not released to chap along with cardano-node 1.35.4. Hopefully this is only temporary.

[michaelpj]

I had to reintroduce a srp for cardano-node because cardano-git-rev cardano-submit-api trace-dispatcher trace-resources trace-forward were not released to chap along with cardano-node 1.35.4.

Are those packages that we depend on, or ones that the released packages depend on? We could probably release those now if they should have been released.

[michaelpj]

Can we move to the Hackage quickcheck-dynamic now, perhaps?

[andreabedini]

@michaelpj

Are those packages that we depend on, or ones that the released packages depend on? We could probably release those now if they should have been released.

we use cardano-submit-api in plutus-example, the other ones are transitive. We just released trace-dispatcher and trace-forward which are the critical ones.

[andreabedini]

Can we move to the Hackage quickcheck-dynamic now, perhaps?

yes but it's not entirely trivial, we have ticket for that PLT-1239

[andreabedini]

I think this is the best we can do for the moment.

[michaelpj]

We'll need to resolve the ledger issue before we can publish plutus-apps libs to CHaP, and also there's going to be a lot of local recompilation for folks still until we do, but I agree this is the best we can do for now 👍

[koslambrou]

Well, their new release is based on functionality that was done on August. Not really up to date. Don't know why though.