http-types 0.11 test failures

[DanBurton]

As noted in the changelog for http-types

• 0.11 [2017-11-29]
  Remove dependency on blaze-builder. (Note that as a side effect of this, URI encoding is now using lower-case rather than uppercase hexadecimal.)

A number of test suites are now failing, apparently because they expect URI encoding to produce uppercase hexadecimal when it now produces lowercase.

• Spock-core
• amazonka-ec2
• amazonka-s3
• amazonka-sqs
• ginger

I'm going to check with the maintainers of these projects to see what they think about the issue and whether we should proceed with http-types 0.11.

[DanBurton]

Issues filed with:

• Spock-core: Spock-core test failure with http-types 0.11 agrafix/Spock#138
• amazonka-*: Signing issue with http-types 0.11 and query strings with hex encoding brendanhay/amazonka#440
• ginger: Test failure with http-types 0.11 tdammers/ginger#13

The person who filed the issue with amazonka noted that the URI spec says:

For consistency, URI producers and
normalizers should use uppercase hexadecimal digits for all percent-
encodings.

It is my opinion, for this reason, that we should not accept http-types 0.11 into Stackage.

I have opened an issue on http-types asking the maintainer to go back to uppercasing URI encodings. aristidb/http-types#83

[DanBurton]

We are anticipating a release of http-types 0.12, which will address this issue.

[aristidb]

http-types 0.12 is released now