Missing results with typesense

Bug
1

Hi together,

i have installed vikunja and typesense via docker today its working in general.
But if i enable the typesense-connection it only finds parts…
If i disable typesense and use the general db-search everything can be found.

I was searching in the logs of vikunja and typesense but i cant find any problem…

Does anyone have same problems?

Many thanks

2

Which version are you using?

3

Its vikunja/vikunja:0.24.2 (because of the Preview-Bug in the actual version) and typesense/typesense:27.0

4

There have been a bunch of fixes for this in 0.24.3. Please check if the issue persists with that.

5

I have tested it and its the same.

Ich can go to a task and write a word in the description and searching for it gives no result…
But searching for other things are working somehow.

Reindex dont change that

6

Does it only do that with the description? Can you reproduce it reliably? Did you do a full reindex after switching Vikunja versions?

7

I will Test this in detail as i have tested it with the description only… and yes i can reproduce it without problem. Type somewhat in the description, do a search… nothing… do vikunja index… search… nothing… disable typesense… search… hey here is it.

I did “vikunja index” as i startet to use typesense… then i saw the Problem and was playing around every time with the same command.

But as it happens with New entries too i think there shouldnd be a index nessesary as it is for “old” entries?

8

I was unable to reproduce this in the latest release (0.24.4) with these steps:

  1. Enable Typesense
  2. Run vikunja index
  3. Update the description of a task
  4. Search for parts of the updated description using the global search (ctrl k)
  5. Find the task I just updated

Seems to work fine with new tasks as well.

Can you reproduce it using these steps?

After enabling Typesense you need to index all tasks once, every change after that is updated automatically.

1 Like
9

Hi kolaente,

i have done like you said and the problem is still there.
But i have found out, that the problematic words are in the second, third… line of the description.
Words in the first line i can find.

Thats reproduceable here… every word i put in the first line of the description is found by typesense. Every word i put in other lines not.

1 Like
10

This sounds like a new bug. I’ll take a look.

11

This fixed an issue I was about to post about related to Kanbans. Thank you.

12

@oskharrr I’m unable to reproduce this with the latest unstable build. Are you able to?

13

How do i have do install this?

Im on image: vikunja/vikunja:0.24.4 in my docker-compose…

vikunja/vikunja:unstable gives me an older version so it looks wroong. :thinking:

14

Which version do you get from the unstable image? The important part is the commit hash, not the version number.

15

Sorry for the long delay.
It gives me Version: v0.24.1-313-3e9c41cfc6

I have tested it and it looks like it works!