Self-correction pass caught this before publishing: the previous commit's test
comment and companion post draft claimed a keepAlive set through
ChatClient.prompt().options(...) never reaches the request Ollama receives,
and worked around it by calling ChatModel.call(Prompt) directly instead. That
claim was never actually verified against /api/ps for the ChatClient path --
only inferred from a failed timing assertion that, it turned out, would have
failed the same way even with a genuinely confirmed unload (see below).
Checked directly: unloading via ChatClient.prompt().options(OllamaChatOptions
.builder()...keepAlive("0")).call() and immediately querying /api/ps shows an
empty model registry, same as the ChatModel path. The options merge works
correctly. Simplified the test back to ChatClient throughout, consistent with
the rest of this series, and removed the incorrect comment.
Co-Authored-By: Claude Sonnet 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01FtpJvZfg4nvLvtzgJTDWpB
8 lines
396 B
Plaintext
8 lines
396 B
Plaintext
prompt: "Reply with a single short sentence: what is Testcontainers for?"
|
|
response: Testcontainers is a containerization platform that simplifies the process of building and deploying applications quickly and efficiently.
|
|
|
|
total-duration: 662ms
|
|
load-duration: 2ms
|
|
prompt-eval-count: 42, prompt-eval-duration: 47ms
|
|
eval-count: 16, eval-duration: 607ms
|
|
26.33 tokens/sec (eval-count / eval-duration) |