-
Notifications
You must be signed in to change notification settings - Fork 44.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
updating duckduckgo version #6557
Conversation
This PR exceeds the recommended size of 500 lines. Please make sure you are NOT addressing multiple issues with one PR. |
✅ Deploy Preview for auto-gpt-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
random file
# autogpt-forge = { path = "../forge" } | ||
autogpt-forge = {git = "https://github.com/Significant-Gravitas/AutoGPT.git", subdirectory = "autogpts/forge"} | ||
#TODO: Add this to the documentation so people can use the local or remote version. E.g. setting to local was the only way to fix the duck duck go dependency issue. | ||
autogpt-forge = { path = "../forge" } | ||
#autogpt-forge = {git = "https://github.com/Significant-Gravitas/AutoGPT.git", subdirectory = "autogpts/forge"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will break the Docker build.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh because it needs a remote repo.. ok I wanted to make it a flag anyways.. I can add that maybe?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or maybe the Dockerfile file can account for it?
The proper way to do this would be:
This has to happen in 2 separate commits, because Unfortunately this is much more of a hassle with PRs than with direct commits. :') |
There was a bit of time pressure on this, so I adopted your fix in d820239. Thanks for figuring it out! :) |
During testing for the v0.5.0 release, we discovered web search was not working as expected. This was due to an old version of the sdk being used. This pull request just updates the version to 4 (currently the latest) and also changes the forge to local to use the changes. We should either add this to the docs or leave it default to local i think.