Closed robinjoseph08 closed 8 years ago
On second thought I can't seem to reproduce what you describe, I tested with minicron run composer
and for me it displays as I would expect. See (http://cl.ly/e8RL > http://cl.ly/e8ZU).
Feel free to re-open if this is still an issue.
That's weird... I'm not sure how composer prints out it's contents, but it might print it all out to stdout before it flushes the stream. Try it with echo "hello" && echo "world"
:
Weird... still can't reproduce this, the only noticeable difference seems to be you're running the linux build whereas I'm testing this on OSX. Is this version 0.8.4?
Even on the linux-x84_64
build I'm still get the expected output ordering, very odd.
Yeah, it's v0.8.4. This is strange.
I took a closer look into the setup of things and I think I might have found a possible culprit.
It looks like when the execution outputs are loaded to be displayed, an explicit ordering isn't being set. And without an ORDER BY
clause in SQL, there can be no assumptions made about the ordering of the returning rows. I'm using Postgres in my implementation. Are you using SQLite? It might just be the difference in DBs (and the fact I have a lot more outputs in my table) that's causing this.
If you leave the issue open, I should be able to submit a PR by today to fix it.
Oh that would explain it, I don't test with Postgres very often 😳. MySQL/SQLite default to ascending order by the primary key as far as I'm aware but it should be ordered by the seq
field to make sure it maintains the correct ordering. Nice find!
Right now, the output of an execution is actually displayed with the first line produced is at the bottom. So the following code:
Produces the following: