Closed justinmetz closed 8 years ago
Hi Justin, Can you confirm what build you are on so I can make sure I'm investigating with the right source. Can you click on the help button and there should be a version on the top. Thanks, Eamon
Hi Eamon,
Here's the info from the help tab..
Release informationVisit the Github Commit Page https://github.com/azureautomation/azure-automation-ise-addon/commits/masterfor latest improvements.
Updates for release 0.2.3.2
Thanks,
Justin
On Mon, Apr 4, 2016 at 12:25 PM, eamonoreilly notifications@github.com wrote:
Hi Justin, Can you confirm what build you are on so I can make sure I'm investigating with the right source. Can you click on the help button and there should be a version on the top. Thanks, Eamon
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/azureautomation/azure-automation-ise-addon/issues/107#issuecomment-205375802
Thanks Justin. I'll have a look. Could you verify one more thing for me? If you look at this job in the Azure portal, does it have the duplicate lines also or is it correctly displaying there? This will let me know if it is an engine issue within the service or the ISE Add-On that is doing something incorrect. Thanks again, Eamon
Here's the output in the Azure portal test console... Seems to work in there..
FWIW, I've seen this a number of times as well, but have never been able to pinpoint it (slash, never had the time to spend trying to repro).
I have assumed that it has to do with how the ISE plugin makes the numerous requests to stream the log data back to the client, and then adds them to the display. If data is coming back in batches, and once batch overlaps another (because more data is being added from the job), it would make sense that the plugin code may be ignoring the overlap?
That said, I can't rule out having seen it in the web ui.
Generally, I want to say that when I did see it, it was typically one of the first messages to get written to output. IE: if doing some processing in a loop, I might see the first iteration's output twice, but then all the remaining output wouldn't dupe.
Unfortunately I also am not sure if closing then re-opening the test job window or the test pane makes this duplication go away, or if even I saw the same duplication between the web ui and plugin (ie: once the job has completed; if it did, that would seem to indicate it's an engine thing, perhaps.)
I know that's all not very helpful and circumstantial (at best), but just to say I've seen it intermittently under these circumstances :)
HTH :100::dash:
Thanks guys. Hopefully this is addressed now with the latest check in. I'll do a build next week and push to the PowerShellGallery if there doesn't seem to be any regressions and the issue is fixed. Thanks, Eamon
It looks like a single Write-Output call is echoed to the Test Job output window multiple times. An example of this behavior shown between the test job output and a local txt log of the same runbook instance is attached.