David
> Thanks - I think proxies should work well. Just for context, when we started out, we had to support browsers that didn’t have proxy support and we never re-visited...
@TkDodo yes sorry, been very busy with work and the holidays. I will be taking this up, sorry for the delay
So I did find a root cause of this. It turns out that even though I thought I had one package in the workspace that specified that dep, I had...
@jbedard here is a screenshot from me reproducing the failure with `bazel coverage` using vscode codespaces off of `main` Here is the code ``` # A simple program that runs...
I can confirm also that applying this fix with that code fixes the bug
@thesayyn so are you suggesting that @joeljeske's fix would be preferred? > Presumably you could fix this more properly by having js_test also have a _is_test attr that is set...
@thesayyn Ok I believe I have added the fix as interpreted from @joeljeske's comment. I confirmed with the same test as before that this fix works too
Looks like this breaks some CI stuff. I'll have to spin up an ubuntu container and debug why `bazel coverage //...` is failing
@achew22 I found an issue with my prior change and would like to upstream what I believe the fix is. Would you mind taking a look?
Sure I can try and add a test case. The basic gist from the logic I followed is that in this case this arg needs to be passed to `bazel...