Skip to content
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

The unlooping and fixing of file execution. #3368

Merged
merged 14 commits into from
Apr 27, 2023

Conversation

BillSchumacher
Copy link
Contributor

@Pwuts deserves most of the credit for fixing file operations here.

Background

Changes

Documentation

Test Plan

PR Quality Checklist

  • My pull request is atomic and focuses on a single change.
  • I have thoroughly tested my changes with multiple different prompts.
  • I have considered potential risks and mitigations for my changes.
  • I have documented my changes clearly and comprehensively.
  • I have not snuck in any "extra" small tweaks changes

@vercel
Copy link

vercel bot commented Apr 27, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
docs ⬜️ Ignored (Inspect) Visit Preview Apr 27, 2023 4:03am

@github-actions github-actions bot added the conflicts Automatically applied to PRs with merge conflicts label Apr 27, 2023
@github-actions
Copy link
Contributor

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

@github-actions github-actions bot removed the conflicts Automatically applied to PRs with merge conflicts label Apr 27, 2023
@github-actions
Copy link
Contributor

Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly.

@codecov
Copy link

codecov bot commented Apr 27, 2023

Codecov Report

Patch coverage: 71.79% and project coverage change: +0.15 🎉

Comparison is base (65b6c27) 51.22% compared to head (409e111) 51.37%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3368      +/-   ##
==========================================
+ Coverage   51.22%   51.37%   +0.15%     
==========================================
  Files          65       65              
  Lines        2975     3013      +38     
  Branches      502      508       +6     
==========================================
+ Hits         1524     1548      +24     
- Misses       1331     1338       +7     
- Partials      120      127       +7     
Impacted Files Coverage Δ
autogpt/commands/execute_code.py 0.00% <0.00%> (ø)
autogpt/json_utils/json_fix_llm.py 49.51% <61.11%> (-1.08%) ⬇️
autogpt/chat.py 65.51% <77.77%> (+0.96%) ⬆️
autogpt/__init__.py 88.88% <83.33%> (-11.12%) ⬇️
autogpt/prompts/prompt.py 56.60% <100.00%> (+0.83%) ⬆️
autogpt/workspace/workspace.py 100.00% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@vercel vercel bot temporarily deployed to Preview April 27, 2023 01:57 Inactive
waynehamadi
waynehamadi previously approved these changes Apr 27, 2023
@github-actions github-actions bot added size/l and removed size/m labels Apr 27, 2023
@waynehamadi waynehamadi merged commit d8c16de into Significant-Gravitas:master Apr 27, 2023
@Pwuts Pwuts added this to the v0.3.0 release milestone Apr 27, 2023
@Boostrix
Copy link
Contributor

Boostrix commented May 2, 2023

The unlooping and fixing of file execution

is this actually working as well as it sounds ?
The background being, we've been talking about a different method to detect unnecessary looping by hashing current actions and commands and incrementing a corresponding counter: #3668, but if that's now redundant, that would obviously be great!

BillSchumacher added a commit to BillSchumacher/Auto-GPT that referenced this pull request May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants