Edit start script for checking environment once.

[liaosunny123]

Background

#2901 , reducing the start time.

Changes

Modifying the run.bat and run.sh. I add the command to generate a file named env_check.lock to skip the env check after first starting.

Documentation

As what the changes said.

Test Plan

I tested in window and ubuntu 22.04, it works.

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

[hdkiller]

The script is intended to run the check requirements every time in case the repository was pulled by the user and there are new requirements added, so a one time lock file is not enough.

A better solution would be to check if the requirements file has been not changed since a successful pip install.

[liaosunny123]

The script is intended to run the check requirements every time in case the repository was pulled by the user and there are new requirements added, so a one time lock file is not enough.

A better solution would be to check if the requirements file has been not changed since a successful pip install.

You are right and I ignore this situation. I check check_requirements.py and I think it is unnecessary to get the missing package exactly. Do you think check the hash of the requirment file to decide whether install requirement is a good idea?

[github-actions[bot]]

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

[p-i-]

This is a mass message from the AutoGPT core team. Our apologies for the ongoing delay in processing PRs. This is because we are re-architecting the AutoGPT core!

For more details (and for infor on joining our Discord), please refer to: https://github.com/Significant-Gravitas/Auto-GPT/wiki/Architecting

[ntindle]

A hash would work well in this case I believe as we typically pin versions of something breaks relating to a package

[vercel[bot]]

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		May 20, 2023 2:06am

[github-actions[bot]]

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

[codecov[bot]]

Codecov Report

Patch and project coverage have no change.

Comparison is base (7e21f38) 63.26% compared to head (a29c5b9) 63.26%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2924   +/-   ##
=======================================
  Coverage   63.26%   63.26%           
=======================================
  Files          74       74           
  Lines        3427     3427           
  Branches      504      504           
=======================================
  Hits         2168     2168           
  Misses       1103     1103           
  Partials      156      156           

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

[liaosunny123]

this pr will check requirement.py hash to decide if need to procee

[github-actions[bot]]

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