requests with the actual input and output keys used by the trainer code, or
    conversely, update the trainer code to name the input and output Tensors
    'inputs' and 'outputs', respectively. Signatures using the 'classify' and
    'regress' methods are not affected by this change; they will continue to
    standardize their input and output keys as before.
*   Add in-memory caching to the Dataset API.

                                    <div class="form-inline col-sm-9">
                                        <la:errors property="sortOrder"/>
                                        <input type="number" name="sortOrder" id="sortOrder"
                                               value="${f:h(sortOrder)}" class="form-control"
                                               min="0" max="100000">

        // Assert
        assertEquals(0, resultWithNull, "Should return 0 for null buffer");
        assertEquals(0, resultWithData, "Should return 0 regardless of input data");
    }

    @Nested
    class CreateResponseTests {

        @Test
        @DisplayName("createResponse returns Smb2LogoffResponse and requests CIFSContext config")

	return errors.Is(err, syscall.ENOSPC)
}

// Invalid argument, unsupported flags such as O_DIRECT
func isSysErrInvalidArg(err error) bool {
	return errors.Is(err, syscall.EINVAL)
}

// Input/output error
func isSysErrIO(err error) bool {
	return errors.Is(err, syscall.EIO)
}

// Check if the given error corresponds to EISDIR (is a directory).
func isSysErrIsDir(err error) bool {

                                            key="labels.dict_kuromoji_file"/></label>
                                    <div class="col-sm-9">
                                        <input type="file" id="kuromojiFile" name="kuromojiFile" class="form-control-file"/>
                                    </div>
                                </div>
                            </div>

                                            key="labels.dict_mapping_file"/></label>
                                    <div class="col-sm-9">
                                        <input type="file" id="charMappingFile" name="charMappingFile" class="form-control-file"/>
                                    </div>
                                </div>
                            </div>

                                            key="labels.dict_stopwords_file"/></label>
                                    <div class="col-sm-9">
                                        <input type="file" id="stopwordsFile" name="stopwordsFile" class="form-control-file"/>
                                    </div>
                                </div>
                            </div>

   */
  @SuppressWarnings("nullness") // test of a bogus call
  static void assertBasicUrlEscaperExceptPercent(UnicodeEscaper e) {
    // URL escapers should throw null pointer exceptions for null input
    try {
      e.escape((String) null);
      fail("Escaping null string should throw exception");
    } catch (NullPointerException x) {
      // pass
    }

    private final Class<?> clazz;

    private SubtypeOfPredicate(Class<?> clazz) {
      this.clazz = checkNotNull(clazz);
    }

    @Override
    public boolean apply(Class<?> input) {
      return clazz.isAssignableFrom(input);
    }

    @Override
    public int hashCode() {
      return clazz.hashCode();
    }

    @Override
    public boolean equals(@Nullable Object obj) {

 * want their output to be non-null in operations like `stream.map(myConverter)`, and we can
 * guarantee that as long as we also require the input type to be non-null[*] (which is a
 * requirement that existing callers already fulfill).
 *
 * Disclaimer: Part of the reason that callers are so well adapted to `Function<A, B>` may be that