Bump waitress from 2.1.1 to 2.1.2

[dependabot]

Bumps waitress from 2.1.1 to 2.1.2.

Changelog

Sourced from waitress's changelog.

2.1.2

Bugfix

- When expose_tracebacks is enabled waitress would fail to properly encode
  unicode thereby causing another error during error handling. See
  https://github.com/Pylons/waitress/pull/378

Header length checking had a calculation that was done incorrectly when the
data was received across multple socket reads. This calculation has been
corrected, and no longer will Waitress send back a 413 Request Entity Too
Large. See Pylons/waitress#376

Security Bugfix

• in 2.1.0 a new feature was introduced that allowed the WSGI thread to start sending data to the socket. However this introduced a race condition whereby a socket may be closed in the sending thread while the main thread is about to call select() therey causing the entire application to be taken down. Waitress will no longer close the socket in the WSGI thread, instead waking up the main thread to cleanup. See Pylons/waitress#377

Commits

• 0aa4879 Remove change of default for clear_untrusted_proxy_headers
• 2784628 Revert "Merge pull request #370 from Yourun-proger/del_warnings"
• 479df63 Prep 2.1.2
• 4f6789b Merge pull request #377 from Pylons/bugfix/select-closed-socket-race
• 1952050 Merge pull request #379 from Pylons/enhancement/pyupgrade-3.7
• 8f5b473 pyupgrade 3.7
• c7a3d7e Only close socket in the main thread
• 7c3739b Merge pull request #376 from Pylons/bugfix/header-calculation
• 3066fdd Merge pull request #378 from Pylons/bugfix/expose_tracebacks-encode-error
• 4467d76 Fix tests to assume body is bytes
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

[KTAtkinson]

Considering there are no security patches or needed bugfixes in this version,a 94% compatibility rating seems like a little more risk than I would like. Thoughts @nsheaps?

[nsheaps]

@KTAtkinson I don't think the change is that drastic considering the actual code changes, but I'm not clear on how to ensure that this works properly for all of our use cases other than merging and having people try it out (beyond the tests that currently exist). We could upgrade some of the services we own and test it out there but based on our past upgrade experiences I don't think that's sufficient unfortunately.

[nsheaps]

Our testing methodology has improved to the point where we should be able to validate this

[KTAtkinson]

Should go out with next release.

[nsheaps]

Thanks Katie!

🏃