Matt Mueller

Should this have been fixed by: https://github.com/rogchap/v8go/pull/223? We're seeing a couple errors: ``` # rogchap.com/v8go ld.lld: error: ../../go/pkg/mod/rogchap.com/[email protected]/deps/linux_x86_64/libv8.a(api.o) is incompatible with aarch64linux ld.lld: error: ../../go/pkg/mod/rogchap.com/[email protected]/deps/linux_x86_64/libv8.a(v8threads.o) is incompatible with aarch64linux clang-14:...

Yes if the node modules don't use node. I'd recommend bundling with https://esbuild.github.io/ then passing the bundle into v8go.

Thanks @rogchap! Good point regarding sharing contexts. I'll avoid that. And yah, I think puddle and sync.Pool are pretty similar, the difference being that you can specify a maximum number...

I also ran into this in [Bud](https://github.com/livebud/bud) where the following test was failing (in this case matching unexpectedly): ```go func TestMatchSubdir(t *testing.T) { is := is.New(t) matcher, err := glob.Compile(`{generator/**.go,bud/internal/generator/*/**.go}`)...

Hey @edimoldovan, that's weird. Can you share your `go env`? I'm curious what your default `GOPATH` is. It seems like the runtime wasn't downloaded. What commands did you run before...

Yep, that would work! You might just need to wrap it to tell Bud how to initialize it. I usually put these wrappers in internal, but it doesn't really matter....

Isn't this expected behavior? If there's a lingering `setInterval`, it would wouldn't exit in Node either.

i think it's just going to take a PR replacing the current stuff haha

+1, I like where this is going but could the `` get a bit long? What if it changed on `suite end`?

Hey @jeffrichie, we're not working on it yet and unfortunately I can't give you an ETA at the moment. For now I recommend what @kentcdodds suggested, which is to have...