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
Is your feature request related to a problem? Please describe.
When executing long-running shell commands, it is not possible to track progress. even if the command sends progress info via stdOut. We can display an infinite progress bar or another indicator to the user, but there is no real live-info.
Describe the solution you'd like
Each data sequence terminated with a linefeed, coming from stdOut is read into a buffer.
Next a JS event is triggered in the frontend, called e.g. progress.
This event receives the buffered, raw data as a string for further processing.
The buffer is cleared and the next line is read from stdOut.
Loop until command terminates.
When the command has been terminated an additional event called progress_end could be triggered.
Describe alternatives you've considered
No alternatives, as far as I can see ....
The text was updated successfully, but these errors were encountered:
hschneider
changed the title
Execute a shell command and emit events via stdOut
Execute a shell command and emit events triggered by stdOut
Feb 24, 2024
Right, so the same for stdErr would be useful, maybe the events should be better named cmd_stdout and cmd_stderr triggered line by line and cmd_start and cmd_end triggered before start and after end of the external process.
Is your feature request related to a problem? Please describe.
When executing long-running shell commands, it is not possible to track progress. even if the command sends progress info via stdOut. We can display an infinite progress bar or another indicator to the user, but there is no real live-info.
Describe the solution you'd like
Describe alternatives you've considered
No alternatives, as far as I can see ....
The text was updated successfully, but these errors were encountered: