Ben Leitner

> We don't currently support absolute paths in `replace` directives and I'm not sure we will any time soon: Bazel is very much designed to not reference absolute paths in...

I tried to revisit this today since I have plans for a little project that I want to keep out of my main "monolith" repo but still be ablw to...

I don't know what changed, but after a couple updates to the plugin, now if I try to sync while the `.git` directory exists, the sync crashes due to malformed...

This (along with partial sync never working because path errors) is one of the bigger pain points with using Bazel on windows. It's been several months since it got the...

Any progress/thoughts/ETA? This is consistently the most irritating issue when using bazel on windows (this, and the fact that partial sync doesn't work because path names). Having to disengage the...

Something seems to have changed as the behavior is now back to what it was prior to my March 26th, 2021 update. Pressing the sync button no longer leads to...

It had been a while since I did work on my personal projects, but I decided to poke around today and thought of checking on this issue in the process....

> > 1. shows an error in bazel problems: > > ``` > > "Error: no such target '//:WORKSPACE': target 'WORKSPACE' not declared in package '' defined by" > >...

Sorry for the delay. I was out of town for a while. > Oh, I forgot there was one in the message from 2021. Could you please add your "guava"...

For a comparison, I also checked with IntelliJ for my java tests (same bazel plugin version) and it worked fine there, so it does seem to be golang specific.