phoenix-oss/llama-stack-mirror
0
0
Fork 1
mirror of https://github.com/meta-llama/llama-stack.git synced 2025-10-22 16:23:08 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

style: apply pre-commit fixes

Browse source 
🤖 Applied by @github-actions bot via pre-commit workflow
This commit is contained in:
github-actions[bot] 2025-10-19 02:11:52 +00:00
parent e4294af8ef
commit 5da1b4f81e
4 changed files with 88 additions and 80 deletions
Download patch file Download diff file Expand all files Collapse all files

76
docs/static/llama-stack-spec.yaml vendored
View file

@ -354,26 +354,27 @@ paths:
- type: object
title: NotGiven
description: >-
A sentinel singleton class used to distinguish omitted keyword arguments
from those passed in with the value None (which may have different
behavior).
For parameters with a meaningful None value, we need to distinguish
between the user explicitly passing None, and the user not passing
the parameter at all.
User code shouldn't need to use not_given directly.
For example:
```py
def get(timeout: Union[int, NotGiven, None] = NotGiven()) -> Response:
...
def create(timeout: Timeout | None | NotGiven = not_given): ...
get(timeout=1) # 1s timeout
create(timeout=1) # 1s timeout
get(timeout=None) # No timeout
create(timeout=None) # No timeout
get() # Default timeout behavior, which may not be statically known
at the method definition.
create() # Default timeout behavior
```
- name: include
@ -396,26 +397,27 @@ paths:
- type: object
title: NotGiven
description: >-
A sentinel singleton class used to distinguish omitted keyword arguments
from those passed in with the value None (which may have different
behavior).
For parameters with a meaningful None value, we need to distinguish
between the user explicitly passing None, and the user not passing
the parameter at all.
User code shouldn't need to use not_given directly.
For example:
```py
def get(timeout: Union[int, NotGiven, None] = NotGiven()) -> Response:
...
def create(timeout: Timeout | None | NotGiven = not_given): ...
get(timeout=1) # 1s timeout
create(timeout=1) # 1s timeout
get(timeout=None) # No timeout
create(timeout=None) # No timeout
get() # Default timeout behavior, which may not be statically known
at the method definition.
create() # Default timeout behavior
```
- name: limit
@ -429,26 +431,27 @@ paths:
- type: object
title: NotGiven
description: >-
A sentinel singleton class used to distinguish omitted keyword arguments
from those passed in with the value None (which may have different
behavior).
For parameters with a meaningful None value, we need to distinguish
between the user explicitly passing None, and the user not passing
the parameter at all.
User code shouldn't need to use not_given directly.
For example:
```py
def get(timeout: Union[int, NotGiven, None] = NotGiven()) -> Response:
...
def create(timeout: Timeout | None | NotGiven = not_given): ...
get(timeout=1) # 1s timeout
create(timeout=1) # 1s timeout
get(timeout=None) # No timeout
create(timeout=None) # No timeout
get() # Default timeout behavior, which may not be statically known
at the method definition.
create() # Default timeout behavior
```
- name: order
@ -465,26 +468,27 @@ paths:
- type: object
title: NotGiven
description: >-
A sentinel singleton class used to distinguish omitted keyword arguments
from those passed in with the value None (which may have different
behavior).
For parameters with a meaningful None value, we need to distinguish
between the user explicitly passing None, and the user not passing
the parameter at all.
User code shouldn't need to use not_given directly.
For example:
```py
def get(timeout: Union[int, NotGiven, None] = NotGiven()) -> Response:
...
def create(timeout: Timeout | None | NotGiven = not_given): ...
get(timeout=1) # 1s timeout
create(timeout=1) # 1s timeout
get(timeout=None) # No timeout
create(timeout=None) # No timeout
get() # Default timeout behavior, which may not be statically known
at the method definition.
create() # Default timeout behavior
```
deprecated: false