[HUMAN App] fix: remove unnecessary query invalidation - #3484
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
4 Skipped Deployments
|
dnechay
marked this pull request as draft
July 30, 2025 15:09
dnechay
force-pushed
the
dnechay/fix-ha-queries
branch
from
July 30, 2025 16:19
ea7e81c to
fe9e825
Compare
dnechay
force-pushed
the
dnechay/fix-ha-queries
branch
from
July 30, 2025 19:52
2a9749a to
fa5079f
Compare
dnechay
marked this pull request as ready for review
July 30, 2025 20:03
KirillKirill
approved these changes
Jul 31, 2025
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue tracking
Fresstyle
Context behind the change
Mutations are being blocked in "pending" state because of waiting for
invalidateQueriesfor long-running queries (governance logs in our case). Removing it to avoid lags.How has this been tested?
Release plan
Just merge
Potential risks; What to monitor; Rollback plan
Should be safe since we don't use caching on client anyways.