// Act
        int actual = findNtStatusOrMinusOne(dosCode);

        // Assert
        assertEquals(-1, actual);
    }

    @Test
    @DisplayName("Structure: DOS_ERROR_CODES is non-null with [code,status] pairs")
    void dosErrorCodesStructureIsValid() {
        // Arrange & Act
        int[][] table = DosError.DOS_ERROR_CODES;

        // Assert
        assertNotNull(table, "DOS_ERROR_CODES must not be null");

	}
	r.prevRune = -1
	n = copy(b, r.s[r.i:])
	r.i += int64(n)
	return
}

// ReadAt implements the [io.ReaderAt] interface.
func (r *Reader) ReadAt(b []byte, off int64) (n int, err error) {
	// cannot modify state - see io.ReaderAt
	if off < 0 {
		return 0, errors.New("bytes.Reader.ReadAt: negative offset")
	}
	if off >= int64(len(r.s)) {
		return 0, io.EOF
	}
	n = copy(b, r.s[off:])
	if n < len(b) {
		err = io.EOF

        assertTrue(result.contains("Trans2QueryFSInformation"));
        assertTrue(result.toLowerCase().contains(expectedHex.toLowerCase()));
    }

    @Test
    @DisplayName("Test object state after multiple operations")
    void testObjectStateAfterMultipleOperations() {
        trans2QueryFSInfo = new Trans2QueryFSInformation(config, FileSystemInformation.SMB_INFO_ALLOCATION);

   * addListener/SES.schedule. The later racy write in cancel() is not guaranteed to be observed,
   * however that is fine since the correctness is based on the atomic state in our base class. The
   * initial write to timer is never definitely visible to Fire.run since it is assigned after
   * SES.schedule is called. Therefore Fire.run has to check for null. However, it should be visible

        // Header length
        SMBUtil.writeInt2(64, buffer, bufferIndex + 4);
        // Credit charge
        SMBUtil.writeInt2(1, buffer, bufferIndex + 6);
        // Status
        SMBUtil.writeInt4(0, buffer, bufferIndex + 8);
        // Command - SMB2_SET_INFO (0x0011)
        SMBUtil.writeInt2(0x0011, buffer, bufferIndex + 12);
        // Credits

	input       chan *queueItem           // input for workers
	queue       chan *queueItem           // output from workers in order
	err         error                     // global error state, only touched by Reader.Read
	bufferPool  bpool.Pool[[]byte]        // pool of []byte objects for input
	kvDstPool   bpool.Pool[[]jstream.KVS] // pool of []jstream.KVS used for output

---

            (byte) 0x00, (byte) 0x00, // ChannelSequence
            (byte) 0x00, (byte) 0x00, // Reserved
            (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00, // Status
            (byte) 0x00, (byte) 0x00, // Command
            (byte) 0x00, (byte) 0x00, // CreditRequest/CreditResponse
            (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00, // Flags

Und Sie erhalten Editor-Unterstützung überall.

Selbst für Dinge in Listen:

<img src="/img/tutorial/body-nested-models/image01.png">

Sie würden diese Editor-Unterstützung nicht erhalten, wenn Sie direkt mit `dict`, statt mit Pydantic-Modellen arbeiten würden.

Aber Sie müssen sich auch nicht weiter um die Modelle kümmern, hereinkommende Dicts werden automatisch in sie konvertiert. Und was Sie zurückgeben, wird automatisch nach JSON konvertiert.

            searchPaging(data, form);
        });
    }

    /**
     * Returns to the search log list from a detail view.
     *
     * @param form the search form containing current state
     * @return HTML response for the search log list page
     */
    @Execute
    @Secured({ ROLE, ROLE + VIEW })
    public HtmlResponse back(final SearchForm form) {
        saveToken();