-
Notifications
You must be signed in to change notification settings - Fork 842
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
Start implementing #3006 #3120
Start implementing #3006 #3120
Conversation
Update install_and_upgrade.md
I went ahead and made the changes to |
Hey! Sorry for the delay on feedback. Looks good to me, thanks for working on this! One thing is that the version tags, like ( |
…tras Don't clean packages listed as extra-deps
@mgsloan To clarify, should it be changed On a separate note, should I remove the commented out definitions of Thanks! |
…ad-pvp-revision pvp-bounds -revision
…ad-cleanup Upload cleanup, and save-hackage-creds option
…haskell#3159) * Fixed pid1 ownership inside fpco/stack-build docker image
Because `--local-bin-path` is deprecated in favour of `--local-bin`.
…l#3158) This seems a bit more accurate: When the user is already running the most recent version, the message "your version is already *more* recent" is incorrect and ever so slightly confusing. The other case -- where the user is running a more recent version than is available as a binary, for which the old message is accurate -- likely occurs much less frequently.
path-0.5.13, released in March 2017, [adds function reldir](https://hackage.haskell.org/package/path-0.5.13/changelog). Local variable reldir shadows it: https://travis-ci.org/commercialhaskell/stack/jobs/234552558 So the combination doesn't build since March. Sorry this is the quickest fix possible, I know a few alternatives, but I'm short on time and the choice is a matter of taste.
…nsible-snapshots Extensible snapshots
I totally broke this PR with extensible-snapshots, which switched from GitSHA1 to a SHA256. I'm going to this it up and open a new PR, I'll add a comment when that's done. |
…exeyzab/stack into alexeyzab-3006-speed-up-store-instances
PR #3260 is now open. When it's merged, it will merge this PR too. |
Continuing the discussion from the other PR: here's a really hacky implementation of the |
That's pretty interesting. If we were to use that library, we'd change data StaticSHA256 = StaticSHA256 !Bytes32 Is that right? And then get rid of the |
Yes, though I'd prefer a |
Makes sense. In that case it seems all that's left here is to edit the |
@snoyberg Thanks for walking me through what needed to be done here! |
No problem, thank you! It looks like the PR is showing all of my changes on extensible-snapshots as differences, which is a bit annoying... anyway, I think this is good to go. @mgsloan, did you have any objections to merge? |
Thanks! |
This changes
GitSHA1
from using aByteString
to aStaticSize 40 ByteString
. Other edits make sure the code compiles and the tests pass.It was not possible to derive a
Hashable
instance after the change, so I've implemented one by hand.I have commented out the implementation of
peek
andpoke
forGitSHA1
'sStore
instance as I am not sure if those are needed or not.If these changes are satisfactory, I'll start working on the
Stack.Types.PackageIndex.PackageDownload.pdSHA256
's instances as well.