3 ms·

It's interesting that you bring up "more code metadata" and "self-hosted deployment" as strengths of Sourcegraph. I work for a company that licenses the self-ho

It's interesting that you bring up "more code metadata" and "self-hosted deployment" as strengths of Sourcegraph. I work for a company that licenses the self-hosted enterprise SG. We have had bugs open for months due to code metadata issues crippling the usefulness of the tool. Specifically, deleted repositories are not getting de-indexed and archived repositories are not getting indexed as such. This makes search results extremely noisy and in some cases outright incorrect. This forces our teams to create extensive "search contexts" in order to find relevant results. I use this tool daily and advocate for more usage internally, which speaks to its usefulness, but it's painful to teach new users all the caveats of poor data quality.

sqs 4y ago
I'm really sorry about those problems. Can you please email me at sqs@sourcegraph.com and let me know which company you're at? I will see why these haven't been fixed yet and figure out how we can get them resolved for your company ASAP. edit: The person emailed me (thank you!), and we will get this resolved ASAP.
metadat 4y ago
@sqs: Quinn, is it common to leave enterprise customers' bugs open for months? Why does it take social media escalation to gain traction? I say this as a big fan of SG, because issues like this ring like a big red alarm bell to me. The GitHub monopoly stranglehold over OSS needs to be broken, not further enriched. You are one of our only hopes..
- sqs 4y ago
  No, this is neither common nor acceptable.
  - COMMENT___ 4y ago
    Just passing by, but I’d love to read a story what happened with this user’s bug report. This looks like a serious usability problem for those who delete or re-create repositories often, and I guess that it wasn’t prioritised correctly or went into dev/null due to pilot’s error. So where exactly this report got stuck?
    - metadat 4y ago
      +1, good idea @COMMENT___.

sqs 4y ago

I'm really sorry about those problems. Can you please email me at sqs@sourcegraph.com and let me know which company you're at? I will see why these haven't been fixed yet and figure out how we can get them resolved for your company ASAP. edit: The person emailed me (thank you!), and we will get this resolved ASAP.

metadat 4y ago

@sqs: Quinn, is it common to leave enterprise customers' bugs open for months? Why does it take social media escalation to gain traction? I say this as a big fan of SG, because issues like this ring like a big red alarm bell to me. The GitHub monopoly stranglehold over OSS needs to be broken, not further enriched. You are one of our only hopes..

sqs 4y ago
No, this is neither common nor acceptable.
- COMMENT___ 4y ago
  Just passing by, but I’d love to read a story what happened with this user’s bug report. This looks like a serious usability problem for those who delete or re-create repositories often, and I guess that it wasn’t prioritised correctly or went into dev/null due to pilot’s error. So where exactly this report got stuck?
  - metadat 4y ago
    +1, good idea @COMMENT___.