Progress bar when deploying

[johnnyman727]

It would be really useful to be able to see how long it might take for a code bundle to be deployed over T2 (especially over USB).

[rwaldron]

Absolutely. Yesterday I introduced @goliatone to T2 and this came up.

[johnnyman727]

I tried progress-stream library last week but for some reason that I can't recall anymore, it didn't work. I can give it another try this week.

[johnnyman727]

The difficulty is that we basically dump a single buffer into the stdin stream instead of actually piping a stream into it. If you try to use progress-stream, it will report that it has completely deployed immediately. We would need some way to introspect the internal stream backlogging mechanism to get actual data of how much of the bundle we've transferred... The Node docs don't give much insight into how to do this.

[johnnyman727]

See work in progress here: #304

[johnnyman727]

One possibility might be to change the result of the tarBundle function so it returns a stream? The usb transfer process will likely be slower than the tarring operation.

[johnnyman727]

An easier way to do this is use the du command on T2 to get the size of the folder. Just run that command at an interval and you can get a real time update of how many bytes have been transferred.

The only confusing thing is that OpenWRT seems to report folder sizes different (higher) than OSX.

[johnnyman727]

I attempted to build a progress bar using the du command on OpenWRT but, as I said above, OpenWRT always returns a slightly different file size. Branch is here.

[LinusU]

are-we-there-yet might help you tie everything together. I think it's used by npm :)