New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 719056 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: May 2017
Cc:
j...@chromium.org
flyboy@chromium.org
rauch+monorail-auto@google.com
█ orodley+autocc@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

cs.chromium.org cross-references are wrong.

Project Member Reported by lgar...@chromium.org, May 5 2017 
What steps will reproduce the problem?
(1) Visit https://cs.chromium.org/chromium/src/net/http/transport_security_state.cc?q=dirtynotify&l=1321
(2) Click on "StateIsDirty"

What is the expected result?
Get taken to the definition of "State is Dirty"

What happens instead?
Get dumped on an unrelated line at https://cs.chromium.org/chromium/src/net/http/transport_security_state.h?l=52

Comment 1 by emso@chromium.org, May 17 2017

Status: WontFix (was: Untriaged)
Thanks for the report and sorry for the inconvenience. Xrefs are computed periodically by a pipeline parallel to the Git integration that was added recently to code search. This setup gives us an Xrefs latency of many hours. We are working on reducing this latency (crbug/697786).

I can't reproduce this problem any more, but please re-open this bug if the problem reappears.

Comment 2 by lgar...@chromium.org, May 17 2017 

> This setup gives us an Xrefs latency of many hours.

Is it expected that references are incorrect during this time? If so, dupe of  Issue 697786  sounds correct.

Comment 3 by emso@chromium.org, May 18 2017 

Yes, unfortunately that is the case. The best we can do is to speed up the generation, but there will always we some delay.

Comment 4 by lgar...@chromium.org, May 18 2017 

Alright, that's fair. Thanks for the reply on this bug!
►

Sign in to add a comment