Adam Tibbing

Still experiencing this in Wavesurfer 2.2.1, when quickly switching between different sources. Any update?

@mshima Is there any plan to patch this? It seems both related issues have been closed. The yeoman v4 packages now contains sub-dependencies with vulnerabilities, and this prevents us from...

> @tibbing because they have been fixed in [yeoman/environment@cd68282](https://github.com/yeoman/environment/commit/cd68282b238ea895d1dcff2f2a583bd47fb15aca). @mshima Hmm, we are still observing the same error when generating locally using `[email protected]`, `[email protected]` and `[email protected]`: ``` You don't seem...

Hey @mshima! Would be awesome to get this patched, as @TomerAberbach said it's probably as simple as to upgrade `yeoman-environment` to the latest version 🙂

Also running into this issue. In our case we only want to fail the check if the coverage for updated code falls below the threshold, a PR comment is just...

Agreed, this would also fix https://github.com/5monkeys/cobertura-action/issues/40

Bump @pablovarela > @smoya / @der-eismann --> I've forked the repo for now, and I just pushed v1.2.3 that addresses rate limiting for user groups. I used a slightly different...

FWIW I got it working on Lambda like this: ```typescript import { promisify } from 'node:util'; import winston from 'winston'; import WinstonCloudWatch from 'winston-cloudwatch'; export const getLogger = () =>...

Observing similar issue in the latest version of the provider (4.36.0). Works fine in 4.34.0. ``` Stack trace from the terraform-provider-cloudflare_v4.36.0 plugin: panic: interface conversion: interface {} is nil, not...