Tim Fish

I think you're seeing this: https://github.com/microsoft/vscode/issues/116783 Which has a linked v8 dev tools issue which is still open: https://issues.chromium.org/issues/41161875 The argument is that debugger should not break here because the...

I've opened a PR in `opentelemetry-instrumentation-fetch-node` which should stop this from hitting the debugger issue.

> @timfish > Did you test this PR if it resolves the issue? No sorry. I looked at the open Chromium debugger issues and the causes and then made assumptions...

We're going to drop `opentelemetry-instrumentation-fetch-node` in favour of `@opentelemetry/instrumentation-undici` which should help solve this issue. I'll respond in this issue when this makes it into a release.

Looks like the task list needs updating because Node v14 doesn't support vitest?

Almost everything is now migrated to Vitest. There are a couple of packages where I've created branches to migrate them but got stuck on some blockers: ## `@sentry/remix` Branch -...

Our instrumentation hooks the `google-gax` module. If you mock out the PubSub object, it'll never hit any of the `google-gax` code and the instrumentation does not get tested. I'm OOO...

Looks like I need to pull my Windows laptop out and work out why those tests are failing!

So the failing unit test (`zeromq-node-gyp`) passes in isolation on my Windows machine but fails when all the tests are run. One thing I don't understand is how it's passing...

Unfortunatly not 😭 I'm more confused as to how this test passes on any platform. The additional dependency in the failing case looks like it should be included!