import jcifs.internal.smb2.ServerMessageBlock2Request;
import jcifs.internal.smb2.Smb2Constants;
import jcifs.internal.util.SMBUtil;

/**
 * SMB2 Session Setup request message. This command is used to establish a security session
 * and authenticate a user to the server.
 *
 * @author mbechler
 *
 */
public class Smb2SessionSetupRequest extends ServerMessageBlock2Request<Smb2SessionSetupResponse> {

	tokens []Token  // Body of macro.
}

// Tokenize turns a string into a list of Tokens; used to parse the -D flag and in tests.
func Tokenize(str string) []Token {
	t := NewTokenizer("command line", strings.NewReader(str), nil)
	var tokens []Token
	for {
		tok := t.Next()
		if tok == scanner.EOF {
			break
		}
		tokens = append(tokens, Make(tok, t.Text()))
	}
	return tokens

Utiliser comme suit :

* Avoir une invite spécifique à la langue - `docs/{language code}/llm-prompt.md`.
* Effectuer une nouvelle traduction de ce document dans votre langue cible souhaitée (voir par exemple la commande `translate-page` de `translate.py`). Cela créera la traduction sous `docs/{language code}/docs/_llm-test.md`.
* Vérifier si tout est correct dans la traduction.

- "Removed the ability to run `kubectl exec [POD] [COMMAND]` without a `--` separator.
  The `--` separator has been recommended since the Kubernetes v1.18 release, which also deprecated the legacy way of invoking `kubectl exec`.
  
  This change aligns with the deprecation of legacy `kubectl exec` command execution and enforces the use of `kubectl exec [POD] -- [COMMAND]` for improved compatibility and adherence to recommended practices."

import jcifs.Configuration;
import jcifs.internal.smb2.ServerMessageBlock2Request;
import jcifs.internal.smb2.Smb2Constants;
import jcifs.internal.util.SMBUtil;

/**
 * SMB2 Change Notify request message.
 *
 * This command is used to monitor a directory for changes
 * and receive notifications when modifications occur.
 *
 * @author mbechler
 */
public class Smb2ChangeNotifyRequest extends ServerMessageBlock2Request<Smb2ChangeNotifyResponse> {

            "The TID specified was invalid.", "The handle is invalid.", "The network name cannot be found.",
            "Not enough storage is available to process this command.", "The media is write protected.", "The device is not ready.",
            "A device attached to the system is not functioning.", "A device attached to the system is not functioning.",

            "The TID specified was invalid.", "The handle is invalid.", "The network name cannot be found.",
            "Not enough storage is available to process this command.", "The media is write protected.", "The device is not ready.",
            "A device attached to the system is not functioning.", "A device attached to the system is not functioning.",

```python
from app.main import app
```

De cette façon, la commande `fastapi` saura où trouver votre app.

/// Note | Remarque

Vous pourriez aussi passer le chemin à la commande, comme :

```console
$ fastapi dev app/main.py
```

Mais vous devriez vous rappeler de passer le bon chemin à chaque fois que vous appelez la commande `fastapi`.

### kubectl rolling-update: < v1.4.0 client vs >=v1.4.0 cluster

Old version kubectl's rolling-update command is compatible with Kubernetes 1.4 and higher only if you specify a new replication controller name. You will need to update to kubectl 1.4 or higher to use the rolling update command against a 1.4 cluster if you want to keep the original name, or you'll have to do two rolling updates.

            (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
            (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00, // NextCommand