wehub-resource-sync
a06f331eb8
CI / benchmark (push) Has been skipped
install-script / posix-syntax (push) Successful in 6m1s
CI / build-onnx (push) Failing after 6m43s
init-smoke / dry-run (push) Failing after 15m57s
security / govulncheck (push) Has been cancelled
security / trivy-fs (push) Has been cancelled
CI / test (1.26, ubuntu-latest) (push) Has been cancelled
Scorecard supply-chain security / Scorecard analysis (push) Has been cancelled
CI / test (1.26, macos-latest) (push) Has been cancelled
CI / build-windows (push) Has been cancelled
CI / lint (push) Has been cancelled
install-script / powershell-syntax (push) Has been cancelled
install-script / install (macos-14) (push) Has been cancelled
install-script / install (ubuntu-latest) (push) Has been cancelled
82 lines
2.3 KiB
Django/Jinja
82 lines
2.3 KiB
Django/Jinja
Please solve this issue: {{task}}
|
|
|
|
You can execute bash commands and edit files to implement the necessary changes.
|
|
|
|
## Recommended Workflow
|
|
|
|
This workflows should be done step-by-step so that you can iterate on your changes and any possible problems.
|
|
|
|
1. Analyze the codebase by finding and reading relevant files
|
|
2. Create a script to reproduce the issue
|
|
3. Edit the source code to resolve the issue
|
|
4. Verify your fix works by running your script again
|
|
5. Test edge cases to ensure your fix is robust
|
|
6. Submit your changes and finish your work by issuing the following command: `echo COMPLETE_TASK_AND_SUBMIT_FINAL_OUTPUT`.
|
|
Do not combine it with any other command. After this command, you cannot continue working on this task.
|
|
|
|
## Important Rules
|
|
|
|
1. Every response must contain exactly one action
|
|
2. The action must be enclosed in triple backticks
|
|
3. Directory or environment variable changes are not persistent. Every action is executed in a new subshell.
|
|
However, you can prefix any action with `MY_ENV_VAR=MY_VALUE cd /path/to/working/dir && ...` or write/load environment variables from files
|
|
4. Make minimal, targeted changes. Don't refactor unrelated code.
|
|
|
|
<system_info>
|
|
{{system}} {{release}} {{version}} {{machine}}
|
|
</system_info>
|
|
|
|
## Formatting your response
|
|
|
|
Here is an example of a correct response:
|
|
|
|
<example_response>
|
|
THOUGHT: I need to understand the structure of the repository first. Let me check what files are in the current directory to get a better understanding of the codebase.
|
|
|
|
```mswea_bash_command
|
|
ls -la
|
|
```
|
|
</example_response>
|
|
|
|
## Useful command examples
|
|
|
|
### Create a new file:
|
|
|
|
```bash
|
|
cat <<'EOF' > newfile.py
|
|
import numpy as np
|
|
hello = "world"
|
|
print(hello)
|
|
EOF
|
|
```
|
|
|
|
### Edit files with sed:
|
|
|
|
{%- if system == "Darwin" -%}
|
|
<note>
|
|
You are on MacOS. For all the below examples, you need to use `sed -i ''` instead of `sed -i`.
|
|
</note>
|
|
{%- endif -%}
|
|
|
|
```bash
|
|
# Replace all occurrences
|
|
sed -i 's/old_string/new_string/g' filename.py
|
|
# Replace only first occurrence
|
|
sed -i 's/old_string/new_string/' filename.py
|
|
# Replace all occurrences in lines 1-10
|
|
sed -i '1,10s/old_string/new_string/g' filename.py
|
|
```
|
|
|
|
### View file content:
|
|
|
|
```bash
|
|
# View specific lines with numbers
|
|
nl -ba filename.py | sed -n '10,20p'
|
|
```
|
|
|
|
### Any other command you want to run
|
|
|
|
```bash
|
|
anything
|
|
```
|