Ethan Atkins 4cea09937c Set isSuccessEnabled in network channel consistently ... The thin client needs to do its own success reporting because in batch mode it's possible for the task to exit before success is logged by the server. If the server also prints success, there can be double printing. Unfortunately, the Prompt.Batch check is not reliable because MainLoop will change the prompt to Running during task evaluation. The interactive flag is set in the NetworkChannel when the client explicitly registers itself as an interactive session, so this should be more reliable.		2020-09-21 13:42:03 -07:00
..
src	Set isSuccessEnabled in network channel consistently	2020-09-21 13:42:03 -07:00
NOTICE	Add, configure & enforce file headers	2017-10-05 09:03:40 +01:00