* rarely use it directly, in part because it does not provide direct access to the {@code Future}
 * result. (If you want such access, you may prefer {@link Futures#addCallback
 * Futures.addCallback}.) Still, direct {@code addListener} calls are occasionally useful:
 *
 * {@snippet :
 * final String name = ...;
 * inFlight.add(name);
 * ListenableFuture<Result> future = service.query(name);

 * rarely use it directly, in part because it does not provide direct access to the {@code Future}
 * result. (If you want such access, you may prefer {@link Futures#addCallback
 * Futures.addCallback}.) Still, direct {@code addListener} calls are occasionally useful:
 *
 * {@snippet :
 * final String name = ...;
 * inFlight.add(name);
 * ListenableFuture<Result> future = service.query(name);

        wagonManager.getArtifact(artifact, repo, transferListener, false);
        assertFalse(
                wagon.getTransferEventSupport().hasTransferListener(transferListener),
                "Transfer listener still registered after getArtifact");

        /* putArtifact */
        File sampleFile = getTestFile("target/test-file");
        FileUtils.fileWrite(sampleFile.getAbsolutePath(), "sample file");

        assertFalse(

      return entry.value;
    }
    entry = cacheEntry2;
    if (entry != null && entry.key == key) {
      // Promote second cache entry to first so the access pattern
      // [K1, K2, K1, K3, K1, K4...] still hits the cache half the time.
      addToCache(entry);
      return entry.value;
    }
    return null;
  }

  @Override
  void clearCache() {
    super.clearCache();
    cacheEntry1 = null;

# Extra Data Types { #extra-data-types }

Up to now, you have been using common data types, like:

* `int`
* `float`
* `str`
* `bool`

But you can also use more complex data types.

And you will still have the same features as seen up to now:

* Great editor support.
* Data conversion from incoming requests.
* Data conversion for response data.
* Data validation.
* Automatic annotation and documentation.

        assertEquals(0, bytesWritten, "Should return 0 bytes written for null source.");
        assertEquals(pos, NtlmMessage.readULong(dest, off), "Position should still be written for null source.");

        // Test with empty source array
        dest = new byte[20];
        bytesWritten = NtlmMessage.writeSecurityBufferContent(dest, pos, off, new byte[0]);

										href="/search?q=${f:u(q)}&ex_q=label%3a${f:u(countEntry.key)}&sdh=${f:u(fe:sdh(sh))}${fe:pagingQuery(null)}${fe:facetQuery()}${fe:geoQuery()}">
											${f:h(fe:label(countEntry.key))} 
											<span class="badge rounded-pill text-bg-secondary float-end">${f:h(countEntry.value)}</span>
									</la:link></li>
							</c:if>
						</c:forEach>
					</ul>
				</c:if>
			</c:forEach>

        CloseableUtil.closeQuietly(in);

        // Verify no column metadata
        assertNull(extractData.getValues("columns"));

        // But content should still be present
        final String content = extractData.getContent();
        assertTrue(content.contains("John Doe"));
    }

    public void test_delimiterDetection() {
        // The test.csv uses comma delimiter

     * attributes are asserted here only because server file systems may not
     * support filtering by all attributes (e.g. even though ATTR_DIRECTORY was
     * specified the server may still return objects that are not directories).
     */
    @Override
    public boolean accept(final SmbFile file) throws SmbException {
        return (file.getAttributes() & attributes) != 0;
    }

{* ../../docs_src/response_cookies/tutorial002_py39.py hl[1, 8:9] *}

And then you can return any object you need, as you normally would (a `dict`, a database model, etc).

And if you declared a `response_model`, it will still be used to filter and convert the object you returned.