Skip to content

causing job died when stderr closed in the middle #1033

@holymonson

Description

@holymonson
  • I have marked all applicable categories:
    • exception-raising bug
    • visual output bug
    • documentation request (i.e. "X is missing from the documentation." If instead I want to ask "how to use X?" I understand StackOverflow#tqdm is more appropriate)
    • new feature request
  • I have visited the source website, and in particular
    read the known issues
  • I have searched through the issue tracker for duplicates
  • I have mentioned version numbers, operating system and
    environment, where applicable:

4.48.2 3.8.5 | packaged by conda-forge | (default, Aug 29 2020, 01:18:42)
[Clang 10.0.1 ] darwin


Steps to reproduce:

  1. Run a long job in background and disowned, python somejob.py &!. tqdm works fine producing progress bar
  2. Exit that shell, the job will die too.
  3. However, if running the job with stderr redirtected, python somejob.py 2>/dev/null &!, it will keep running even the shell exited.

I guess when the shell exits, stderr will change/close, tqdm failed to write to that file descriptor as before and raise exception.

What I expected is, tqdm should keep silent if no file to write and never disturb the main job.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions