mirror of
https://github.com/pewdiepie-archdaemon/odysseus.git
synced 2026-09-11 02:32:20 +02:00
RaresKeYandStressTestor
7026cf40b5
* docs(specs): restore bootstrap after dev rewrite
* docs(specs): remove runtime inventory snapshot
* docs(specs): reconcile current dev truth
* docs(specs): document scheduled task actions as an owner-attribution source
Owner Attribution covered cookie, bearer-token and internal-loopback
requests. Scheduled task actions are a fourth source and behave
differently: _execute_action passes owner=task.owner off the stored
ScheduledTask row, so no request and no resolved principal are in
flight, and route-level require_user() never runs.
Webhook triggers are the sharp case. They are unauthenticated by
design with the token as the only credential and execute under the
stored task.owner.
Paths cite routes/task/task_routes.py, the canonical location after
the task subpackage move (#6081); routes/task_routes.py on current dev
is the backward-compat shim.
* docs(specs): add chained tasks to the trigger list, refresh dev stamp
Review feedback from RaresKeY on the previous commit.
"Every trigger path" was too broad: success-chained tasks are another
path into _execute_action. Added them with their own citation, and
noted that chaining additionally requires the target task to share
task.owner and rejects cycles, which is stricter than the trigger-side
checks. Softened the lead-in to "these trigger paths".
Line 56 still pointed at routes/task_routes.py for webhook credential
validation. That path is the backward-compat shim on current dev after
the task subpackage move (#6081); repointed to the canonical
routes/task/task_routes.py.
Stamp moved to dev@2a6b09b. Inspection backing that bump was scoped:
every file path cited in this spec was mechanically checked to resolve
on 2a6b09b, and every file:line in the Owner Attribution additions was
read against it. Behavioral claims elsewhere in the file were not
re-audited.
* docs(specs): correct SECURE_COOKIES description to match current behavior
Third of the stale details RaresKeY enumerated. The cookie section
described SECURE_COOKIES as purely opt-in, which stopped being true.
_secure_cookie() (routes/auth_routes.py:89) treats an explicit true or
false as authoritative and derives the Secure attribute from the
request otherwise, including when the variable is unset and when
docker-compose injects it present-but-empty. Either the connection
scheme or the first X-Forwarded-Proto hop being https is enough.
* docs(specs): refresh current dev truth
---------
Co-authored-by: StressTestor <212606152+StressTestor@users.noreply.github.com>
48 lines
1.8 KiB
Markdown
48 lines
1.8 KiB
Markdown
# llama.cpp Provider Shape
|
|
|
|
Last updated: dev@e57f60b | 2026-07-20
|
|
|
|
## Scope
|
|
|
|
Canonical provider ID `llamacpp`; OpenAI Chat/Responses and Anthropic Messages
|
|
compatibility plus native server metadata; reader
|
|
`src/model_capability_readers/llamacpp.py`.
|
|
|
|
## Metadata Shapes
|
|
|
|
`/v1/models` provides served identity and can include server model entries;
|
|
native `/props` is authoritative for the running model/server combination:
|
|
|
|
- `model_alias`/`model_path`;
|
|
- `default_generation_settings.n_ctx` and sampling `params`;
|
|
- `total_slots` and optional `/slots[].n_ctx` fallback;
|
|
- `chat_template_caps` for tools/system role;
|
|
- `modalities.vision|audio`;
|
|
- current server/build state.
|
|
|
|
Capability depends on weights, projection/model assets, chat template, parser,
|
|
and launch flags. It is endpoint evidence, not a checkpoint-name claim.
|
|
`/props` and `/v1/models` can be merged only for the same served identity.
|
|
|
|
## Request And Response Shape
|
|
|
|
llama-server supports several OpenAI-compatible tasks and native extensions.
|
|
Do not infer embeddings/rerank/chat solely from the OpenAI model card; use an
|
|
explicit server model capability field or endpoint configuration. Tool and
|
|
reasoning correctness can depend on selected chat template and parser.
|
|
|
|
## Fallback And Safety
|
|
|
|
The registry selects llama.cpp through an explicit vendor or endpoint kind; it
|
|
does not auto-detect `/props` from payload shape. Port 8000 currently maps to
|
|
the vLLM placeholder, while 8080 falls through to generic OpenAI-compatible.
|
|
llama.cpp-only `session_id` and `cache_prompt` affinity fields must remain local
|
|
endpoint behavior and never leak to strict cloud providers (#4640 and current
|
|
affinity tests).
|
|
|
|
## Current Gaps
|
|
|
|
- Multi-model routing requires per-served-model `/props` association.
|
|
- Parser/template configuration is not yet fully represented in canonical
|
|
endpoint metadata.
|