tessel logs

[Frijol]

Current status: no such command

Spec: T2 CLI spec
tessel logs [-n ] [-t | --tail] [stdout | stderr]

Lists the recent activity and console.logs (100 lines default) from the running program

$ tessel logs --help
> Usage: tessel logs [-n <lines>] [-t | --tail] [--help]
>  -n:          the number of lines of log to display
>  -m|--monitor:    continuously display the logs as they are updated
>  stdout|stderr:   display the logs from the specified output stream
$ 

$ tessel logs -n 2
> Bulbasaur is running index.js
> #[03/31/2015 18:10:28] This is my logggggg
> #[03/31/2015 18:10:29] Look at it!
$ 

$ tessel logs --tail
> Bulbasaur is running index.js
> #[03/31/2015 18:10:28] This is my logggggg
> #[03/31/2015 18:10:29] Look at it!
> #[03/31/2015 18:11:29] Look at it!
> #[03/31/2015 18:12:29] Look at it!
> #[03/31/2015 18:13:29] Look at it!
> #[03/31/2015 18:14:29] Look at it!
> #[03/31/2015 18:15:29] Look at it!
> #[03/31/2015 18:16:29] Look at it!
> #[03/31/2015 18:17:29] Look at it!
> #[03/31/2015 18:18:29] Look at it!
$ 

$ tessel logs -t stderr
> Bulbasaur is running index.js
> #[03/31/2015 18:10:28] Error: index.js:146 - index out of bounds yo
$ 

[nplus11]

The -o in the usage message is old. Needs to be removed and changed to [stdout|stderr]

[Frijol]

Removed.

[johnnyman727]

@sidwarkd are you still working on this task?

[johnnyman727]

I've removed @sidwarkd as the assignee because we haven't heard from him lately. I think this is a non-trivial feature to add: you'll have to somehow overwrite console.log to write to a file whose lifespan is the same as the Node process, then add a command to the CLI to read the contents of that file.

[dbuentello]

Id like to propose additional functionality.

Functionality: Log the boot process
Example interface: t2 logs --boot

The current method to log the boot process is cumbersome. This is due to fact that it happens really early and really fast:

1. know the /dev/serial/whatever location of your tessel
2. enter the command line for screen -L
3. connect the tessel via usb
4. hit enter as fast as you can

I wrote a tool that provided some relief* but implementing this in the CLI would be awesome. It can also help when providing support.

*I still had to switch between terminals 😅

[dbuentello]

@johnnyman727 I'll look into overwriting console.log, any ideas on capping the size?

[Frijol]

@dbuentello that idea seems reasonable to me – sounds like this is something you've needed in the past?

I don't think we need to worry overmuch about the size of the logs