feat(blocks) Add finetune block

[aarushik93]

Background

Changes 🏗️

PR Quality Scorecard ✨

• [x] Have you used the PR description template?   +2 pts
• [ ] Is your pull request atomic, focusing on a single change?   +5 pts
• [ ] Have you linked the GitHub issue(s) that this PR addresses?   +5 pts
• [ ] Have you documented your changes clearly and comprehensively?   +5 pts
• [ ] Have you changed or added a feature?   -4 pts
  • [ ] Have you added/updated corresponding documentation?   +4 pts
  • [ ] Have you added/updated corresponding integration tests?   +5 pts
• [ ] Have you changed the behavior of AutoGPT?   -5 pts
  • [ ] Have you also run agbenchmark to verify that these changes do not regress performance?   +10 pts

[netlify[bot]]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	e651781e01c89c3dd1820bc4ce0d10539b5108e9
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/66b060ebc3d9980008a92bf7

[qodo-merge-pro[bot]]

CI Failure Feedback 🧐

(Checks updated until commit https://github.com/Significant-Gravitas/AutoGPT/commit/e651781e01c89c3dd1820bc4ce0d10539b5108e9)

Action: test (3.10, windows, postgres)

Failed stage: Run Linter [❌]

Failure summary: The action failed because the linter detected issues with the import statements in the file autogpt_server/blocks/finetune.py: The import json is unused. Imports are incorrectly sorted and/or formatted. The command poetry run isort --diff --check --profile black . returned a non-zero exit status 1, indicating that the imports need to be fixed.

Relevant error logs: 1: ##[group]Operating System 2: Microsoft Windows Server 2022 ... 963: | 964: 1 | from typing import Any, List 965: 2 | import json 966: | ^^^^ F401 967: 3 | import tempfile 968: 4 | import openai 969: | 970: = help: Remove unused import: `json` 971: Found 3 errors. 972: [*] 3 fixable with the `--fix` option. 973: ERROR: D:\a\AutoGPT\AutoGPT\rnd\autogpt_server\autogpt_server\blocks\finetune.py Imports are incorrectly sorted and/or formatted. ... 987: File "<string>", line 1, in <module> 988: File "D:\a\AutoGPT\AutoGPT\rnd\autogpt_server\linter.py", line 21, in lint 989: raise e 990: File "D:\a\AutoGPT\AutoGPT\rnd\autogpt_server\linter.py", line 16, in lint 991: run("isort", "--diff", "--check", "--profile", "black", ".") 992: File "D:\a\AutoGPT\AutoGPT\rnd\autogpt_server\linter.py", line 10, in run 993: subprocess.run(["poetry", "run"] + list(command), cwd=directory, check=True) 994: File "C:\hostedtoolcache\windows\Python\3.10.11\x64\lib\subprocess.py", line 526, in run 995: raise CalledProcessError(retcode, process.args, 996: subprocess.CalledProcessError: Command '['poetry', 'run', 'isort', '--diff', '--check', '--profile', 'black', '.']' returned non-zero exit status 1. 997: >>>>> Running poetry run ruff check . --exit-zero 998: >>>>> Running poetry run isort --diff --check --profile black . 999: Lint failed, try running `poetry run format` to fix the issues: Command '['poetry', 'run', 'isort', '--diff', '--check', '--profile', 'black', '.']' returned non-zero exit status 1. 1000: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check. The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

[github-actions[bot]]

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

[github-actions[bot]]

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

[github-actions[bot]]

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