Hanfei Shen

Encountering similar issue here. Spawned the server inside of flask/werkzeug just like this https://github.com/ZwickyTransientFacility/alertbase/blob/87d642fbd2ba4d7c77640450f269820571192376/test/test_blobstore.py#L14 The root cause maybe similar to this https://github.com/localstack/localstack/issues/459#issuecomment-346756560.

Here's the code to reproduce: ```python import boto3.session import moto.server import pytest import threading import werkzeug TEST_BUCKET = 'test-bucket' @pytest.fixture def s3_server(): ip = "127.0.0.1" port = "5287" app =...

It's the same as just using `moto_server` because `moto_server` uses `werkzeug` underlying as well.

looks like gunicorn has the same behavior: https://github.com/benoitc/gunicorn/blob/master/gunicorn/http/wsgi.py#L136 Test code: ```python import gunicorn.app.base import moto.server class StandaloneApplication(gunicorn.app.base.BaseApplication): def __init__(self, app, options=None): self.options = options or {} self.application = app super().__init__()...

waitress drops headers containing `_`: https://github.com/Pylons/waitress/blob/master/src/waitress/parser.py#L231 ```python import waitress import moto.server ip = "127.0.0.1" port = "5287" app = moto.server.DomainDispatcherApplication( moto.server.create_backend_app, service="s3", ) app.debug = True waitress.serve(app, port=5287) ```

same as bjoern: https://github.com/jonashaag/bjoern/blob/master/bjoern/request.c#L154

@bblommers @thehesiod it seems not many other alternatives out there. Do you guys have any suggestion on this?

@mur-wtag The related spec is one of some specs never get executed because the filenames of those specs not having the suffix `_spec`. And 3 of 4 are failed now....

Having the same issue here. https://github.com/kubernetes/autoscaler/blob/852ea800914cae101824687a71236f7688ee653d/cluster-autoscaler/cloudprovider/aws/auto_scaling_groups.go#L220 `SetDesiredCapacity` will not return any error related to `InsufficientInstanceCapacity` according to its [doc][1]. We might need to check the scaling activities by calling [DescribeScalingActivities][2]....

Thanks for fighting against the bad network. The retry facility would be even more useful if it could be extracted to a decorator.