Skip to content

Commit

Permalink
Create troubleshooting.md
Browse files Browse the repository at this point in the history
Documenting a workaround discussed at https://hasurahq.slack.com/archives/C03263T1L9W/p1653561662369129 in a new Troubleshooting doc

PR-URL: hasura/graphql-engine-mono#4575
GitOrigin-RevId: eb80662b93f157d363cd0b53993fc5bb5972b546
  • Loading branch information
sassela authored and hasura-bot committed May 30, 2022
1 parent b2ff316 commit 2518d16
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 0 deletions.
2 changes: 2 additions & 0 deletions server/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,8 @@ Then in a new terminal launch `graphql-engine` in dev mode with:

$ scripts/dev.sh graphql-engine

This command also starts the GraphQL Engine console, which you can access at http://localhost:8181/console.

The `dev.sh` will print some helpful information and logs from both services
will be printed to screen.

Expand Down
8 changes: 8 additions & 0 deletions server/troubleshooting.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
### `cabal: Could not resolve dependencies:`

a.k.a "how do I get Cabal to update the freeze file with the dependencies it needs, and why doesn't `cabal update` work?"
- issue: `cabal freeze` also freezes the `index-state` at the bottom of the file so, in some cases, `cabal update` has no effect
- fix:
- delete the line starting with `index-state` at the bottom of the `cabal.project.freeze` file
- delete lines for any dependencies you want to update
- run `cabal update`/`cabal freeze`

0 comments on commit 2518d16

Please sign in to comment.