AJ Danelz

@awesome-doge When I run it against my fork, it comes back clean. I believe those errors have to be handled by the repo maintainer, which I have mentioned in the...

@zacharywhitley The only step left for these lint errors to be resolved is for you to add a repo description.

@sindresorhus @awesome-doge All of the linter rules are passing and the checks are passing.

@zacharywhitley @sindresorhus @awesome-doge bump

+1, not having this will be pushing us to use a different solution.

Hey @jyguyomarch I got some of these changes covered but if you think yours could improve the repo you could rebase your PR.

Hi @taylorfturner, sorry for the delay, I am helping the maintainer now. thank you for the suggestion. If you think this should be added, please create a PR.

I have been using it on Windows 64bit. However it was inside of WSL. i will run inside of both cmd and powershell and report back.

after digging around it looks like this all ties back to the aws cli. The progress for the fix is being tracked by @mariano-calandra-xp's ticket here https://github.com/localstack/localstack/issues/1783

could fix or make troubleshooting for this community issue better: https://github.com/aklivity/zilla/issues/1268