Bad behavior when repo is not on Sourcegraph instance

[sqs]

Version: 1.12.1, Sourcegraph URL = https://sourcegraph.sgdev.org

Repro:

1. Visit https://github.com/sourcegraph/sourcegraph-basic-code-intel/blob/master/.editorconfig, which is a repository that is NOT currently on our internal Sourcegraph instance (nor is it on sourcegraph.com because it is a private repository)

When the page loads, the JS console shows the following error:

Error: no sourcegraph urls are configured
    at new t (inject.bundle.js:21)
    at r (inject.bundle.js:21)
    at t.selector (inject.bundle.js:21)
    at t.error (inject.bundle.js:31)
    at t._next (inject.bundle.js:15)
    at t.next (inject.bundle.js:15)
    at t.next (inject.bundle.js:31)
    at XMLHttpRequest.o (inject.bundle.js:31)

This is incorrect, because my Sourcegraph URL is set to https://sourcegraph.sgdev.org and other private and public repos work.

Also, there are no View file buttons. Clicking View repository opens the extension's options page instead of the repository.

[ijsnow]

What would you like that error to say? "Repository not found?". Because that's what the problem is. I think it should at the very least be logged rather than swallowing it silently.

There shouldn't be a "View file" button because we don't know where the file is.

The "View repository" button should certainly not take you to the options page

[sqs]

For now, remove the incorrect button and change the error to say “Repository not found on $url”. @francisschmaltz can work with you to improve this UX in the future.

[felixfbecker]

I've just wanted to file this too.

https://github.com/sourcegraph/deploy-sourcegraph-dogfood

[sqs]

dupe of #946