-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: upgrade hasql-notifications to show error #3324
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -19,15 +19,18 @@ let | |
# | ||
# To temporarily pin unreleased versions from GitHub: | ||
# <name> = | ||
# prev.callCabal2nixWithOptions "<name>" (super.fetchFromGitHub { | ||
# lib.dontCheck (prev.callCabal2nixWithOptions "<name>" (super.fetchFromGitHub { | ||
# owner = "<owner>"; | ||
# repo = "<repo>"; | ||
# rev = "<commit>"; | ||
# sha256 = "<sha256>"; | ||
# }) "--subpath=<subpath>" {}; | ||
# }) "--subpath=." {}); | ||
# | ||
# To fill in the sha256: | ||
# update-nix-fetchgit nix/overlays/haskell-packages.nix | ||
# | ||
# Nowadays you can just delete the sha256 attribute above and nix will assume a fake sha. | ||
# Once you build the derivation it will suggest the correct sha. | ||
|
||
configurator-pg = | ||
prev.callHackageDirect | ||
|
@@ -48,6 +51,15 @@ let | |
|
||
hasql-pool = lib.dontCheck prev.hasql-pool_0_10; | ||
|
||
hasql-notifications = lib.dontCheck (prev.callHackageDirect | ||
{ | ||
pkg = "hasql-notifications"; | ||
ver = "0.2.1.0"; | ||
sha256 = "sha256-MEIirDKR81KpiBOnWJbVInWevL6Kdb/XD1Qtd8e6KsQ="; | ||
Comment on lines
+56
to
+58
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If we want to consider this as part of our bug fix, we should bump the lower bounds in There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Additionally the index-state in cabal.project.freeze needs to be updated, too. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hm, those are too easy to miss. Since we have cabal and stack running on CI, shouldn't those give an error? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. They won't be missed - if you take the first step before the second. Adjusting the package overlay for nix is the second step. If you need to bump dependencies, you should always go to |
||
} | ||
{ } | ||
); | ||
|
||
}; | ||
in | ||
{ | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think those changes make sense for the template here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, why? I'm always lost when I see that
<subpath>
andlib.dontCheck
is almost always the wanted behavior.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While working on compiling with GHC 9.8 inside nix on a local branch, I have added plenty of those in the last couple of weeks. My experience so far:
lib.dontCheck
was used not very often - and even if it was, it should not be the default as in "copy & paste comes with it", but should be added once those tests actually fail.--subpath=.
hides the fact that this is configurable and not some required default setting. I had quite a few cases where I needed a subpath other than.
. On the other hand, if<subpath>
is in there, you might need to think about it, yes, but the solution will be obvious, right?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok cool. Addressed on #3326