}
  }

  /**
   * A special purpose queue/executor that dispatches listener events serially on a configured
   * executor. Each event can be added and dispatched as separate phases.
   *
   * <p>This class is very similar to {@link SequentialExecutor} with the exception that events can
   * be added without necessarily executing immediately.
   */
  private static final class PerListenerQueue<L> implements Runnable {

  - type: markdown
    attributes:
      value: >
        Comparing two approaches to a use case side by side can make it easier to examine the
        differences between them.


        Additionally, it's very useful to us if you can provide a "straw API" — what the
        method signatures would look like, for example, even if the method and class names are still

        assertEquals("value0", param.getValues()[0]);
        assertEquals("value999", param.getValues()[999]);
    }

    public void test_veryLongStrings() {
        // Test with very long strings
        StringBuilder longNameBuilder = new StringBuilder();
        for (int i = 0; i < 10000; i++) {
            longNameBuilder.append("a");
        }
        String longName = longNameBuilder.toString();

    public void test_constructor_withLongTypeAndMessage() {
        // Test constructor with long strings
        String type = "VeryLongTokenTypeNameForTestingPurposes";
        String message =
                "This is a very long error message that describes in detail why the access token is invalid and what went wrong during validation";
        InvalidAccessTokenException exception = new InvalidAccessTokenException(type, message);

                throw exception;
            });
        }
    }

    @Nested
    @DisplayName("Edge Cases")
    class EdgeCaseTests {

        @Test
        @DisplayName("Should handle very long messages")
        void testVeryLongMessage() {
            StringBuilder longMessage = new StringBuilder();
            for (int i = 0; i < 10000; i++) {
                longMessage.append("x");
            }

        Smb2LeaseKey key = leaseManager.requestLease(path, requestedState);
        assertNotNull(leaseManager.getLease(key));

        // Wait a bit and then cleanup with a very short expiration time
        Thread.sleep(10);
        int cleaned = leaseManager.cleanupExpiredLeases(1); // 1ms expiration

        assertEquals(1, cleaned);
        assertNull(leaseManager.getLease(key));
    }

You can also read more about them in the <a href="https://en.wikipedia.org/wiki/Environment_variable" class="external-link" target="_blank">Wikipedia for Environment Variable</a>.

In many cases it's not very obvious how environment variables would be useful and applicable right away. But they keep showing up in many different scenarios when you are developing, so it's good to know about them.

Or you might have any other way to communicate with the WebSocket endpoint.

---

But for this example, we'll use a very simple HTML document with some JavaScript, all inside a long string.

This, of course, is not optimal and you wouldn't use it for production.

In production you would have one of the options above.

   * thus a motivated caller may be able to expose the reference to another thread that would then
   * call cancel() and be unable to cancel the delegate.
   * There are a number of ways to solve this, none of which are very pretty, and it is currently
   * believed to be a purely theoretical problem (since the other actions should supply sufficient
   * write-barriers).
   */

  @LazyInit private @Nullable ListenableFuture<V> delegateRef;

        assertEquals("short", result);
    }

    @Test
    void testReadStringWithMaxLengthExceeded() {
        smb.useUnicode = false;
        byte[] buffer = "a very long string that exceeds max length".getBytes();
        assertThrows(RuntimeException.class, () -> {
            smb.readString(buffer, 0, 10, false);
        });
    }

    @Test
    void testEncodeDecode() {