No stack trace resulting in ContainerError when tty is enabled
Open
Nobody has claimed this yet.
kind/bug
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
I am having an issue where I don't get the error responsible for the ContainerError unless I turn off tty. Is the expected behavior?
With tty enabled:
ContainerError: Command '['train']' in image 'conductor:latest' returned non-zero exit status 1:
With tty disabled:
ContainerError: Command '['train']' in image 'conductor:latest' returned non-zero exit status 1: Traceback (most recent call last):
...
long stack trace
...
raise ValueError('Config not specified')
ValueError: Config not specified
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported command with tty enabled and disabled, then compare how ContainerError captures and displays the command's output. Done means the behavior is understood and, if confirmed as a bug, the tty-enabled case preserves the relevant traceback; the issue does not name a file or test to start from.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100