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

Terminal Tool doesn’t include stdout content on error #4503

Open
3 tasks done
Tracked by #3634
chezsmithy opened this issue Mar 6, 2025 · 0 comments · May be fixed by #4482
Open
3 tasks done
Tracked by #3634

Terminal Tool doesn’t include stdout content on error #4503

chezsmithy opened this issue Mar 6, 2025 · 0 comments · May be fixed by #4482
Assignees
Labels
kind:bug Indicates an unexpected problem or unintended behavior "needs-triage"

Comments

@chezsmithy
Copy link
Contributor

Before submitting your bug report

Relevant environment info

- OS: MacOS
- Continue version: 1.1.1
- IDE version: latest
- Model:
- config:
  

  
  OR link to assistant in Continue hub:

Description

When a terminal command ends in error some of them have stdout without stderr. An example of this is cucumber-js. When tests fail the processes exits with an error status but the test results are written to stdout. As such, tools don’t provide feedback to the LLM so automated fixes can be suggested.

To reproduce

Run cucumber-js tests that end in error.
Note in the terminal context there is no output.
The tools loop attempts to rerun over and over but will never get any results.

Log output

@dosubot dosubot bot added the kind:bug Indicates an unexpected problem or unintended behavior label Mar 6, 2025
@RomneyDa RomneyDa mentioned this issue Mar 11, 2025
24 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:bug Indicates an unexpected problem or unintended behavior "needs-triage"
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants