edwards25519.NewScalar().MultiplyAdd(k, &priv.s, r) copy(signature[:32], R.Bytes()) copy(signature[32:], S.Bytes()) return signature } func Verify(pub *PublicKey, message, sig []byte) error { return verify(pub, message, sig) } func verify(pub *PublicKey, message, sig []byte) error { fipsSelfTest() fips140.RecordApproved() return verifyWithDom(pub, message, sig, domPrefixPure, "") } func VerifyPH(pub *PublicKey, message []byte, sig []byte, context string) error { fipsSelfTest() fips140.RecordApproved() if l := len(message);...

edwards25519.NewScalar().MultiplyAdd(k, &priv.s, r) copy(signature[:32], R.Bytes()) copy(signature[32:], S.Bytes()) return signature } func Verify(pub *PublicKey, message, sig []byte) error { return verify(pub, message, sig) } func verify(pub *PublicKey, message, sig []byte) error { fipsSelfTest() fips140.RecordApproved() return verifyWithDom(pub, message, sig, domPrefixPure, "") } func VerifyPH(pub *PublicKey, message []byte, sig []byte, context string) error { fipsSelfTest() fips140.RecordApproved() if l := len(message);...

* Add `auto_error` parameter to security utility functions. Allowing them to be optional. Also allowing to have multiple alternative security schemes that are then checked in a single dependency instead of each one verifying and returning the error to the client automatically when not satisfied. PR [#134](https://github.com/tiangolo/fastapi/pull/134).

    *   oneDNN optimizations can yield slightly different numerical results compared to when oneDNN optimizations are disabled due to floating-point round-off errors from
 different computation approaches and orders.
    *   To verify if oneDNN optimizations are on, look for a message with *"oneDNN custom operations are on"* in the log. If the exact phrase is not there, it means they are off.

* Making the `tf.function` type system fully available: