GoDanno wrote:The script didn't generate any output.
You get this when the script doesn't print anything out to stdout, and will also generate the "can't determine the feed type" error, since what you're seeing as the last feed is obviously not a valid feed.
This is where it gets interesting...
One of the things that came out of the aforementioned extensive stress-testing was that Windows would sometimes exhibit some utterly bizarre behaviour where a plugin would generate it's output, it got saved in the temp file Awasu created to capture it, but when Awasu went to read the file, it would be empty, or full of zeroes. This was insanely difficult to track down since it was very intermittent and also very transient; if you waited a second or two after the plugin finished, the file contents would mysteriously become available.
I put something in to work around the problem but it may be the case that this is what's causing your problem. IIRC, this didn't have anything to do with running multiple plugins simultaneously, it would happen even with just one plugin running. The way to check if this is what's happening is to be absolutely sure that the plugin is writing to stdout (e.g. I would build the feed in a string buffer and then print it to stdout and another temp file), then wait for the channel to get the error. If you get the "script didn't generate any output' error but you're sure that it did, then what I described above might be what's happening.
Also, let me know what version of Windows and how many CPU's you have.