* Make connection failures visible in Ruby SDK
The underlying HTTP library, Typhoeus, requires you to be explicit about
error handling. Unfortunately, this also means that we can't assume that
`response.success?` will be false only when the HTTP status code is not
a 200; it could also be false when the request fails (timeouts, TLS
verification issues, etc.). This commit adds explicit error handling for
these cases.
* Update samples
* python: Let logging format messages on demand
* python: Use six more
* python: Remove unused imports
* python: flake8 fixes
* python: Make examples compatible with Python 3
* python: Spelling fixes
* add line break test to petstore-security-test.yaml
* add objc/swift security testing
* add go,scala,qt5cpp for security test
* add security test for typescript
* fix go security issue, fix consumes,produces line break
Previous ApiException message would simply print out the result of the
`curl_getinfo($curl)` call, which might be useful only if the developer
actually wanted very low-level information from curl about why a call
failed. The new message should print out a higher-level but more
informative, human-readable message. If necessary for debugging, the
ApiException's responseObject is set to the `curl_getinfo($curl)`.
Following #3224 this adds a `pom.xml` for executing `mvn
integration-test` on the PHP Swagger Petstore Security Client tests.
The `pom.xml` is identical to the one in
`samples/client/petstore/php/SwaggerClient-php/pom.xml` with only name
and artifactId changed.