You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In automating aartfaac-server, we would like to store the stdout/stderr in log files for analysis of breakdowns. Currently, aartfaac-server generates messages like
'[WARNING] [aartfaac-server-41027] QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState', probably when a pipeline severs its connection. However, the message is written out within a busy loop, resulting in very large log files. Such connections should time out and retry after a reasonable period, probably with a more informative error message.
The text was updated successfully, but these errors were encountered:
In automating aartfaac-server, we would like to store the stdout/stderr in log files for analysis of breakdowns. Currently, aartfaac-server generates messages like
'[WARNING] [aartfaac-server-41027] QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState', probably when a pipeline severs its connection. However, the message is written out within a busy loop, resulting in very large log files. Such connections should time out and retry after a reasonable period, probably with a more informative error message.
The text was updated successfully, but these errors were encountered: