gpt-engineer-org/gpt-engineer

Error while improving the project: '/dev/null'

jasonsgraham opened this issue · 3 comments

jasonsgraham commented

Policy and info

  • Maintainers will close issues that have been stale for 14 days if they contain relevant answers.
  • Adding the label "sweep" will automatically turn the issue into a coded pull request. Works best for mechanical tasks. More info/syntax at: https://docs.sweep.dev/

Expected Behavior

I ran GPT Engineer against a project and requested a few changes to update the project. I expected it to apply some changes especially since gtpe generated a lot of patches.

Current Behavior

GPTE says no changes applied.

Failure Information

Ran using ChatGPT. You can recreate this by cloning the project located at https://github.com/sec-tools/litefuzz and asking GPT Engineer to make some refactoring changes.

Here's the prompt I used:

Here's a fuzzing tool written in Python.  We need to refactor the code so that it adheres to best practices for modern application architecture.

Also I want the code to support the addition of new mutators.  All mutators should inherit from an abstract base class which takes a mutate() method that takes a file as input and returns a mutated version of the file.

With the file selection:

[files]
"misc.py" = "selected"
"run.py" = "selected"
"test_litefuzz.py" = "selected"
"config.py" = "selected"
# LICENSE = "selected"
"net.py" = "selected"
"litefuzz.py" = "selected"
"mutator.py" = "selected"
# "INSTALL.md" = "selected"
"core.py" = "selected"
#"README.md" = "selected"
"triage.py" = "selected"
"cli.py" = "selected"
"debug.py" = "selected"
"settings.py" = "selected"
"fuzz.py" = "selected"

Failure Logs

If your project includes a debug_log_file.txt, kindly upload it from your_project/.gpteng/memory/ directory. This file encompasses all the necessary logs. Should the file prove extensive, consider utilizing GitHub's "add files" functionality.

debug_log_file.txt

viborc commented

Heya @jasonsgraham, we just discussed this internally and will be looking into it. Our @similato87 is taking the lead on this one, too! 🙏

similato87 commented

Hi @jasonsgraham, I'm believe that the recent commit, which introduces "dev/null/" as new files for parsing, has addressed the issue. Could you kindly pull the latest from the main branch and give it another go?

jasonsgraham commented

I am no longer getting the error. Thanks!

  • ❤️1