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
Migrate to per-repo storage scheme
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
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
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
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, …
Various fixes and improvements to the Demo
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+ …
Demo: change closed issue/PR color to github's
Enable all full-text search operators
Enable all full-text search operators
Enable operators for keyword search and disable query sanitizer
Enable all full-text search operators
Enable all full-text search operators
Add license and related fixes and improvements
Prevent 100k+ repos to be added
est::size_S
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
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 …
Change internal architecture of storing data
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.
Change internal architecture of storing data
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 …
Change internal architecture of storing data
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 …
Change internal architecture of storing data
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 …
Long query leads to "Something went wrong"
Search across all organization's repositories
Change internal architecture of storing data
Long query leads to "Something went wrong"