for _, cat := range testcats {
		for _, test := range cat.tests {
			parser.allowABI = cat.allowABI
			parser.errorCount = 0
			parser.lineNum++
			if !parser.pseudo(test.pseudo, tokenize(test.operands)) {
				t.Fatalf("Wrong pseudo-instruction: %s", test.pseudo)
			}
			errorLine := buf.String()
			if test.expected != errorLine {
				t.Errorf("Unexpected error %q; expected %q", errorLine, test.expected)
			}
			buf.Reset()
		}
	}

				got := 0
				for b := range in {
					PutByteBuffer(b)
					got++
				}
				if got != requests {
					return NewRemoteErrf("wrong number of requests. want %d, got %d", requests, got)
				}
				return nil
			},

			Subroute:    "some-subroute",
			OutCapacity: 1,
			InCapacity:  1, // Only one message buffered.
		}))

            IllegalStateException exception = assertThrows(IllegalStateException.class, () -> {
                testRequest.encode(buffer, 0);
            });

            assertTrue(exception.getMessage().contains("Wrong size calculation"));
        }
    }

    // Test implementation classes
    private static class TestServerMessageBlock2Request extends ServerMessageBlock2Request<TestServerMessageBlock2Response> {

  - The project ID will be auto-generated as `Gradle_MyTestBranch`. If not, you probably selected wrong parent, the "Parent project" should be `Gradle`.
- Now click on the new project you just created. The URL should be `https://builds.gradle.org/admin/editProject.html?projectId=Gradle_<MyTestBranch>`.

    stem from Plexus Classworlds originally.
    <p><i>Notice:</i> this documentation is generated from a Modello model but the code executed is not generated
    from this descriptor. Please report if you find anything wrong.</p>
  ]]></description>
  <defaults>
    <default>
      <key>package</key>
      <value>extension descriptor XML documentation (no java generation)</value><!-- intentionally non-buildable value -->
    </default>

For any non-trivial change, we need to be able to answer these questions:

* Why is this change done? What's the use case?
* For user-facing features, what will the API look like?
* What test cases should it have? What could go wrong?
* How will it roughly be implemented? We'll happily provide code pointers to save you time.

We may ask you to answer these questions directly in the GitHub issue or (for large changes) in a shared Google Doc.

    * An example is `404`, for a "Not Found" response.
    * For generic errors from the client, you can just use `400`.
* `500 - 599` are for server errors. You almost never use them directly. When something goes wrong at some part in your application code, or server, it will automatically return one of these status codes.

/// tip

    @Test
    @DisplayName("Should reject null key")
    void testNullKey() {
        assertThrows(IllegalArgumentException.class, () -> new Smb2LeaseKey(null));
    }

    @Test
    @DisplayName("Should reject wrong size key")
    void testWrongSizeKey() {
        assertThrows(IllegalArgumentException.class, () -> new Smb2LeaseKey(new byte[15]));
        assertThrows(IllegalArgumentException.class, () -> new Smb2LeaseKey(new byte[17]));

     */
    @Override
    public boolean verifySignature(final byte[] buffer, final int i, final int size) {
        // observed too that signatures on error responses are sometimes wrong??
        // Looks like the failure case also is just reflecting back the signature we sent

        // with SMB3's negotiation validation it's no longer possible to ignore this (on the validation response)

   * would be the right tool for the job here: {@code @Nullable} is the annotation that we're trying
   * to get rid of, and {@code @NonNull} would be wrong for our use case for the same reason as
   * {@code requireNonNull}: Our use case is the one in which {@code T} has parametric nullness—and
   * thus its value may be legitimately {@code null}.)
   */
  @ParametricNullness