addCreateContext(leaseContext);
        setRequestedOplockLevel(SMB2_OPLOCK_LEVEL_LEASE);
    }

    /**
     * Remove lease contexts and fall back to oplock
     * @param oplockLevel the oplock level to fall back to
     */
    public void fallbackToOplock(byte oplockLevel) {
        // Remove any lease contexts
        if (this.createContexts != null) {

            assertEquals(SmbComTransaction.TRANSACTION_BUF_SIZE, buffer.length, "Buffer should have correct size");
            buffers.add(buffer);
        }

        // When - Release all buffers back
        for (byte[] buffer : buffers) {
            BufferCache.releaseBuffer(buffer);
        }

        // Then - Should be able to get buffers again
        byte[] newBuffer = BufferCache.getBuffer();

  id 'elasticsearch.build-tools'
  id 'elasticsearch.eclipse'
}

group = 'org.elasticsearch.gradle'

// we update the version property to reflect if we are building a snapshot or a release build
// we write this back out below to load it in the Build.java which will be shown in rest main action
// to indicate this being a snapshot build or a release build.

    ...
```

Python will have to compare the whole `stanleyjobso` in both `stanleyjobsox` and `stanleyjobson` before realizing that both strings are not the same. So it will take some extra microseconds to reply back "Incorrect username or password".

#### The time to answer helps the attackers { #the-time-to-answer-helps-the-attackers }

                    <span class="btn btn-info" role="button">Merge release to master</span>
                  </summary>
                  <div class="well">
                    Merging `release` back to `master` is a regular operation you’re free to do, at any time. Usually, you will see conflicts in `notes.md` or `accepted-public-api-changes.json`.

        // search

    }

    /**
     * Deletes job logs that ended before the specified number of days ago.
     * Used for cleaning up old log entries.
     *
     * @param days the number of days to look back from the current time
     */
    public void deleteBefore(final int days) {
        final long oneday = 24 * 60 * 60 * 1000L;

        assertTrue(queryCommand.lowercaseWildcard);

        // Test setting to false
        queryCommand.setLowercaseWildcard(false);
        assertFalse(queryCommand.lowercaseWildcard);

        // Test setting back to true
        queryCommand.setLowercaseWildcard(true);
        assertTrue(queryCommand.lowercaseWildcard);
    }

    @Test
    public void test_convertWildcardQuery_withBoost() throws Exception {

            <offlineLink>
              <url>https://javadoc.io/doc/com.google.j2objc/j2objc-annotations/latest/</url>

* `"request"`: start the dependency before the *path operation function* that handles the request (similar to when using `"function"`), but end **after** the response is sent back to the client. So, the dependency function will be executed **around** the **request** and response cycle....

   * Finalizer directly with no problems.
   *
   * If this library is loaded in an application class loader, it's important that Finalizer not
   * have a strong reference back to the class loader. Otherwise, you could have a graph like this:
   *
   * Finalizer Thread runs instance of -> Finalizer.class loaded by -> Application class loader