[Sourcegraph] Self-hosted sourcegraph search doesn't work

[dleen]

Extension – Sourcegraph

Author: @bobheadxi

Description

Searching using self-hosted url doesn't work.

Error:

Error: Protocol error

__node_internal_captureLargerStackTrace:errors:464:5
NghttpError:util:555:5
Http2Session.onSessionInternalError:core:784:26

Steps To Reproduce

1. Configure self-hosted sourcegraph address e.g. https://sourcegraph.mydomain.net, enter API key
2. Do a search

The current behavior

The search doesn't work...

The expected behavior

The search results are shown

Raycast version

Version: 1.30.3

[bobheadxi]

@dleen What version of Sourcegraph is your self-hosted Sourcegraph instance?

[dleen]

Good question, sorry I should have included it: 3.37.0

[bobheadxi]

No worries! Is your instance hosted behind networking restrictions of any kind? I use Sourcegraph's internal self-hosted instance regularly, and am unable to reproduce your issue:

[dleen]

Yes, my sourcegraph instance is only available via a VPN. But I made sure the VPN was connected, I can access the instance fine via browser, and via curl.

I think I'll check out the extension and run it locally with some debug statements to see what's happening...

[bobheadxi]

I did some brief searches regarding this. Threads like this one indicate that we might need to introduce additional configuration to connect to VPNs, but I'm not terribly familiar with VPNs in general so I'm not too sure where to start.

If you could share a more complete error message, or some details about your VPN setup, that might be helpful!

[dleen]

I got around to looking at this.

If you could share a more complete error message, or some details about your VPN setup, that might be helpful!

Unfortunately that error message is the entire message. Nothing else shows up. I don't think the VPN setup is the problem because I am able to reach the instance using all other clients just fine e.g. the sourcegraph curl instructions work.

I installed the extension locally but it didn't give any extra error details. The error said Error: Protocol error so when I took a look at the code I did notice that it was using EventSource and http2:

import EventSource from "@bobheadxi/node-eventsource-http2"

I took a look at the library and saw that it was a fork because the original didn't support http2. I swapped out the EventSource library for:

import EventSource from 'eventsource'

which actually worked and returned results from the server.

This ran into its own problem where it never stopped (requesting?) returning results until it hit a memory limit:

Error: Worker terminated due to reaching memory limit: JS heap out of memory

__node_internal_captureLargerStackTrace:errors:464:5
NodeError:errors:371:5
Worker.[kOnExit]:worker:279:26
Worker.<computed>.onexit:worker:201:20

Maybe that's an issue with the library being different from the fork and some code needs updating to stop returning results?

But it was good to make some progress.

I'm not sure why the http2 library didn't work or what the protocol error actually means. When I visit my sourcegraph instance in the browser and inspect the network requests I see some h2 requests (although just for JS assets, not the actual API queries).

[bobheadxi]

Interesting, I tried eventsource when first creating the extension and I couldn't get it to work. I see they cut a new release recently (https://github.com/EventSource/eventsource/releases/tag/v2.0.0), and I am indeed able to get it to work now - I'm not sure if something changed in the library or on our end 🤔

I saw the memory limit issue as well and I think I've fixed it with bobheadxi/raycast-sourcegraph@0b66d0a

[bobheadxi]

The update will be included in #1228 ! Thank you for looking into this 🙏

[bobheadxi]

@dleen did the new update resolve your issue?

[dleen]

Yep! Works perfectly, thanks!!