• Sourcegraph version: 4.0.0
• Reported by: https://github.com/sourcegraph/accounts/issues/583

Steps to reproduce:

1. Configure a Perforce depot path that will result in no Git commits when p4-fusion runs.
   https://github.com/sourcegraph/accounts/issues/583 depot path had this happen as a result of this message . This seems to be caused by:

It happens to be that if you open a client from a server where the client spec doesn’t originally belong from, you do see the client spec details but you don’t see the exact view mappings, which is what p4-fusion needs.
So p4-fusion requires you to use the same edge server (or a downstream server started from that edge) to create a client spec and also then use that same client spec

2. Let the depot sync and get converted to a Git repo

3. Go to the repository in Sourcegraph and you will see:
   

4. Go to the Site admin > Repository status

5. Click on Settings. It redirects you back to the empty repo.

Expected behavior:

You can see the logs from p4-fusion in the Repository status.

Actual behavior:

You cannot see any logs about why the repository is empty. You must login to the gitserver and run p4-fusion manually to see the output.

If would like immediate help on this, please email support@sourcegraph.com (you can still create the issue, but there are not SLAs on issues like there are for support requests).

/cc @jplahn @ryphil