)
            for reply in comment.replies.nodes:
                if reply.author:
                    authors[reply.author.login] = reply.author
                    if reply.author.login != discussion_author_name:
                        author_time = discussion_commentors.get(
                            reply.author.login, reply.createdAt
                        )

        }
        return Long.parseLong(value);
    }

    /**
     * Gets the reply URL for Entra ID authentication.
     * Uses new entraid.reply.url key with fallback to legacy aad.reply.url.
     * @param request The HTTP servlet request.
     * @return The reply URL.
     */
    protected String getReplyUrl(final HttpServletRequest request) {

            responseData.setContentLength(0);
            ftpClientQueue.offer(client);
        }
    }

    /**
     * Validates the FTP request by checking the reply code from the FTP server.
     * If the reply code indicates an error, a CrawlingAccessException is thrown.
     *
     * @param client the FTPClient instance to validate
     * @throws CrawlingAccessException if the FTP request failed
     */

				"application/fits",
				"application/font-tdpfr",
				"application/h224",
				"application/http",
				"application/hyperstudio",
				"application/ibe-key-request+xml",
				"application/ibe-pkg-reply+xml",
				"application/ibe-pp-data",
				"application/iges",
				"application/illustrator",
				"application/im-iscomposing+xml",
				"application/index",
				"application/index.cmd",

## Date

2025-08-06

## Context

Our codebase uses `null` extensively to represent an absence of value or optionality of the argument.
We utilize nullness annotations in Java code and somewhat rely on IDE warnings to guide us.
However, the Java code we have is not fully annotated, which causes several consequences:
* IDE warnings can be misleading

    task.cancel(false);
    assertTrue(task.isDone());
    assertTrue(task.isCancelled());
    assertEquals(1, runLatch.getCount());

    // Wait for the listeners to be called, don't rely on the same-thread exec.
    listenerLatch.await(5, SECONDS);
    assertTrue(task.isDone());
    assertTrue(task.isCancelled());

    // Make sure we didn't run anything.
    assertEquals(1, runLatch.getCount());

 * [OkHttp Profiler](https://plugins.jetbrains.com/plugin/11249-okhttp-profiler): An IntelliJ plugin for monitoring OkHttp calls.
 * [OkReplay](https://github.com/airbnb/okreplay): Record and replay OkHttp network interaction in your tests.
 * [okhttp-signpost](https://github.com/pakerfeldt/okhttp-signpost): OAuth signing with signpost and OkHttp.

    task.cancel(false);
    assertTrue(task.isDone());
    assertTrue(task.isCancelled());
    assertEquals(1, runLatch.getCount());

    // Wait for the listeners to be called, don't rely on the same-thread exec.
    listenerLatch.await(5, SECONDS);
    assertTrue(task.isDone());
    assertTrue(task.isCancelled());

    // Make sure we didn't run anything.
    assertEquals(1, runLatch.getCount());

    newArchives.from(currentDistroJars)
    oldArchives.from(baselineJars)

    // binary breaking change checking setup
    onlyModified = false
    failOnModification = false // we rely on the custom report to fail or not
    ignoreMissingClasses = true // because of a missing scala.runtime.AbstractFunction0 class

    BinaryCompatibilityHelper.setupJApiCmpRichReportRules(
        delegate,

 *
 * <p>Tests should inherit from this class, and declare subtyping relationship with public methods
 * annotated by {@link TestSubtype}.
 *
 * <p>These declaration methods rely on Java static type checking to make sure what we want to
 * assert as subtypes are really subtypes according to javac. For example:
 *
 * {@snippet :
 * class MySubtypeTests extends SubtypeTester {