#community-help

Bug Discovery and Resolution in Collection Admin Panel

TLDR Bruno reported a bug regarding the collection admin panel and posted it on GitHub. Jason replicated the issue and determined it was due to duplicated keys in a collection. Bruno agreed to delete the problematic collections.

30mo

Join the chat

Aug 05, 2021 (30 months ago)

Photo of md5-0ca37054c6c9042aa04fcfb92cc7d99c

Bruno

11:01 PM

I think I found a bug with the collection admin panel, report it here or on GitHub? Might be related to our specific dataset.

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

11:02 PM

Github issue would be great

Bruno

11:13 PM

Ok, done: https://github.com/typesense/typesense/issues/335

Jason

11:17 PM

Hmmmm, it seems to work for me

11:18

Jason

11:18 PM

Do you by any chance block Rollbar from loading, via a browser extension or at the network level?

Bruno

11:22 PM

I don't think so, but opening the first collection works for me. I can try more browsers.

11:24

Bruno

11:24 PM

Tried Firefox, same behavior. Only works for the results_normalizedcollection. Trying Safari on an iPad next.

11:29

Bruno

11:29 PM

Reproduced the issue on Safari on the iPad. Also connected it through a phone's 4G via hotspot, so another network.

Jason

11:31 PM

Hmm, I wonder if it has something to do with the dataset / schema that might be triggering this. Would you be ok if I accessed your cluster data to debug this further?

(We don't access customer data as a matter of standard policy, unless explicitly granted permission by the user).

If it's ok, could you email [email protected] with your cluster ID, authorizing access?

Bruno

11:32 PM

Sure, go ahead, you already have written permission, unless you need a separate e-mail per bug for legal reasons.

Jason

11:33 PM

Oh we do? Sorry if I might have forgotten. Let me look real quick

Bruno

11:33 PM

No worries, I'm not enough of a big deal to expect to be remembered 🙂

Jason

11:34 PM

My bad! :hugging_face:

11:35

Jason

11:35 PM

This is probably terrible, but since I have many conversations during the day, I remember use cases more than names! I definitely remember discussing your use case over email!

11:35

Jason

11:35 PM

Taking a look now...

11:38

Jason

11:38 PM

Yaaay, I was able to replicate it now! Digging deeper

Bruno

11:40 PM

I actually have an idea about what could be causing this. There's still that results_test_duplicate_fields set that has the duplicate (triplicate?) creation_date from the duplicate fields bug report. Maybe these things are connected.

Jason

11:49 PM

Yup! That's exactly what's causing this

11:50

Jason

11:50 PM

Wasn't planning for keys to be duplicated in a collection, so the Vue :key is duplicated

Bruno

11:50 PM

I also detected that I mistakenly added another duplicate field, which is a facet. I was about to report a bug with groupBy "eating" results, and it's likely that this is related.

11:51

Bruno

11:51 PM

If it's OK with you, I'll go ahead and delete the problem collections?

Jason

11:51 PM

Yup :thumbsup:

Bruno

11:52 PM

Sorry for being such a troublemaker, but I am known for being somewhat of a natural-born corner case finder

Jason

11:52 PM

Hahaha, not a problem at all! In fact thank you for finding all these interesting bugs 😄

Bruno

11:53 PM

If the groupBybug turns out to be real, you won't be too happy 🙂

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3005 threads (79% resolved)

Join Our Community

Similar Threads

Slow, High CPU Write Operations After Collection Drop in Typesense

Himank discussed an issue in Typesense where deleting and recreating a collection led to slow write operations and high CPU usage. Kishore Nallan suggested using an alias to avoid this issue. Numerous tests and debugging was conducted as pboros contributed with local testing. Kishore Nallan aimed to start implementing a range delete and full db compaction after deletion to potentially solve the issue.

232

17mo

Crash and Recovery Issues with Node Reindexing

Greg encountered issues with node health during reindexing, with service unresponsive and recovery taking significant time. Jason and Kishore Nallan suggested it might be a case of high volume writes and not a crash. Problem wasn't fully resolved after attempted solutions and data sharing for further debugging.

yesterday

Threading Problem During Multiple Collection Creation and Batch Insertion in Typesense

Johan has a problem with creating multiple collections and batch-inserting documents into Typesense, which is returning results from different collections. Kishore Nallan helps troubleshoot the issue and suggests a potential local race condition, which is fixed in a later build.

17mo

Duplicate Field Issue in Schema Creation

gab faced an issue with duplicated fields in their schema. When examined by Kishore Nallan, they found that gab may have accidentally created the duplicates due to wildcard field naming. The potential bug was identified and resolved.

26mo

Phrase Search Relevancy and Weights Fix

Jan reported an issue with phrase search relevancy using Typesense Instantsearch Adapter. The problem occurred when searching phrases with double quotes. The team identified the issue to be related to weights and implemented a fix, improving the search results.

111

8mo