assertThat("Thu, 01 Jan 1970 00:00:00 GMT".toHttpDateOrNull()!!.time).isEqualTo(0L)
    assertThat("Fri, 06 Jun 2014 12:30:30 GMT".toHttpDateOrNull()!!.time).isEqualTo(1402057830000L)

    // RFC 850, obsoleted by RFC 1036 with GMT.
    assertThat("Thursday, 01-Jan-70 00:00:00 GMT".toHttpDateOrNull()!!.time).isEqualTo(0L)
    assertThat("Friday, 06-Jun-14 12:30:30 GMT".toHttpDateOrNull()!!.time).isEqualTo(1402057830000L)

private val BROWSER_COMPATIBLE_DATE_FORMAT_STRINGS =
  arrayOf(
    // HTTP formats required by RFC2616 but with any timezone:
    // RFC 822, updated by RFC 1123 with any TZ.
    "EEE, dd MMM yyyy HH:mm:ss zzz",
    // RFC 850, obsoleted by RFC 1036 with any TZ.
    "EEEE, dd-MMM-yy HH:mm:ss zzz",
    // ANSI C's asctime() format
    "EEE MMM d HH:mm:ss yyyy",
    // Alternative formats:
    "EEE, dd-MMM-yyyy HH:mm:ss z",

                    <mxGeometry relative="1" as="geometry">
                        <mxPoint x="1030.0000000000005" y="649.9999999999995" as="sourcePoint"/>
                        <mxPoint x="850" y="540.0000000000005" as="targetPoint"/>
                        <Array as="points">
                            <mxPoint x="1030" y="540"/>
                        </Array>
                    </mxGeometry>

                    <mxGeometry relative="1" as="geometry">
                        <mxPoint x="1030.0000000000005" y="649.9999999999995" as="sourcePoint"/>
                        <mxPoint x="850" y="540.0000000000005" as="targetPoint"/>
                        <Array as="points">
                            <mxPoint x="1030" y="540"/>
                        </Array>
                    </mxGeometry>

                    <mxGeometry relative="1" as="geometry">
                        <mxPoint x="1030.0000000000005" y="649.9999999999995" as="sourcePoint"/>
                        <mxPoint x="850" y="540.0000000000005" as="targetPoint"/>
                        <Array as="points">
                            <mxPoint x="1030" y="540"/>
                        </Array>
                    </mxGeometry>

                    <mxGeometry relative="1" as="geometry">
                        <mxPoint x="1030.0000000000005" y="649.9999999999995" as="sourcePoint"/>
                        <mxPoint x="850" y="540.0000000000005" as="targetPoint"/>
                        <Array as="points">
                            <mxPoint x="1030" y="540"/>
                        </Array>
                    </mxGeometry>

`applyStyle` with a custom implementation.\n   *\n   * This modifier has `850` as `order` value to maintain backward compatibility\n   * with previous versions of Popper.js. Expect the modifiers ordering method\n   * to change in future major versions of the library.\n   *\n   * @memberof modifiers\n   * @inner\n   */\n  computeStyle: {\n    /** @prop {number} order=850 - Index used to define the order of execution */\n    order: 850,\n    /** @prop {Boolean} enabled=true - Whether the modifier is enabled...

f(t.bottom<o.top||t.left>o.right||t.top>o.bottom||t.right<o.left){if(!0===e.hide)return e;e.hide=!0,e.attributes['x-out-of-boundaries']=''}else{if(!1===e.hide)return e;e.hide=!1,e.attributes['x-out-of-boundaries']=!1}return e}},computeStyle:{order:850,enabled:!0,fn:function(e,t){var o=t.x,n=t.y,i=e.offsets.popper,r=D(e.instance.modifiers,function(e){return'applyStyle'===e.name}).gpuAcceleration;void 0!==r&&console.warn('WARNING: `gpuAcceleration` option moved to `computeStyle` modifier and will not...

* Update [External Links](https://fastapi.tiangolo.com/external-links/) with new links and dynamic GitHub projects with `fastapi` topic. PR [#850](https://github.com/tiangolo/fastapi/pull/850).
* Fix Peewee `contextvars` handling in docs: [SQL (Relational) Databases with Peewee](https://fastapi.tiangolo.com/advanced/sql-databases-peewee/). PR [#879](https://github.com/tiangolo/fastapi/pull/879).