[BUG-UI/UX] Filtering by vectors

[damianpumar]

Try to find a similar record I get this error.

Screen.Recording.2024-03-13.at.16.27.14.mov

[dosubot]

Hey @damianpumar! Great to see you diving into the depths of Argilla again. Hope you're ready for another adventure in bug squashing! 🐛🔨

Based on the context provided, it seems like you're encountering an issue with the "Filtering by vectors" feature in the Argilla platform. However, without the exact error message, it's difficult to pinpoint the exact problem.

The "Filtering by vectors" feature allows users to filter datasets or records based on specific vector attributes. Each vector is uniquely identified by a combination of vector_name, dataset_id, and record_id, serving as its primary key. Vectors are associated with particular records within datasets, and each vector has a name and a set of values (vector_values). The is_active attribute suggests that vectors can be toggled on or off, possibly affecting their inclusion in filtering operations.

The structure and data type of vector_values in the Vector.js model is an array. This is indicated by the use of this.attr([]) in the model definition, where [] denotes an empty array as the default value.

The data that the "Filtering by vectors" feature is expected to handle includes Vector Settings, Feedback Records, Vector Values, and Operations on Vectors.

There are known issues or bugs related to the "Filtering by vectors" feature in the Argilla platform. Specifically, the test case marked with @pytest.mark.skip highlights a problem related to the order of tests affecting the outcome unexpectedly. The comment within the @pytest.mark.skip decorator mentions, "Review this test since this is the ONLY order where all tests pass. If you change the order, some of those tests will fail with unexpected vector names." This suggests that there is a dependency or side effect between tests that is not intended, which can be considered a bug or issue in the context of software testing and stability of the "Filtering by vectors" feature.

To better assist you, could you please provide more details about the error you're encountering? Specifically, the exact error message and the steps to reproduce the error would be very helpful. This will allow us to understand the issue more clearly and provide a more accurate solution.

For reference, here are the sources I used to gather this information:

• frontend/models/Vector.js
• tests/integration/client/feedback/dataset/remote/test_working_with_vectors.py

Sources

• frontend/models/Vector.js
• tests/integration/client/feedback/dataset/remote/test_working_with_vectors.py

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

[frascuchon]

Thanks @damianpumar!!

I need to do some tests by I think the problem is because this specific record doesn't contain a vector with that name since vector values are optional, even if vector settings are defined.

[damianpumar]

Yes! I understood, but I'm not sure if we should handle it or not, because I don't know if this is a SDK issue or we can handle it in the frontend side.

Thanks!

[nataliaElv]

Proposal for the toast message:

{vector_name} not found for record {id}

[damianpumar]

Final message:
{vector_name} not found for the selected record.