Why do console lines have different colors?

zapta

Below is a screenshot of executing the same command a few times. Some of the lines are blue and some are green. Do the colors mean something?

T3P3Tony

@zapta errors are red, warnings are yellow/orange, info is green or blue. but its a good question why the same command or type could sometimes be blue and sometimes gree. Definitely a question for @chrishamm

chrishamm

@zapta @t3p3tony empty replies usually indicate a success (green) whereas replies not starting with "Error" or "Warning" mean an info message (blue).

zapta

Thanks @chrishamm, this explains it. If another open DWC tab occasionally steels the output from duet (a long standing issue), it will result with this behavior and color difference. Which brings two questions:

Any chance of of fixing the duet/DWC behavior when another DWC is happened to be open? Duet/DWC seem assume blindly that only a single tab is open which result in unpredictable behavior when the assumption is false (e.g. when running a macro, some echo are shown, while other are omitted).
Is the color distinction between commands that have output and comment that don't really useful for the user?

chrishamm

@zapta Yes, we've got a new approach for HTTP session management planned but I cannot give you a definite ETA yet.

zapta

Thanks @chrishamm.

I think it's possible to have a stateless duet that support proper console output to any number of clients. It's based on the fact that the polling interval T is relatively short. Something along these lines:

Duet keeps only last lines not older than T + some margin.
Duet tracks sequence number of each line from start.
When returning lines to a client, duet also returns seq number of last returned line.
Client pass that seq number in next call and duet sends back only newer lines.

Or something like this. The duet's memory overhead is independent on the number of clients, and client can tell if they lost lines for any reason.

BTW, having multiple DWC clients at a same time is a common use case. For example, when debugging a macro, I open the file in one tab and issue manual commands in another.