Summary

The documentation "activate_announcer_on_command_failure" is not helpful for users as it misses information a

Today, many string methods cause symbolic strings to be "materialized" (the symbolic string becomes a concrete string and then gets handed to the native string implementation).

For some of these operations, this is likely the best we can do, but others may be implementable with the SMT solver directly. This is a list of those methods, and we'll check them off when we've decided that we have th

We need a page in the docs that tell users that to mock they should use from unittest import mock.

We should note that the mock.patch decorators don't currently work, and that we need to use the context managers instead.

Right now we just use the standard C random library, but really it'd be nice if the brute force fuzzer could do consistent tests across platforms, for various purposes. We probably need our own PRNG, something like:

https://www-cs-faculty.stanford.edu/~knuth/news02.html#rng

or

https://github.com/cmcqueen/simplerandom

I'm not sure what's best. We'd like decentish quality, maybe, and d

Documenting an issue uncovered by @flokli in a private repo that I'll describe here:

curl-runnings uses http-client-tls, which apparently has no nice way to configure your own cert file.

@flokli opened snoyberg/http-client#461, so http-client-tls honors SSL_CERT_FILE.

He recommended Switching Network.HTTP.Client.TLS to Network.HTTP.Client.OpenSSL and adjusting noVerifyTlsSettings should b