alpha
Login
or
Join now
boltless.me
/
zoekt
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
fork of https://github.com/sourcegraph/zoekt
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
Pulls
Pipelines
zoekt
/
testdata
/
at
db067d1294f3ac13d77c19c8259baa3a8c6c1b6a
6 folders
2 files
Geoffrey Gilmore
grpc: RepoList: actually persist "repos" field when converting to protobuf message (#644)
2y ago
2d1affd4
backcompat
grpc: RepoList: actually persist "repos" field when converting to protobuf message (#644)
2 years ago
fuzz
grpc: RepoList: actually persist "repos" field when converting to protobuf message (#644)
2 years ago
golden
scoring: score files based on absolute number of atoms (#542) This changes how atom-score is calculated to better reflect the complexity of the result or the user's intent. Currently, the atom-score is the ratio "atomMatchCount/totalAtomAcount". However, "totalAtomAcount" is based on the pruned match-tree which may be very different from the user query. For example, a match-tree for the query "foo or bar" is pruned to (a matchtree representing the query) "foo" if the shard doesn't contain the trigram "bar". In an extreme case, a query like "foo or bar or bas or qux" can receive the maximum atom-score if a repo just contains matches for foo. Assuming that the score of a match should reflect how close a match is to the user's intent, we should rather base the atom-score on the original unpruned match-tree. However, the original match-tree is already based on a simplified query, (see "d.simplify(q)" in eval.go) Hence I change the scoring function for atom-score to be based on the absolute count and to assymptotically approach scoreFactorAtomMatch. This also makes the score more comparable across shards.
3 years ago
repo
Add small test for v15 backwards compatibility (#23) * add test for backwards compatibility for v15 * update version * WIP use smaller index Change-Id: Id28f9477a400b7d5649bbc0e8a4d567813792fae * reduce test index + use golden file * cleanup * update test
6 years ago
repo2
merging: support exploding compound shards (#271) This change let's us split a compound shard into its constituent repos. In the future this should happen instead of deleting too small compound shards. Fow now, the feature is behind a feature flag. To activate, place a file EXPLODE in the index dir.
4 years ago
shards
ranking: add document ranks to shards (#449) We persist document ranks in the shards and sort file matches based on the rankings determined by the document ranks and match scores. Co-authored-by: Keegan Carruthers-Smith <keegan.csmith@gmail.com>
3 years ago
gen-shards.sh
ci: add shellcheck step (#316)
4 years ago
search_result_1.pb
Add a gRPC API (#577) This adds a gRPC API alongside the existing gob API. It is enabled whenever the RPC setting is enabled. I didn't think it made sense to have a separate setting to enable it. It is only used when a gRPC request is detected (Content-Type: application/grpc). Eventually, we should likely open a separate port for gRPC traffic, but this should be okay for now. In order to minimize the footprint of this change, we only use the protobuf definitions in the RPC layer. They are translated to/from the existing go types. This results in a small perf penalty.
3 years ago