start by opening a new issue describing the bug or feature you're intending to
fix. Even if you think it's relatively minor, it's helpful to know what people
are working on. And as mentioned above, API changes should be discussed
thoroughly before moving to code.

Some examples of types of pull requests that are immediately helpful:

  - Fixing a bug without changing a public API.
  - Fixing or improving documentation.

    /** The key used for language field identification */
    private static final String LANG_KEY = "lang";

    /** The underlying map that this DocMap wraps */
    private final Map<String, Object> parent;

    /**
     * Constructor that creates a DocMap wrapping the given parent map.
     *
     * @param parent the map to wrap and delegate operations to
     */

        assertNotNull(exception.getStackTrace());
        assertTrue(exception.getStackTrace().length > 0);
        assertNull(exception.getCause());
    }

    public void test_inheritance() {
        // Test that ResultOffsetExceededException is a subclass of FessSystemException
        ResultOffsetExceededException exception = new ResultOffsetExceededException("Test message");

        assertTrue(exception instanceof FessSystemException);

            .that(comparedUsingComparatorMethods)
            .isEqualTo(comparedUsingComparisonChain);
      }
    }
  }

  static class Bar {
    private final boolean isBaz;

    Bar(boolean isBaz) {
      this.isBaz = isBaz;
    }

    boolean isBaz() {
      return isBaz;
    }
  }

  /**

		}
	}
}

func TestEndianBaseCompare(t *testing.T) {
	// This test compares byte slices that are almost identical, except one
	// difference that for some j, a[j]>b[j] and a[j+1]<b[j+1]. If the implementation
	// compares large chunks with wrong endianness, it gets wrong result.
	// no vector register is larger than 512 bytes for now
	const maxLength = 512
	a := make([]byte, maxLength)
	b := make([]byte, maxLength)

        attachArtifact(project, artifact, path);
    }

    /**
     * Attaches a produced artifact to the project at the specified path. This is the base method
     * that the other attachArtifact methods delegate to.
     *
     * @param project the project to attach the artifact to
     * @param artifact the produced artifact to attach
     * @param path the path to the artifact file

* Federated deployment controller that supports the same api as the regular kubernetes deployment controller. ([#34109](https://github.com/ku...

        assertEquals("test_stackTrace", stackTrace[0].getMethodName());
    }

    public void test_serialization() {
        // Test that the exception has proper serialVersionUID
        DataStoreException exception = new DataStoreException("Serialization test");

        // Check that it's a RuntimeException and can be thrown
        try {
            throw exception;
        } catch (DataStoreException e) {

   witnesses, please include them as well.
 * Your account of what occurred, and if you believe the incident is ongoing. If there is a publicly
   available record (e.g. a mailing list archive or a public IRC logger), please include a link.
 * Any additional information that may be helpful.

After filing a report, a representative from the Square Code of Conduct committee will contact you

    /*
     * In principle, a Multimap implementation could add e3 first before failing on the null. But
     * that seems unlikely enough to be worth complicating the test over, especially if there's any
     * chance that a permissive test could mask a bug.
     */
    expectUnchanged();
    // Be extra thorough in case internal state was corrupted by the expected null.