Issue 712468  has been merged into this issue.

 Issue 711835  has been merged into this issue.

can we maybe just deactivate webrtc while this is sorted out

Sorry about this. Adding WebRTC as a separate package is the typical way of adding a new project to code search based on how things are designed. However, with chromium being the only package until now this means searching now requires filtering on the chromium package. 

Rolling back WebRTC to only staging again until we sort out how we want to handle this.

We need to verify that the cleanup procedure is correct which means we will cleanup staging before prod. This takes a little while. Sorry for the inconvenience. 

maybe we can change cs.chromium.org to just include package:^chromium$ in the default query?

That is one option. IT's added by default in some of the cases but not when you add a search without it in the search bar (except from the start page). We are rolling back to re-asses and then try again. Fully rolled back on staging as a test. I'll start the rollback on prod this afternoon CPH time.

WebRTC should be fully rolled back and there should not be any mixed results. Please re-open the bug if you still experience the issue.