Title: Fix TypeError in harness.py by updating Coder.create method calls #9
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.
Pull Request Description:
Description
This pull request addresses the
TypeError
encountered while runningharness.py
on swebench-lite. The error was caused by passing an unexpected keyword argumentgit_dname
toCoder.create()
which is not present in the latest code onaider-chat
.To resolve this, the pull request modifies the code to remove the
git_dname
parameter from the call toCoder.create()
inharness.py
. However, after making this change, another errorTypeError: Coder.__init__() got an unexpected keyword argument 'max_chat_history_tokens'
occurred. This error is due to passing themax_chat_history_tokens
parameter to theCoder
constructor, which is also not valid.This PR aims to fix these issues by updating the parameter passing in the
Coder.create()
andCoder
constructor methods to align with the latest code onaider-chat
.Changes Made
git_dname
parameter from the call toCoder.create()
inharness.py
.Coder
constructor to resolve theTypeError: Coder.__init__() got an unexpected keyword argument 'max_chat_history_tokens'
error.Related Issue
Fixes #ISSUE_NUMBER (Replace ISSUE_NUMBER with the actual issue number being addressed)
Please review the changes and provide feedback.