Fix 'cp: cannot stat 'src/stable/*': No such file or directory' error

[sweep-ai[bot]]

PR Feedback (click)

• [ ] 👍 Sweep Did Well
• [ ] 👎 Sweep Needs Improvement

  Description

  This PR fixes the 'cp: cannot stat 'src/stable/': No such file or directory' error that occurs when running the build_docker.sh script. The error is caused by the script trying to copy files from the `src/stable/` directory, which does not exist. This PR adds a check to ensure that the directory exists before attempting to copy files from it. If the directory does not exist, the script will print an error message and exit.

Summary of Changes

• Modified the prepare_vscode.sh script to check if the src/stable directory exists before copying files from it.
• Added an if statement to check if the directory exists and print an error message if it does not.
• This change prevents the 'cp: cannot stat 'src/stable/*': No such file or directory' error from occurring.

Fixes #10.

---

🎉 Latest improvements to Sweep:

• Sweep now uses the rope library to refactor Python! Check out Large Language Models are Bad at Refactoring Code. To have Sweep refactor your code, try sweep: Refactor <your_file>.py to be more modular!
• Sweep finds and fixes bugs in your code by writing unit tests! Check out Having GPT-4 Iterate on Unit Tests like a Human.

---

💡 To get Sweep to edit this pull request, you can:

• Comment below, and Sweep can edit the entire PR
• Comment on a file, Sweep will only modify the commented file
• Edit the original issue to get Sweep to recreate the PR from scratch

[sweep-ai[bot]]

Sandbox Executions

• [X] Check prepare_vscode.sh ✓

  Sandbox logs for https://github.com/reconsumeralization/CodeCurse/commit/a9bc7c18e617aeb4d6c3fc7a5a0dff4188b07ae7

trunk fmt prepare_vscode.sh || exit 0 1/2 ✓

 ✔ Formatted prepare_vscode.sh
Re-checking autofixed files...

Checked 1 file
✔ No issues

trunk check --fix --print-failures prepare_vscode.sh 2/2 ✓

  ISSUES  
prepare_vscode.sh:85:65
  85:65  low  Consider invoking this command separately to avoid masking its return value (or use '||  shellcheck/SC2312
              true' to ignore).                                                                                         
 199:60  low  Consider invoking this command separately to avoid masking its return value (or use '||  shellcheck/SC2312
              true' to ignore).                                                                                         
 200:60  low  Consider invoking this command separately to avoid masking its return value (or use '||  shellcheck/SC2312
              true' to ignore).                                                                                         
 205:56  low  Consider invoking this command separately to avoid masking its return value (or use '||  shellcheck/SC2312
              true' to ignore).                                                                                         
Checked 1 file
4 existing issues

[sweep-ai[bot]]

Apply Sweep Rules to your PR?

• [ ] Apply: All docstrings and comments should be up to date.
• [ ] Apply: Code should be properly formatted and indented.
• [ ] Apply: Variable and function names should be descriptive and follow a consistent naming convention.
• [ ] Apply: There should be no trailing whitespace at the end of lines.
• [ ] Apply: Comments should be used to explain complex sections of code or to provide additional context.
• [ ] Apply: There should be no unused or commented out code in the repository.

[height[bot]]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.