inconsistent terminal output from snap job status window

[master-of-neutrons]

i am seeing SNAP execution behavior that i dont understand. i have two streams, i submit them to local. the job status window for one stream displays the terminal output of the relap execution but not for the other stream. why are these streams/snap behaving differently?

because the streams execute differently even though they were launched the same way from the same .med file, it makes me uncertain that the runs are not somehow corrupted

relaunching the stream that failed to write to the job status window while executing, perhaps 0.5 to one hour later, that stream wrote terminal output in the job status window EVEN THOUGH NOTHING WAS CHANGED

[NRCgg]

@WDunsford This was submitted by an NRC user that brought it to my attention. Once I saw what was happening I recalled others had seen such behavior. I don't know what causes a stream not to output something - but then output something when relaunched sometime later. I assume that there is a file-lock or network socket that is blocking the first attempt?

In any case, there should be some indication presented to the user to indicate what is happening!

Also, should I make a new GitHub label for this kind of issue so that they are easier to find? Let me know.