Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
This MR fixes a crash in fiftyone's web app that happens when we try to filter the annotations by attributes.
The bug can be reproduced if we load the dataset
lours_test/test_data/caipy_dataset/tags/default_schema
.running

dataset.to_fiftyone()
will work but when we try to filter on attributes in the GUI, we get this error:Here's the same dataset, loaded and correctly filtered after applying the fix:

The error is very deep inside the fiftyone package and I couldn't get a clue from it. Here's the full message if you want to take a shot!
But after experimenting a bit with the attribute columns in libia, I found that the error happens when the name of the attribute column starts with the string "attributes". This could be caused by the fact that fiftyone have something they call attributes but it's only a guess at this point: https://docs.voxel51.com/user_guide/using_datasets.html#dynamic-attributes
To fix the error, I just replaced the string "attributes" with "attr" when exporting to fiftyone (juste like we replace dots with "->" to avoid problems with fiftyone).
I also upgraded fiftyone to 0.25 since we're two versions behind but this has nothing to do with the bug being fixed. The bug is still present in 0.25 if we don't rename "attributes" to 'attr'.
Some docs file have been corrected by pre-commit too.