Skip to content

No stack trace resulting in ContainerError when tty is enabled #2260

@damienrj

Description

@damienrj

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions