[Samuelodan]

So, one test started failing after updating the gems. This was the error message:

CapybaraAgent says: ERROR: {"runtime.gave_up" => {key: "runtime.gave_up", path: [], runtime_path: [], category: :runtime, symbol: :gave_up, message: "Gave up.", context: {reason: "While trying to choose the next command and inputs, I've ran into an error several times that I couldn't figure out how to get past. The last error looked like this:\n{\"data.unexpected_attributes\" => {key: \"data.unexpected_attributes\", path: [], runtime_path: [], category: :data, symbol: :unexpected_attributes, message: \"Unexpected attributes [:temperature]. Expected only [:api_token, :anthropic_version, :system, :max_tokens, :model, :messages]\", context: {unexpected_attributes: [:temperature], allowed_attributes: [:api_token, :anthropic_version, :system, :max_tokens, :model, :messages]}, is_fatal: true}}"}, is_fatal: false}}
response is a?: NilClassF../Users/samuelodan/repos/work/miles/forks/temp-gem-bump/agent-cli/src/foobara/cli_runner.rb:60: warning: literal string will be frozen in the future (run with --debug-frozen-string-literal for more information)
.

Failures:

  1) Foobara::Agent when there are some capybaras but one has a bad year of birth #run_cli can handle new goals with old context
     Failure/Error: expect(response).to be_a(String)
       expected nil to be a kind of String
     # ./spec/agent_spec.rb:144:in 'block (4 levels) in <top (required)>'

After some digging, I suspected it was related to the latest commit to foobara-anthropic-api, so I decided to temporarily pin it to the previous version, and the test stopped failing.

Could you please show me where we can make it so that temperature is no longer part of the request?
Thanks.

[azimux]

I patched this up yesterday I think so might not be anything worth doing here or if there is probably simpler to just do a fresh branch rather than resolving conflicts here. So will close but reopen if really wanting to reuse this branch.

[Samuelodan]

Okay. Cool. Thanks