Ryan Khalil

Just to experiment I tried also adding `this.kinesis.destroy()` after running `stopConsumer()` to see if I needed to do that and the stream handlers are still showing up as a leak...

I'm actually seeing the same behavior with the kinesis-client, too now. I updated to the latest version of lifion-kinesis cause I realized I was using a slightly older version. ```...

Workaround is to install yarn yourself using npm (after running this action) ``` - name: Install Yarn run: npm install -g yarn ``` and later can uninstall it - ```...

@konsalex Since self-hosted runners are shared and are not a clean instance per job execution, like a github hosted runner would be, the job should do its best to clean...