Filter by reset
- Everywhere
79 - Issues
22 - Pull Requests
17 - Comments
40
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
Long query leads to "Something went wrong"
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
Long query leads to "Something went wrong"
Long query leads to "Something went wrong"
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 …
Long query leads to "Something went wrong"
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
Long query leads to "Something went wrong"
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 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 …
Show comments on state filter change for those issue state only (JOIN in the demo)
When we work with filters and search, we can currently filter by the state that only issues and pull requests have. However, when we change the state to open or close, we still search for comments everywhere. As discussed before, it would be a good idea …
size_S
Replace "Vector search" with "Semantic search" in the demo
Rename 'Vector Search' to 'Semantic Search'. Prepare and upload a new database dump containing only vector embeddings for our repositories. This will make it lighter and easier to get started.
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
Various fixes and improvements to the Demo
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.
Demo: change closed issue/PR color to github's
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.
Update to separate table per organization schema
Prevent 100k+ repos to be added
est::size_S
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 …
Empty list when adding a repository to the github demo
Implement auto disabling of filters that have no data when we change the query for the current search.
Notifications are not beeing send
bugsize_S
Demo: change closed issue/PR color to github's
Change internal architecture of storing data
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+ …
Change internal architecture of storing data
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 …
Change internal architecture of storing data