chore: vendor hasql#5084
Open
wolfgangwalther wants to merge 1391 commits into
Open
Conversation
Pipelining mode
As a workaround for Hackage including the dependencies of internal libs in the public list of package dependencies.
* master: Update actions
* clean-up-public-deps: Remove rerebase from the internal library deps
Report errors when LISTEN or UNLISTEN fail
Remove stack from repo since I am currently working only with cabal
This prepares the merge into the postgrest main repo. To avoid merge conflicts and give a clear history wrt renames, all the files are moved to a vendor/ subdirectory first, before they are moved to their final location.
This prepares the merge into the postgrest main repo. To avoid merge conflicts and give a clear history wrt renames, all the files are moved to a vendor/ subdirectory first, before they are moved to their final location.
This prepares the merge into the postgrest main repo. To avoid merge conflicts and give a clear history wrt renames, all the files are moved to a vendor/ subdirectory first, before they are moved to their final location.
This prepares the merge into the postgrest main repo. To avoid merge conflicts and give a clear history wrt renames, all the files are moved to a vendor/ subdirectory first, before they are moved to their final location.
wolfgangwalther
force-pushed
the
vendor-hasql
branch
2 times, most recently
from
3b09a5b to
04d651b
Compare
taimoorzaeem
reviewed
Jul 9, 2026
wolfgangwalther
force-pushed
the
vendor-hasql
branch
from
04d651b to
74fd5d9
Compare
This prepares the merge into the postgrest main repo. To avoid merge conflicts and give a clear history wrt renames, all the files are moved to a vendor/ subdirectory first, before they are moved to their final location.
This was referenced Jul 12, 2026
wolfgangwalther
force-pushed
the
vendor-hasql
branch
2 times, most recently
from
6591271 to
299d40c
Compare
Member
Author
|
The commit check can't pass due to the big number of historic commits merged here. Everything else should pass by now. I do wonder whether we should merge this - or wait a bit and cut a v16 release first. This certainly needs follow up (inclusion of tests, reduction of code, ...), so we might want to have a last release without vendoring first. |
Member
Agree, let's do it for v16. |
Member
After v16 maybe we could merge this into another branch and remove what we don't need before merging into |
This removes everything from the vendored hasql packages, except their license, source code, tests and .cabal file. We also remove metadata which is not needed anymore from .cabal file, but leave everything that needs to be ported to our own .cabal file later in place.
It's all MIT, so it will be enough to keep the additional copyright notices.
To run it, we need to remove the Arrows extension from postgrest.cabal. It doesn't seem to be depended upon by the hasql code (but was still introduced along with it), but breaks the style check. That's because stylish-haskell applies all extensions found in the .cabal file for all files, even when they are only part of *one* component. The Arrows extension makes `proc` a reserved keyword, which is used in CallPlan.hs.
I did not fix all of these by hand, but used the `--refactor` flag on hlint to do it for me. This is something that we might want to add in the future by default.
wolfgangwalther
force-pushed
the
vendor-hasql
branch
from
299d40c to
450759c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
13 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Step 2 for #4823. This replaces the
hasql-*dependencies (which includeshasql-notifications, but I don't know of a way not to fork that as well, since it depends onhasqlitself) with a vendored copy keeping the original history.We're only using the source code, so far, but not the original tests. That will be a next, separate step to merge these tests with ours and integrate them into the nix tooling etc.
Right now, it builds. Let's see what CI says - I assume it should also pass all our tests.
TODO:
Depends on #5093 and #5094.