You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered a little unexpected behavior while using concurrently today, and wanted to file an issue in case it seemed like something worth tackling!
If you use the --timings along with the --group option, the timings table is printed when the last command exits rather than at the end of the output. This can lead to the timings table getting printed in the middle of the stream rather than the end:
❯ ./node_modules/.bin/concurrently --group --timings "sleep 1 && exit""exit"
[0] sleep 1 &&exit started at 2022-04-24 19:28:03.242
[0] sleep 1 &&exit stopped at 2022-04-24 19:28:04.252 after 1,010ms
[0] sleep 1 &&exit exited with code 0
--> Timings:
--> ┌──────┬──────────┬───────────┬────────┬─────────────────┐
--> │ name │ duration │ exit code │ killed │ command │
--> ├──────┼──────────┼───────────┼────────┼─────────────────┤
--> │ │ 1,010 │ 0 │ false │ sleep 1 &&exit │
--> │ │ 5 │ 0 │ false │ exit │
--> └──────┴──────────┴───────────┴────────┴─────────────────┘
[1] exit started at 2022-04-24 19:28:03.249
[1] exit stopped at 2022-04-24 19:28:03.254 after 5ms
[1] exit exited with code 0
The text was updated successfully, but these errors were encountered:
I encountered a little unexpected behavior while using
concurrently
today, and wanted to file an issue in case it seemed like something worth tackling!If you use the
--timings
along with the--group
option, the timings table is printed when the last command exits rather than at the end of the output. This can lead to the timings table getting printed in the middle of the stream rather than the end:The text was updated successfully, but these errors were encountered: