### Target language

Translate to Ukrainian (українська).

Language code: uk.

### Grammar and tone

- Use polite/formal address consistent with existing Ukrainian docs (use “ви/ваш”).
- Keep the tone concise and technical.
- Use one style of dashes. For example, if text contains "-" then use only this symbol to represent a dash.

### Headings

- Follow existing Ukrainian heading style; keep headings short and instructional.

it is unlikely that we'll be able to remove `null` entirely.

After migrating to Java 8, we can use pluggable type checkers to ensure that our annotations are consistent, 
and there are no missing null checks.

## Decision

Use "NullAway" in JSpecify mode to check for null-related errors in Java code.

   * may prefer to invoke that method directly; this method exists only for consistency with the
   * other utilities in this package.
   *
   * <p><b>Note:</b> this method simply delegates to the JDK method {@link Float#compare}. It is
   * provided for consistency with the other primitive types, whose compare methods were not added
   * to the JDK until JDK 7.
   *

        // Each call should return a new instance
        assertNotSame(option1, option2);
    }

    @Test
    public void test_provideMappingOption_consistency() {
        // Test that multiple calls provide consistent configuration
        JsonMappingOption option1 = provider.provideMappingOption();
        JsonMappingOption option2 = provider.provideMappingOption();

        assertEquals(option1.getFieldNaming(), option2.getFieldNaming());

### Quotes

- Prefer Japanese corner brackets 「」 in normal prose when quoting a term.
- Do not change quotes inside inline code, code blocks, URLs, or file paths.

### Ellipsis

- Keep ellipsis style consistent with existing Japanese docs (commonly `...`).
- Never change `...` in code, URLs, or CLI examples.

### Preferred translations / glossary

Use the following preferred translations when they apply in documentation prose:

package org.codelibs.fess.exception;

import org.apache.lucene.queryparser.classic.ParseException;

/**
 * Exception thrown when a query parsing error occurs.
 * This exception wraps Lucene's ParseException to provide consistent error handling
 * within the Fess search framework.
 *
 */
public class QueryParseException extends FessSystemException {

    /** Serial version UID for serialization compatibility */

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

/**
 * Base test class providing common test infrastructure and utilities.
 * All test classes should extend this to ensure consistent test setup.
 */
@ExtendWith(MockitoExtension.class)
public abstract class BaseTest {

    protected final Logger logger = LoggerFactory.getLogger(getClass());

    @BeforeEach
    void baseSetUp() {

        assertSame(invertibleCryptographer, first);
    }

    @Test
    public void test_providePrimaryInvertibleCryptographer_consistency() {
        // Test multiple calls return consistent results
        for (int i = 0; i < 10; i++) {
            InvertibleCryptographer cryptographer = securityResourceProvider.providePrimaryInvertibleCryptographer();
            assertNotNull(cryptographer);

 */
package org.codelibs.fess.exception;

/**
 * This exception is thrown when a storage-related error occurs.
 * It can be used to wrap underlying storage exceptions, providing a
 * consistent error handling mechanism for storage operations.
 */
public class StorageException extends FessSystemException {
    private static final long serialVersionUID = 1L;

    /**

            ndrShort1.encode(encodeBuffer);

            NdrShort ndrShort2 = new NdrShort(0);
            ndrShort2.decode(decodeBuffer);

            // Then: Should maintain masked value consistency
            verify(encodeBuffer).enc_ndr_short(maskedValue);
            verify(decodeBuffer).dec_ndr_short();
            assertEquals(maskedValue, ndrShort1.value);
            assertEquals(maskedValue, ndrShort2.value);