Skip to content
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

Doesn't compile with latest http-conduit 2.2.0 #206

Closed
felixonmars opened this issue Jul 5, 2016 · 7 comments
Closed

Doesn't compile with latest http-conduit 2.2.0 #206

felixonmars opened this issue Jul 5, 2016 · 7 comments

Comments

@felixonmars
Copy link
Contributor

[ 3 of 76] Compiling Aws.Core         ( Aws/Core.hs, dist/build/Aws/Core.o )

Aws/Core.hs:497:9: error:
    Not in scope: `HTTP.checkStatus'
    Perhaps you meant `HTTP.mkStatus' (imported from Network.HTTP.Types)
    Neither `Network.HTTP.Types' nor `Network.HTTP.Conduit' exports `checkStatus'.

Related change:

snoyberg/http-client@b476183

@ilovezfs
Copy link

Any progress on this?

ilovezfs added a commit to ilovezfs/git-annex that referenced this issue Jul 22, 2016
aws 0.14.0 is incompatible with http-conduit 2.2.0
aristidb/aws#206

esqueleto 2.4.3 is incompatible with persistent 2.5
prowdsponsor/esqueleto#137
prowdsponsor/esqueleto#141
prowdsponsor/esqueleto#139

Solver needs these hints when building git-annex with +S3 and +Webapp.
@aristidb
Copy link
Owner

I haven't had time to work on this yet, but Pull Requests are always
welcome.

ilovezfs notifications@github.com schrieb am Fr., 22. Juli 2016, 13:32:

Any progress on this?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#206 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAB3-ISonxtS-0hmNMwwZOcZYvbJ_i7dks5qYKo2gaJpZM4JFAHa
.

@jkachmar
Copy link

jkachmar commented Aug 2, 2016

I just poked at this a little bit and wanted to share what I found, since I don't have the time to go further right now:

  • instance Default Request has been removed; Network.HTTP.Client.defaultRequest should be used instead of Data.Default.def
  • checkResponse changed its type signature from checkStatus; the default response is now \_ _ -> return ()

Changing these lets Aws.Core compile, but causes Aws.S3.Commands.GetObject to fail wit the following messages

    Couldn't match expected type ‘HTTP.CookieJar -> r0’
                with actual type ‘HTTP.HttpExceptionContent’
    The function ‘HTTP.StatusCodeException’
    is applied to three arguments,
    but its type ‘HTTP.Response ()
                  -> B8.ByteString -> HTTP.HttpExceptionContent’
    has only two
    In the second argument of ‘($)’, namely
      ‘HTTP.StatusCodeException status headers cookies’
    In the expression:
      throwM $ HTTP.StatusCodeException status headers cookies
    Couldn't match expected type ‘HTTP.Response ()’
                with actual type ‘HTTP.Status’
    In the first argument of ‘HTTP.StatusCodeException’, namely
      ‘status’
    In the second argument of ‘($)’, namely
      ‘HTTP.StatusCodeException status headers cookies’
    Couldn't match type ‘[HTTP.Header]’ with ‘B8.ByteString’
    Expected type: B8.ByteString
      Actual type: HTTP.ResponseHeaders
    In the second argument of ‘HTTP.StatusCodeException’, namely
      ‘headers’
    In the second argument of ‘($)’, namely
      ‘HTTP.StatusCodeException status headers cookies’

Hopefully someone finds this helpful!

@bgamari
Copy link
Collaborator

bgamari commented Nov 13, 2016

@aristidb I think it would make sense to push out a release at this point; the restrictive bounds of aws are becoming quite painful.

@aristidb
Copy link
Owner

@bgamari Please feel free to go ahead and make the release. :-)

@aristidb
Copy link
Owner

I believe #213 closes this issue.

@bgamari
Copy link
Collaborator

bgamari commented Nov 13, 2016

Aristid Breitkreuz notifications@github.com writes:

@bgamari Please feel free to go ahead and make the release. :-)

Will do. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants