Girder's server-side handler writes data to the job log even if it's just an empty string, which ends up writing e.g. ["", "", "", ""] to the database, growing linearly with each progress update event. It's debatable whether that server side behavior is desirable, however it's easy enough to handle it here and only send the log value if something has been written to it.
Girder's server-side handler writes data to the job log even if it's just an empty string, which ends up writing e.g.
["", "", "", ""]
to the database, growing linearly with each progress update event. It's debatable whether that server side behavior is desirable, however it's easy enough to handle it here and only send the log value if something has been written to it.