Eric Boehs

I think we should patch this everywhere, not just CI/test. A large cost in DD is superfluous logs. Is there a reason we should keep this in other places besides...

This seems like something the community should care about. Yarn caching in the nodejs buildpack has supposedly been around for 2+ years. Our yarn install takes 50+ seconds each deploy....

Schneems suggestions seem to be helpful. Sort of. Here's how you do it: * Add the nodejs buildpack before your ruby buildpack. It will cache node_modules but not remove it...

I have done some primitive caching of the node_modules here: https://github.com/ericboehs/heroku-buildpack-ruby-yarn-cache/commit/f851a9560ff7363818b530bbe14490da5c51d5f6 (this isn't production ready as it will need cache pruning). ~It seems to be almost identical in execution time...

Hmmm. After testing my caching buildpack a few more times, it seems it does indeed save 10-20 seconds (my last run saved 19 seconds) compared to running with the nodejs...

Sorry for the delay, I wasn't watching this repo so I wasn't getting notifications. @anders0ndg I don't have the delay issue with my Roku TVs. I've been using this adapter...

I'm not sure. Perhaps it's not able to parse the lan hub command. Maybe your Device Network ID isn't right? All the handler is looking for is "PowerOn" to be...

By the way, I've updated the handler to include buttons for volume, input selection and a couple of example app launchings.

@ryan-mcneil to create an issue for "Enumerate which cassettes need to be updated" then we'll refine this one.

https://github.com/department-of-veterans-affairs/va.gov-team/issues/87359