- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for isStrict (0.14 sec)
-
RELEASE.md
# Release 2.5.0 ## Major Features and Improvements * Support for Python3.9 has been added. * `tf.data`: * `tf.data` service now supports strict round-robin reads, which is useful for synchronous training workloads where example sizes vary. With strict round robin reads, users can guarantee that consumers get similar-sized examples in the same step.
Registered: Tue Sep 09 12:39:10 UTC 2025 - Last Modified: Mon Aug 18 20:54:38 UTC 2025 - 740K bytes - Viewed (2) -
docs/en/docs/release-notes.md
* `File()` * The new parameter fields are: * `default_factory` * `alias_priority` * `validation_alias` * `serialization_alias` * `discriminator` * `strict` * `multiple_of` * `allow_inf_nan` * `max_digits` * `decimal_places` * `json_schema_extra` ...you can read about them in the Pydantic docs.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Fri Sep 05 12:48:45 UTC 2025 - 544.1K bytes - Viewed (0) -
src/main/java/org/codelibs/fess/mylasta/direction/FessConfig.java
/** * Get the value for the key 'cookie.search.parameter.same_site'. <br> * The value is, e.g. Lax <br> * comment: SameSite attribute for the search parameter cookie. Valid values: Lax, Strict, None * @return The value of found property. (NotNull: if not found, exception but basically no way) */ String getCookieSearchParameterSameSite(); /**
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Thu Jul 17 08:28:31 UTC 2025 - 525.6K bytes - Viewed (2) -
CHANGELOG/CHANGELOG-1.19.md
- `RequestedToCapacityRatioArgs` encoding is now strict ([#91603](https://github.com/kubernetes/kubernetes/pull/91603), [@pancernik](https://github.com/pancernik)) [SIG Scheduling]
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Wed Jan 05 05:42:32 UTC 2022 - 489.7K bytes - Viewed (0) -
lib/fips140/v1.0.0.zip
EXEMPLARY, OR // CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF // SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR // BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, // WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE // OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, // EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. // // See FIPS 197 for specification, and see Daemen and Rijmen's Rijndael submission...
Registered: Tue Sep 09 11:13:09 UTC 2025 - Last Modified: Wed Jan 29 15:10:35 UTC 2025 - 635K bytes - Viewed (0)