You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Please describe the behavior you are expecting.
I want a full codebase without any placeholders or missing files.
Current Behavior
What is the current behavior?
I tried to generate codebase but some files are filles with placeholders withou a logic
Failure Information
Information about the failure, including environment details, such as LLM used.
I use Chat GPT
Steps to Reproduce
If possible, provide detailed steps for reproducing the issue.
I'm not sure
Failure Logs
Any relevant log snippets or files here.
The text was updated successfully, but these errors were encountered:
PierrunoYT
added
bug
Something isn't working
triage
Interesting but stale issue. Will be close if inactive for 3 more days after label added.
labels
Feb 13, 2024
This behaviour happens sometimes but it's not related to gpt-engineer so it's not gpt-engineer's bug. It's something that LLM creates. I'd suggested trying again or trying to say in your prompt that you want it to write full code and not to use placeholders.
I'm closing this since it's not an issue with gpt-engineer itself.
Policy and info
Expected Behavior
Please describe the behavior you are expecting.
I want a full codebase without any placeholders or missing files.
Current Behavior
What is the current behavior?
I tried to generate codebase but some files are filles with placeholders withou a logic
Failure Information
Information about the failure, including environment details, such as LLM used.
I use Chat GPT
Steps to Reproduce
If possible, provide detailed steps for reproducing the issue.
I'm not sure
Failure Logs
Any relevant log snippets or files here.
The text was updated successfully, but these errors were encountered: