pm2 logs big-api is automatic now?

[mattcasey]

I just upgraded to pm2 1.9.4 from 1.8. Is 1.9 stable? (I ask because I know mongoose for instance is only stable for every other version). I used the in-memory pm2 updatePM2.

"pm2 logs" takes me to this big screen now, I figure it's what the big-api flag triggers. It also outputs arrays of numbers, there's no actual message (sorry for formatting.. it's copy/paste):

Starting logs for: #1 user-home ││ │
│ ││ │
│ (out) July 29th 2014, 2:26:15 pm: [ 123, ││ │
│ 125, ││ │
│ 32, ││ │
│ 123,

Please tell me how to get the usual stream of logs... that was a nice feature that I could use to stream logs from remote servers, now it just throws this error (because I'm calling pm2 logs remotely and it's trying to do big-api, I assume):

/home/ubuntu/npm/lib/node_modules/pm2/node_modules/pm2-logs/node_modules/blessed/lib/program.js:241
throw new Error('Not a terminal.');
^
Error: Not a terminal.
at Program.listen (/home/ubuntu/npm/lib/node_modules/pm2/node_modules/pm2-logs/node_modules/blessed/lib/program.js:241:11)
at new Program (/home/ubuntu/npm/lib/node_modules/pm2/node_modules/pm2-logs/node_modules/blessed/lib/program.js:89:8)
at Program (/home/ubuntu/npm/lib/node_modules/pm2/node_modules/pm2-logs/node_modules/blessed/lib/program.js:28:12)
at new Screen (/home/ubuntu/npm/lib/node_modules/pm2/node_modules/pm2-logs/node_modules/blessed/lib/widget.js:256:20)
at Function.Screen (/home/ubuntu/npm/lib/node_modules/pm2/node_modules/pm2-logs/node_modules/blessed/lib/widget.js:245:12)
at module.exports (/home/ubuntu/npm/lib/node_modules/pm2/node_modules/pm2-logs/lib/log-interface.js:8:24)
at /home/ubuntu/npm/lib/node_modules/pm2/node_modules/pm2-logs/lib/logger.js:423:49
at /home/ubuntu/npm/lib/node_modules/pm2/node_modules/pm2-axon-rpc/lib/client.js:45:10
at Parser.onmessage (/home/ubuntu/npm/lib/node_modules/pm2/node_modules/axon/lib/sockets/req.js:65:8)
at Parser.frameBody (/home/ubuntu/npm/lib/node_modules/pm2/node_modules/axon/lib/parser.js:106:10)

[soyuka]

There was a bump fix (2a07d05) that fixes this.
Should be published soon.

[mattcasey]

thanks... npm doesn't see the version 0.9.5 yet, I'll just git clone for now