Brew is listed as the recommended way of installing httpie on macOS. However, it doesn't work with auth plugins.

For example, if you pip3 install requests-hawk and then run http --help hawk will not show as an auth type. If you pip3 install httpie-oauth it will install httpie via pip as a dependency and overwrite the brew installed link in /usr/local/bin/http and now all the plugins wil

tldr; in multi-process environment (Celery) sessions might lead to request/responses being mixed up.

It is unsafe to use Session in a multi-process environment - if the fork happens after Session initialisation the underlying connection pool will be shared across both processes, leading to potentially dangerous and hard to debug issues.

I'm not sure what should happen - whather a code change

1. What would you like to have changed?

Right now caddy2 has two config adapters: Caddyfile and JSON.
I have to admit, that I am not a big fan of json, because it's not possible to insert comments and it's difficult to write manual.

JSON is a format that should be used only from one comput

Problem Description

The option --set doesn't work

Steps to reproduce the behavior:

1. The command mitmdump.exe -p 8088 --set ssl_version_client=all --set ssl_version_server=all doesn't change configuration

2. mitmdump.exe -p 8088 --options doesn't show changes

3. mitmdump.exe --options returns Error starting proxy server: OSError(98, 'Address already in use')

4. A default co

On the man page --create-dirs should mention that it uses odd
drwxr-x--- vs. -rw-r--r-- permissions for files downloaded.

One would think they would be
drwxr-xr-x and -rw-r--r--, or
drwxr-x--- and -rw-r-----

Also mention how to change it. curl 7.67.0, Debian.

I can't find any other explanation or formulas for results like median, average, min/max, req/sec in documentation, readme or web page. On the documentation page I tried basic scenario to search result/s and get no relevant page.

I found this question on stackoverflow, so I'm not only one who didn't understand it
https://stackoverflow.com/questions/39665250/locust-result-summary-how-to-underst

If you're using proxies with requests-html and rendering JS sites is all good. Once you render a website pyppeteer don't know about this proxies and will expose your IP. This is an undesired behavior when scraping with proxies.

The idea is that whenever someone passes in proxies to the session object or any method call, make pyppeteer also use these proxies. #265

Long story short

Regression of #1188

Expected behaviour

Tests pass on armv7l

Actual behaviour

Test run fails at test_cookiejar.py:383: OverflowError

Steps to reproduce

Run tests

Your environment

linux 4.19
nixos 20.03
arm v7l
python 3.7
aiohttp client-3.6.2

Log

        ts_before = datetime.datetime(
            1975, 1, 1, tzinfo=datetim

What is the expected behavior?

Expected that the following would block requests to https://domain.com

nock('https://domain.com');

What is the actual behavior?
It doesn't! It looks like the scope will only intercept the request once a complete interception (scope, request, reply) is in place.

Possible solution
Perhaps update the docs to clarify this? I don't real

What would be the minimal IAM Policy for deploying, I know the policy on the website, but that has also access to EC2 and is quite broad. For example I would not need to control a domain from there.

Like it would be a role that you could put on Travis-CI and not worry about them deleting your EC2 instances.

I tried deleting everything other than Lambda, API Gateway and S3, but then I began

Let's support at least reading "b3" header from a single string, most commonly traceid-spanid-1
It would also be nice to support optionally writing this, especially in message providers or others with constrained environments.

Expected behavior

As discussed on openzipkin/b3-propagation#21 and first implemented here: https://github.com/openzipkin/brave/blob/master/brave/src/main/java/bra

Currently, we ask contributors to strive for consistency with existing code, but it would be helpful to clarify the following regarding docstrings:

• Docstrings should begin with a short (~70 characters or less) summary line that ends in a period.
• The summary line should begin immediately after the opening quotes (do not add a line break before the summary line)
• The summary line should de