Server.log out from Agent mixed up

I am having a problem resolving output from the server.log when run from an agent.

The sequence of output when doing multiple server.log() commands is mixed up. Below is example output when trying to display the content of a blob/buffer. the 4 hex digits on the left show the offset/index into the buffer/blog and and we can see the sequence makes no sense.

Any suggestions??

Andre

2013-11-29 14:53:44 UTC+2: [Agent] 0060-> 5105 5EE5 5FB5 6436 6166 5CE5 67D6 6D56
2013-11-29 14:53:44 UTC+2: [Agent] 0050-> 3E43 4D14 50F5 5205 5465 47C4 46B4 5545
2013-11-29 14:53:44 UTC+2: [Agent] 0040-> 5C15 5AA5 5C15 5AD5 5E35 5B25 55E5 4D24
2013-11-29 14:53:44 UTC+2: [Agent] 0030-> 80C8 7AE7 7C77 76B7 7537 7427 6FA6 6D06
2013-11-29 14:53:44 UTC+2: [Agent] 0020-> 9089 8F88 98C9 93E9 8288 8798 8728 8708
2013-11-29 14:53:44 UTC+2: [Agent] 0010-> 91C9 A87A A75A 98F9 9579 91A9 92D9 8FB8
2013-11-29 14:53:44 UTC+2: [Agent] 0000-> 7A67 7DF7 8218 87A8 85F8 9059 88D8 9909
2013-11-29 14:53:44 UTC+2: [Agent]
2013-11-29 14:53:44 UTC+2: [Agent] -------- Blob length = 0234 (0x00EA) --------
2013-11-29 14:53:45 UTC+2: [Agent] 00E0-> 5D15 6A66 67C6 7577 6336
2013-11-29 14:53:45 UTC+2: [Agent] 00D0-> 53A5 4D64 4F34 5205 53F5 5705 4FF4 59F5
2013-11-29 14:53:45 UTC+2: [Agent] 00C0-> 56A5 5FD5 4FA4 3F43 4754 4E34 52A5 5695
2013-11-29 14:53:45 UTC+2: [Agent] 00B0-> 6EF6 7077 70A7 6C06 5CF5 5605 5D15 55C5
2013-11-29 14:53:45 UTC+2: [Agent] 00A0-> 8F78 8BC8 7E67 7E67 7E17 7F37 7BF7 71A7
2013-11-29 14:53:45 UTC+2: [Agent] 0090-> 94A9 9669 9A19 9B39 9E69 8CB8 87F8 8EB8
2013-11-29 14:53:45 UTC+2: [Agent] 0080-> 8688 8C48 8D98 9BD9 A36A 90C9 9F59 97E9
2013-11-29 14:53:45 UTC+2: [Agent] 0070-> 68A6 6756 67A6 7057 7E47 8388 8038 78C7

I’m used to put a (very) small delay after every server.log().
You could even write a function to do this.

I see this a fair bit. Not too much, maybe about 10% of the time, but things which are logged in quick succession don’t always come through in the order they were sent. I guess due to the nature of async network requests being fired off, and being delayed by different amounts.

This is a known issue we’re working on fixing. If you refresh the browser I believe they come back in the right order - it’s the streaming to the browser which isn’t correctly ordered.