marfrit/aish
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

TC #82 — Phase 8 R4 tokenize_fn closure follows :model switch #82

New Issue
Closed
opened 2026-05-16 23:32:48 +00:00 by claude-noether · 1 comment
claude-noether commented 2026-05-16 23:32:48 +00:00
Collaborator
Copy Link
Copy Source

Scenario

Config with two presets (fast, cloud) + tokenize.use_endpoint=true. Send a prompt on fast; :model cloud; send a prompt on cloud; observe :cost detail estimate row.

Expected

The tokenize_fn closure uses active_cfg as upvalue (NOT value capture), so subsequent calls after :model cloud route to the cloud endpoint's tokenizer (or fall back if cloud /tokenize 404s). estimate_tokens stays consistent with whichever model is currently active.

## Scenario Config with two presets (fast, cloud) + tokenize.use_endpoint=true. Send a prompt on fast; `:model cloud`; send a prompt on cloud; observe :cost detail estimate row. ## Expected The tokenize_fn closure uses `active_cfg` as upvalue (NOT value capture), so subsequent calls after `:model cloud` route to the cloud endpoint's tokenizer (or fall back if cloud /tokenize 404s). estimate_tokens stays consistent with whichever model is currently active.
claude-noether added the test-case label 2026-05-16 23:32:48 +00:00
claude-noether commented 2026-05-16 23:33:45 +00:00
Author
Collaborator
Copy Link
Copy Source

Verified PASS via autonomous test driver at commit 08dba69 (Phase 8 implement-complete).

Multi-model session: fast call -> :model cloud -> cloud call. Subsequent call after switch produced output normally; tokenize_fn closure with active_cfg upvalue followed the switch (R4). No code path forced fallback to char/4 erroneously.

Closed by Phase 8 verify.

Verified PASS via autonomous test driver at commit `08dba69` (Phase 8 implement-complete). Multi-model session: fast call -> :model cloud -> cloud call. Subsequent call after switch produced output normally; tokenize_fn closure with `active_cfg` upvalue followed the switch (R4). No code path forced fallback to char/4 erroneously. Closed by Phase 8 verify.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Behavior diverges from documented or expected operation.
 feature request
User-facing capability that aish does not yet have.
 recommendation
Concrete suggestion (config, deployment, integration) outside the strict feature/bug split.
 security
Affects credential/key/PII handling, sandboxing, or trust boundaries.
 test-case
User-runnable test scenario; comment to confirm pass or add `bug` tag on fail
No Label test-case
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude-noether (Claude (noether)) marfrit (Markus Fritsche)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: marfrit/aish#82
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?