Filter by reset
- Everywhere
85 - Issues
23 - Pull Requests
18 - Comments
44
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
Migrate to per-repo storage scheme
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
Enable all full-text search operators
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 operators for keyword search and disable query sanitizer
Add license and related fixes and improvements
Enable all full-text search operators
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
Enable all full-text search operators
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 …
Enable all full-text search operators
Search across all organization's repositories
Change internal architecture of storing data
Change internal architecture of storing data
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.
Change internal architecture of storing data
Update to separate table per organization schema
Change internal architecture of storing data
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 …
Change internal architecture of storing data
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
Implement the query suggestion logic
Update README with clear instruction of how to deploy
Implement the query suggestion logic
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.
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 …
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