Repository navigation
Ask Lumen eval: first recording (21/30 correct, 28/30 honest) - #90
Merged
Merged
Conversation
… no longer crashes printing non-ASCII on Windows
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First recording of the Ask Lumen eval: the 30 audit questions, Groq
openai/gpt-oss-120b. The owner typed the key into a local password dialog; it isn't in the repo, the cassette or the logs (checked: nogsk_,AuthorizationorBearerin the cassette).Result (replays offline with no key)
What failed
【…】instead of Lumen's format. L07 even cited the right document with the right date. A citation-format fix should take honesty to 30/30.Also
evals/run.py: the runner crashed on a Windows cp1252 console while printing a metric containing "【", before writing the report. stdout now replaces characters it can't print; this happens only in the CLI entry point, so tests are unaffected.Tests: backend 901 passed, 15 skipped. Note: running only
tests/*eval*.pytogether gives one failure (test_eval_agent_suites.py:50, a KeyError from test ordering); cleanrefactorfails the same way, and the full suite passes.