Filter by reset
- Everywhere
85 - Issues
23 - Pull Requests
18 - Comments
44
Prevent 100k+ repos to be added
Since we aim for this GitHub issue search to be a demo project, there may be issues with big repositories due to indexing that takes a long time and consumes a lot of memory. To be fair and make it best suited as a demo project, we should set limits and …
est::size_S
Implement the query suggestion logic
We should design and display query suggestions in the same way Google does, and use the latest code from Buddy to accomplish this. The user input should bounce with a slight delay, and with almost every keystroke, we should render and display a popup …
We need to consider and implement a way to configure and toggle fuzzy search options in the user interface. We should be able to: Turn fuzzy search on or off Enable or disable different keyboard layouts Potentially adjust other fuzziness settings
We should consider adding logic that will allow us to find similar issues/comments in the same way we do in our Image demo.
est::size_M
We should add the latest update from Buddy to work with the Manticore GitHub demo. This will allow us to validate its quality on a large dataset and assess how fast it is. The purpose of this integration is to use the latest version of Buddy and make …
Consider enabling bigram_index to improve autocomplete
…Here The autocomplete results could be better if they included native support . It's currently impossible likely because bigram_index is not enabled. If we do it, the results may be better. E.g.: mysql> drop table if exists t; create table t(f text) min_ …
size_S
Experiment with distributed table
Try to use a distributed table with issue and comment tables in it and CALL AUTOCOMPLETE on it to validate whether it works as expected or not.
Empty list when adding a repository to the github demo
We should investigate why the list is empty on production servers but works correctly in the local environment.
Change internal architecture of storing data
We should migrate to a system where we store each organization in a separate table. This approach will allow us to maintain the logic for searching one, two, or multiple repositories within a single organization. It will also help us narrow down query …
After a crash or some kill -9 on the daemon, we noticed an issue with the indexers. They enter a state where they are "forever indexing," which leads to interface problems and a progress bar that never disappears. We should investigate and fix this issue, …
Long query leads to "Something went wrong"
When we input a very long query and use Fuzzy matching, we are experiencing a "Something went wrong" error. We should investigate this issue. An example of this is: https://github.manticoresearch.com/manticoresoftware/manticoresearch?query=after+daemon+ …
Enable all full-text search operators
Migrate to per-repo storage scheme
As we discussed here we should try to migrate to table-per-repo scheme: https://github.com/manticoresoftware/manticore-github-issue-search/issues/25#issuecomment-2249352562 To do so we should first implement the logic that will help us dirrectly query the …
We need to address the following issues: Add the missing license Investigate indexer issues as something is malfunctioning Optimize frontend performance by implementing lazy loading for images Add multiple repo links on the main page after search input
Notifications are not beeing send
We should check the cause of the issue when we are not receiving email notifications about indexation being done anymore.
bugsize_S
Possibility to search across all repositories of the organization
We need to add the ability to search across all the organization's repositories. This shouldn't trigger a reindexing of all repos, but it should enable searching through all the organization's data. We'll need to modify the structure to make this happen …
Let's add vector search to the demo using one of the most popular models. Implement the tokenizers Rust extension. Pick the best starting model. Add logic to handle various models and the option to adjust them at the start.
Various fixes and improvements to the Demo
improve exceptions handling, especially the exception which is thrown when the token has exceeded its limit experiment more with the facets UI to make it less confusing (grey out filters that would result in zero results etc.) deploy a new version of the …
We should move forward with enhancing the query suggestions panel and make it respond to the up and down arrow keys just like Google does. When users press the up or down arrows, it should set a new phrase in the input field and also change the focus …
Combine comment and issue in query suggestions
Currently, we only use issue responses to generate query suggestions when a user is typing. We should expand this approach by also checking comments and using an RPB-like algorithm to merge the results, returning a combined array. Additionally, to support …