Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix entity selector #16306

Conversation

AdrienClairembault
Copy link
Contributor

The entity selector is never updated, meaning any new entities will never be visible.

This is caused by #15794, which did not take cache invalidation into account.

I've fixed this by adding a hash of every entities last update date into the selector.
This hash will change any time an entity is created, updated or deleted from the database.

I've also deleted references to the old cache key since it is not used anymore after #15794.

Q A
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets !31070

@orthagh
Copy link
Contributor

orthagh commented Jan 4, 2024

#16249 ?

@cconard96
Copy link
Contributor

Is this meant as a replacement for #16249?

@AdrienClairembault
Copy link
Contributor Author

My bad, I didn't know it was already solved by #16249.

@AdrienClairembault
Copy link
Contributor Author

AdrienClairembault commented Jan 4, 2024

I have no idea which approach is better, guess we can let @cedric-anne look into it when he comes back.

Probably a mix of both approach would be best as I understand that you implements additional improvements (like profiler support) while this PR add some tests which are probably needed on this feature.

@AdrienClairembault
Copy link
Contributor Author

Also, a third solution would be to revert #15794 and work on this on the main branch instead to avoid futures issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants