Ryan Slade

> At the moment we fail completely when [the code to fetch repos with the archived label](https://sourcegraph.com/github.com/sourcegraph/sourcegraph@ffa89deaf50ee9f14f1bf15def8d44c04122f218/-/blob/internal/repos/bitbucketserver.go?L199-203) returns an error. Instead, we should log this as a warning and continue...

Just to double check, can we ask their admin to manually try and get the list of archived repos and check how long that takes? It'll be something like this:...

Can we check if the customer has rate limiting enabled on their bitbucket instance? I'm wondering if maybe the newer versions of Bitbucket have rate limiting enabled which is causing...

Correct, bitbucket doesn't have the concept of archived repos so some customers use labels to get around this. This may be a red herring and could just be a symptom...

It would stop the current current sync as we treat it as a fatal error.

It looks like this may have already been done in https://github.com/sourcegraph/sourcegraph/commit/ce750871f59be4672b3d34697b36d60255db3876

No, that change only removed the documentation regarding the config file as a first step before removing support for it. We also have the `-endpoint` flag. I think maybe we...

@sqs Are you happy with the above suggestion, specifically removing the `-endpoint` flag?

We need to keep the endpoint flag around for now as some of our LSIF actions depend on it. I'll submit another PR that removes it from docs but still...

I'm seeing this too and it appears to be a relatively new regression since it only started happening recently, my underlying project code hasn't changed.