When making a request with headers "Connection: keep-alive, Upgrade; Upgrade: websocket", the keep-alive should be ignored when checking if the request should be served by a Websocket, per IETF protocol document, the Connection header must include Upgrade, but is not limited to exactl
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
TPI [INFO] LOG 0 >> 2022-05-21 16:50:59 tpi-task.service: Failed with result 'timeout'.
TPI [INFO] Status: completed with errors •
It would be nice for the final logline to better reflect the timeout, for example:
TPI [INFO] LOG 0 >> 2022-05-21 16:50:59 tpi-task.service: Failed with result 'timeout'.
TPI [INFO] Status: stopped via timeout •
maybe with some pretty
Add a description, image, and links to the cloud-infrastructure topic page so that developers can more easily learn about it.
To associate your repository with the cloud-infrastructure topic, visit your repo's landing page and select "manage topics."
Describe the issue
Navigate to the following section https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ecs_patterns-readme.html#set-capacityproviderstrategies-for-queueprocessingec2service
... and you'll find the heading Set capacityProviderStrategies for QueueProcessingEc2Service ...
... the example is clearly for configuring a QueueProcessingFargateService
Links