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
/
internal
/
at
626c7d8f51ca1c7c4973b62d2cf9467c5ab910de
4 folders
Keegan Carruthers-Smith
introduce DisplayTruncator (#630)
2y ago
626c7d8f
mockSearcher
introduce DisplayTruncator (#630) This moves all decisions about if we should do display limits and how to enforce them into one place. By default we make it stateful so it can be used by the limitSender. But in every other place we will always sort and then truncate, so we also introduce a convenience API for that. The only potential behaviour change here is if you have no display limits but had document ranks turned on, we would not sort matches within a shard. However, the aggregator would still do sorting anyways so this is really just a wasted sort. In practice a display limit should always be set. Test Plan: go test
2 years ago
otlpenv
Support building Zoekt with Bazel (#573)
3 years ago
profiler
Support building Zoekt with Bazel (#573)
3 years ago
tracer
introduce DisplayTruncator (#630) This moves all decisions about if we should do display limits and how to enforce them into one place. By default we make it stateful so it can be used by the limitSender. But in every other place we will always sort and then truncate, so we also introduce a convenience API for that. The only potential behaviour change here is if you have no display limits but had document ranks turned on, we would not sort matches within a shard. However, the aggregator would still do sorting anyways so this is really just a wasted sort. In practice a display limit should always be set. Test Plan: go test
2 years ago