Opened 4 years ago

Closed 4 years ago

#32094 closed Bug (fixed)

flush() on self.stdout/stderr management commands doesn't work.

Reported by: Thomas Riccardi Owned by: Thomas Riccardi
Component: Core (Management commands) Version: 3.1
Severity: Normal Keywords: command flush migration
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no

Description

flush() is notably called during migrate command; it doesn't work, and a long migration effectively prints to stderr no relevant information up until the end:

Operations to perform:
  Apply all migrations: myapp
Running migrations:

Then nothing more, but the migration is being done.
Then at the end of the real migration, the rest is flushed:

  Applying myapp.0002_auto_20200817_1030... OK

Expected behavior:

Operations to perform:
  Apply all migrations: myapp
Running migrations:
  Applying myapp.0002_auto_20200817_1030...

then work
then OK

Change History (3)

comment:1 by Mariusz Felisiak, 4 years ago

Summary: flush() on self.stdout/stderr management commands doesn't work (notably called during migrate command) → flush() on self.stdout/stderr management commands doesn't work.
Triage Stage: Unreviewed → Accepted
Type: Uncategorized → Bug

Thanks. Regression in dc8834cad41aa407f402dc54788df3cd37ab3e22.

​PR

comment:2 by Mariusz Felisiak, 4 years ago

Triage Stage: Accepted → Ready for checkin

comment:3 by Mariusz Felisiak <felisiak.mariusz@…>, 4 years ago

Resolution: → fixed
Status: assigned → closed

In f1f24539:

Fixed #32094 -- Fixed flush() calls on management command self.stdout/err proxies.

Note: See TracTickets for help on using tickets.
Back to Top