Current state of Stable branch; Docker images. #4973
GECORegulatory
started this conversation in
General
Replies: 1 comment 1 reply
-
Hello, I don't understand a little bit
Is workaround to build autogpt from source? Should I use stable or master branch? I tried both and still got this error.
This command doesn't work for me. I used docker-compose run --build --rm auto-gpt |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Current State of AutoGPT Stable Branch and Docker Images
Introduction
As some of you may be aware, AutoGPT is currently undergoing a major architectural overhaul. Unfortunately, this means that bug reports are starting to pile up, and the state of our stable branch and Docker images is not as robust as we would like. I'm making a personal commitment to help remedy this situation, but I could definitely use some assistance from the community.
Current task
Figure out which bugs exist in the stable branch
Find the new highest-severity bug
Track the presence of bugs until the bug count lowers, and until there is little discrepancy between the official docker image and one built from source
Workaround
There is a large discrepancy between bugs in the
stable
branch, and in the docker images. Because of this, I recommend building your own images from source. I've provided a script for this. Please note that you must first clone the repository,cd
and edit your .env with your API key. You cannot build the image without setting it.Script (bash/zsh)
Bugs Overview
Here's a brief rundown of the most pressing issues. By not reproducible, I mean that I wasn't able to reproduce it or find a procedure to reproduce it.:
High Severity Bugs
max_tokens
) sent to the OpenAI API. It's not reproducible and needs more info. This is potentially the current highest severity bug report.read_file
command (an issue I personally reported). It's also reproducible. Workaround currently solves this.Medium Severity Bugs
highest severity bug we have right now.Testingasrequested #4986 is working to fix this. See workaroundappears reproducible.is reproducible, usually without any special procedure.NoneType
error that needs a PR to fix. The issue is already traced, this is a great start to anyone to jump in on. Reproducability is unclearLow Severity Bugs
config.py
manually, but the solution lacks detail.Fixed
run.sh
is run without having an OpenAI API key set up.Moving Forward
I'd like to propose the following steps to improve our situation:
As a starting point, I will begin working on the most severe issue (#4871). Any help would be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions