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 some cases, a nix command can take a while to run (cf. IFD use in nammayatri). When that happens, it is useful to see live feedback (command's stdout/stderr) in the browser itself.
This can also come in handy when interacting with Nix from the browser (eg: #9).
nix commands' progress output is redirected to stderr. Looks like if the session is not TTY, the output is no more a progress bar by default and it will look like this. This looks better than a Spinner but sometimes it can be stuck on a command (for instance, downloading a huge tar) and the user might be clueless about the status.
Got a suggestion on matrix to use PTY to display the progress bar. Will this be useful in the long run if we will allow users to interact with the terminal from the browser?
For this task, we only care about streaming nix's output in the browser―not user interaction. User interaction can happen in a future task, possibly based on raphamorim/rio#25
but sometimes it can be stuck on a command (for instance, downloading a huge tar) and the user might be clueless about the status.
That's fine, for now. The browser view should obviously have some indication that the command is still running.
In some cases, a nix command can take a while to run (cf. IFD use in nammayatri). When that happens, it is useful to see live feedback (command's stdout/stderr) in the browser itself.
This can also come in handy when interacting with Nix from the browser (eg: #9).
Potential libraries to use,
The text was updated successfully, but these errors were encountered: