mirror of
https://github.com/golang/go
synced 2024-11-18 13:04:46 -07:00
59c6fc0b54
I finally spent the time to understand why branch changes were causing unexpected errors. There may be other bugs, but this is the first I spotted. For batched invalidations, we were overriding the value of invalidateMetadata for each file, so the results depended on the order of files in the didChangeWatchedFiles notification. Change-Id: Id3ca7a758af0115c46dcd74ede590a0be3f8307d Reviewed-on: https://go-review.googlesource.com/c/tools/+/244606 Run-TryBot: Rebecca Stambler <rstambler@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> |
||
|---|---|---|
| .. | ||
| analysisinternal | ||
| apidiff | ||
| event | ||
| fakenet | ||
| fastwalk | ||
| gocommand | ||
| gopathwalk | ||
| imports | ||
| jsonrpc2 | ||
| lsp | ||
| memoize | ||
| packagesinternal | ||
| proxydir | ||
| span | ||
| stack | ||
| testenv | ||
| tool | ||
| typesinternal | ||
| xcontext | ||