New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
group search results by source package #1
Comments
|
Just FYI: Complexity-wise, this is ≈ O(full-search), because nearly every file needs to be looked at. In order to implement that feature, an entirely new code path needs to be implemented which uses short-circuits on source package level. Depending on how long such a search query typically takes, it might be necessary to add some user interface to perform a long-running query. That is, the client should have a way to abort the query and see progress nearly as it happens. |
|
I had an idea on how to make “batch” queries work: Each service file should include an instance specifier (e.g. dcs-web@batch0.service) and run the entire stack, but with lower I/O and CPU priority, so that normal queries are not impacted. The user can then reliably cancel queries (by bringing down the stack) and doesn’t impact normal usage. It should be verified that mmaping the same (index) file in two separate processes accesses the same memory in the kernel. |
|
Commit 23da966 lays the foundation for my most recent comment. What still needs to be done is build a UI around the batch queries. |
|
With the launch of Debian Code Search Instant, this is fixed (too many commits to mention them all in this issue). |
seems I found the bug tracker for codesearch :-)
codesearch is already awesome, what would make it even more awesome to do archive wide greps and mass bug filings, is the ability to group the search results by source package and only show a summary per source package which can be expanded via a +
The text was updated successfully, but these errors were encountered: