Require independent renderer and solver clients
This commit is contained in:
@@ -31,9 +31,11 @@ python3 -m logicbench generate --count 3 --length short --seed 20260922
|
||||
Run the checked-in live task:
|
||||
|
||||
```bash
|
||||
export LLM_API_KEY='...'
|
||||
export LLM_BASE_URL='your-provider-compatible-base-url'
|
||||
export RENDERER_API_KEY='...'
|
||||
export RENDERER_BASE_URL='your-renderer-compatible-base-url'
|
||||
export RENDERER_MODEL='your-renderer-model'
|
||||
export SOLVER_API_KEY='...'
|
||||
export SOLVER_BASE_URL='your-solver-compatible-base-url'
|
||||
export SOLVER_MODEL='your-solver-model'
|
||||
python3 -m logicbench run tasks/short-smoke.json
|
||||
```
|
||||
@@ -42,10 +44,8 @@ Role-specific values override the shared fallback:
|
||||
|
||||
| Variable | Meaning |
|
||||
| --- | --- |
|
||||
| `LLM_API_KEY` | Optional shared key when both roles use the same account/provider |
|
||||
| `RENDERER_API_KEY`, `SOLVER_API_KEY` | Optional role-specific keys; each takes precedence over `LLM_API_KEY` |
|
||||
| `LLM_BASE_URL` | Optional shared OpenAI-compatible endpoint |
|
||||
| `RENDERER_BASE_URL`, `SOLVER_BASE_URL` | Optional role-specific endpoints; each takes precedence over `LLM_BASE_URL` |
|
||||
| `RENDERER_API_KEY`, `SOLVER_API_KEY` | Required independent credentials; values may currently be identical |
|
||||
| `RENDERER_BASE_URL`, `SOLVER_BASE_URL` | Required independent OpenAI-compatible endpoints; values may currently be identical |
|
||||
| `RENDERER_API_STYLE`, `SOLVER_API_STYLE` | `responses` (default) or `chat_completions` |
|
||||
| `RENDERER_MODEL`, `SOLVER_MODEL` | Required, independently selected model IDs |
|
||||
|
||||
@@ -63,14 +63,13 @@ The run log prints the rendered questions and scores. The same records, original
|
||||
|
||||
Create these repository Actions settings:
|
||||
|
||||
1. Secret `LLM_API_KEY` when both roles share credentials, or role-specific secrets `RENDERER_API_KEY` and `SOLVER_API_KEY` when they do not.
|
||||
2. Variables `RENDERER_MODEL` and `SOLVER_MODEL`.
|
||||
3. Variable `LLM_BASE_URL` for a shared provider endpoint, or role-specific variables `RENDERER_BASE_URL` and `SOLVER_BASE_URL` for different providers.
|
||||
4. Optional variables `RENDERER_API_STYLE` and `SOLVER_API_STYLE`, each set to `responses` or `chat_completions` according to that provider/model.
|
||||
1. Secrets `RENDERER_API_KEY` and `SOLVER_API_KEY`.
|
||||
2. Variables `RENDERER_BASE_URL`, `RENDERER_MODEL`, and `RENDERER_API_STYLE`.
|
||||
3. Variables `SOLVER_BASE_URL`, `SOLVER_MODEL`, and `SOLVER_API_STYLE`.
|
||||
|
||||
The workflow targets the existing `minecraft-and-affine-server` runner label. Verify that a runner advertising this label is online, then manually dispatch **Short abstraction evaluation** from the repository's Actions page.
|
||||
|
||||
For a current all-Qwen run, create only the shared `LLM_API_KEY` secret with the Model Studio key. Set `LLM_BASE_URL` to the API Host shown for that key and region, set the two model variables independently, and use `chat_completions` for both API-style variables. For example, a fast renderer and stronger solver can use `qwen3.8-flash` and `qwen3.8-max`; both currently support JSON Schema structured output. Do not hard-code the DashScope key or endpoint in the workflow.
|
||||
For a current all-Qwen run, put the Model Studio key into both role-specific secrets and its API Host into both role-specific base-URL variables. The values may be identical today, but the two client boundaries remain explicit. Use `chat_completions` for both API-style variables. For example, a fast renderer and stronger solver can use `qwen3.8-flash` and `qwen3.8-max`; both currently support JSON Schema structured output. Do not hard-code keys or endpoints in the workflow.
|
||||
|
||||
## Tests
|
||||
|
||||
|
||||
Reference in New Issue
Block a user