Cette syntaxe `@something` en Python est appelée un "décorateur".

Vous la mettez au dessus d'une fonction. Comme un joli chapeau décoratif (j'imagine que ce terme vient de là 🤷🏻‍♂).

Un "décorateur" prend la fonction en dessous et en fait quelque chose.

Dans notre cas, ce décorateur dit à **FastAPI** que la fonction en dessous correspond au **chemin** `/` avec l'**opération** `get`.

            byte[] buffer = new byte[10];
            int bufferIndex = 0;
            SMBUtil.writeInt2(4, buffer, bufferIndex); // Write structure size = 4
            SMBUtil.writeInt2(0, buffer, bufferIndex + 2); // Reserved field

            // When
            int bytesRead = response.readBytesWireFormat(buffer, bufferIndex);

            // Then
            assertEquals(4, bytesRead);
        }

        @Test

	},
	ErrMissingSignTag: {
		Code:           "AccessDenied",
		Description:    "Signature header missing Signature field.",
		HTTPStatusCode: http.StatusBadRequest,
	},
	ErrMissingSignHeadersTag: {
		Code:           "InvalidArgument",
		Description:    "Signature header missing SignedHeaders field.",
		HTTPStatusCode: http.StatusBadRequest,
	},
	ErrMalformedExpires: {

            assertFalse((flags & Type2Message.NTLMSSP_NEGOTIATE_TARGET_INFO) != 0);
        }

        @Test
        @DisplayName("toByteArray should exclude version field when flag is not set")
        void testToByteArray_NoNegotiateVersionFlag() throws IOException {
            // Given
            CIFSContext mockContext = createMockContext();

    void setUp() {
        // Directly set the deferred field on the mock
        mockNdrBuffer.deferred = mockDeferredBuffer;

        // Configure mocks for NdrBuffer interactions
        lenient().when(mockDeferredBuffer.derive(anyInt())).thenReturn(mockDeferredBuffer);
        lenient().doNothing().when(mockDeferredBuffer).advance(anyInt());
        // Set up index field for derive operations
        mockDeferredBuffer.index = 0;
    }

				return err
			}
			tw.curr = &sparseFileWriter{tw.curr, spd, 0}
		}
	*/
	return nil
}

func (tw *Writer) writeGNUHeader(hdr *Header) error {
	// Use long-link files if Name or Linkname exceeds the field size.
	const longName = "././@LongLink"
	if len(hdr.Name) > nameSize {
		data := hdr.Name + "\x00"
		if err := tw.writeRawFile(longName, data, TypeGNULongName, FormatGNU); err != nil {
			return err
		}
	}

            byte[] buffer = new byte[100];

            // Act
            int encodedSize = context.encode(buffer, 0);

            // Assert
            assertEquals(2, encodedSize); // Only count field
            assertEquals(0, buffer[0]); // cipher count
            assertEquals(0, buffer[1]);
        }

        @Test
        @DisplayName("Should decode context correctly")

For example, given the Go declaration <code>const bufSize =
1024</code>, assembly code can refer to the value of this constant
as <code>const_bufSize</code>.
</p>

<p>
Field offsets are of the form <code><i>type</i>_<i>field</i></code>.
Struct sizes are of the form <code><i>type</i>__size</code>.
For example, consider the following Go definition:
</p>

<pre>
type reader struct {
	buf [bufSize]byte

can now store only `null` when created using the protobuf content-type or stored in etcd using protobuf serialization (the default in 1.6).
JSON API clients should tolerate `null` values for such fields, and treat `null` and `[]` as equivalent in meaning unless specifically documented otherwise for a particular field. ([#44593](https://github.com/kubernetes/kubernetes/pull/44593))

        void testSizeCalculation() {
            // Note: The size() method in EncryptionNegotiateContext returns 4 as base,
            // while encode() only writes 2 bytes for the count field.
            // This appears to be an implementation inconsistency.
            context = new EncryptionNegotiateContext(mockConfig, new int[3]);
            assertEquals(4 + 6, context.size()); // 4 base + 3*2 for ciphers