this post was submitted on 19 Nov 2023
31 points (94.3% liked)

Programming

17334 readers
319 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
31
What search engine can find this line of code on Github? (lemmy.world)
submitted 11 months ago by sparr@lemmy.world to c/programming@programming.dev
10 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] ruffsl@programming.dev 1 points 11 months ago (1 children)

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:

[โ€“] sparr@lemmy.world 1 points 10 months ago

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.