What search engine can find this line of code on Github?

sparr@lemmy.world to Programming@programming.dev – 37 points –

https://github.com/ocelot-inc/ocelotgui/blob/19349c7334347eb37ef61b9694390581ea5db238/ocelotgui.cpp#L16896C5-L16896C29

I need to find this line of code based on the keywords "tnt_select" and "2^32", without specifying the repository because I'm looking for instances of the same bug in other projects. This repo is public, the file isn't obfuscated, the code is in the head of the default branch. I've tried Google, Github Code Search, Sourcegraph, and BigQuery on the Github data set. I've found a few ways to locate the .rst and .po documentation files that the bug was copied from, but none that find even this single example of it in actual source code files.

10

I tried this in my Grasp account, a search engine that is pre-loaded with all the Hacker News blogs and other select technical website, and builds results in associated degrees of relations from there. It came up with 8 repos searching for:

https://usegrasp.com/search?q=github+%E2%80%9Ctnt_select%E2%80%9D+

Also I want to say, your scenario is troublesome that GitHub itself could not come up with a satisfactory answer. Strange.

Also I want to say, your scenario is troublesome that GitHub itself could not come up with a satisfactory answer. Strange.

They have github.com/search, but for some reason it returns zero results... presumably it's a limitation (optimisation?) of their search index.

Any chance you'd be willing to share those results? The site isn't accepting signups any more.

Weird, clicking your link github shows me:

(Sorry about that, but we can’t show files that are this big right now.)

I can click the "raw" link, which shows the whole 32k line file, but then I don't know which line you were trying to reference.

Can you give us the specific line number(s) you were interested in?

I'm not sure why, but GitHub's search engine, Blackbird, seems to be returning some erroneous results for this query:

Any chance you could narrow down your search to a list of repose that use the library that pulls in tnt_select() function, then clone and manually grep just those, or is it's use too common to index by?

Real funny that even narrowing down GitHub search to just the same repo doesn't help the query results:

I have considered that approach. I'd probably do it in the cloud, in parallel, maybe even in a serverless compute environment. But it does seem like a big endeavor.