- Sort Score
- Result 10 results
- Languages All
Results 11 - 13 of 13 for mypolicy (0.03 sec)
-
doc/godebug.md
Go 1.22 added a new [`crypto/x509.Certificate`](/pkg/crypto/x509/#Certificate) field, [`Policies`](/pkg/crypto/x509/#Certificate.Policies), which supports certificate policy OIDs with components larger than 31 bits. By default this field is only used during parsing, when it is populated with policy OIDs, but not used during marshaling. It can be used to marshal these larger OIDs, instead of the existing PolicyIdentifiers field, by using the
Registered: Tue Sep 09 11:13:09 UTC 2025 - Last Modified: Tue Jul 08 18:30:38 UTC 2025 - 22.9K bytes - Viewed (0) -
fess-crawler/src/main/resources/org/codelibs/fess/crawler/mime/tika-mimetypes.xml
<mime-type type="application/wordperfect5.1"/> <mime-type type="application/wsdl+xml"> <glob pattern="*.wsdl"/> </mime-type> <mime-type type="application/wspolicy+xml"> <glob pattern="*.wspolicy"/> </mime-type> <mime-type type="image/x-tga"> <alias type="image/x-targa"/> <!-- trailer bytes: 54 52 55 45 56 49 53 49 4F 4E 2D 58 46 49 4C 45 2E 00Registered: Sun Sep 21 03:50:09 UTC 2025 - Last Modified: Thu Mar 13 08:18:01 UTC 2025 - 320.1K bytes - Viewed (1) -
RELEASE.md
non-experimental `Policy`, there is no loss scale associated with the `Policy`, and `Model.compile` wraps the optimizer with a `LossScaleOptimizer` if and only if the policy is a `"mixed_float16"` policy. If you previously passed a `LossScale` to the experimental `Policy`, consider just removing it, as the default loss scaling behavior is usually what you want. If you really want to customize the loss scaling behavior, you can wrap your optimizer with a `LossScaleOptimizer` before passing it to `Model.compile`....
Registered: Tue Sep 09 12:39:10 UTC 2025 - Last Modified: Mon Aug 18 20:54:38 UTC 2025 - 740K bytes - Viewed (3)