-
Notifications
You must be signed in to change notification settings - Fork 117
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
Refactor WatchResourcesClient
response handler
#5572
Merged
ericpgreen2
merged 15 commits into
main
from
refactor-watch-resources-client-response-handler
Sep 12, 2024
Merged
Refactor WatchResourcesClient
response handler
#5572
ericpgreen2
merged 15 commits into
main
from
refactor-watch-resources-client-response-handler
Sep 12, 2024
Conversation
This file contains 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
nishantmonu51
added
the
blocker
A release blocker issue that should be resolved before a new release
label
Sep 3, 2024
AdityaHegde
requested changes
Sep 4, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are refetching profiling queries for sources and models once when the reconcile starts and once when it ends. I didnt check a lot of edge cases, with the simplification I feel we will miss quite a few of those.
web-common/src/features/entity-management/WatchResourcesClient.ts
Outdated
Show resolved
Hide resolved
web-common/src/features/entity-management/WatchResourcesClient.ts
Outdated
Show resolved
Hide resolved
AdityaHegde
approved these changes
Sep 12, 2024
ericpgreen2
deleted the
refactor-watch-resources-client-response-handler
branch
September 12, 2024 15:15
ericpgreen2
added a commit
that referenced
this pull request
Sep 12, 2024
* Refactor `WatchResourcesClient` response handler * Match instance query key w/ invalidated query key * Refetch rather than invalidate * Clarify log during e2e test * Remove redundant `fileArtifact.softDeleteResource()` * Remove console log * Remove old code * Use `meta.stateVersion` to avoid excessive invalidations * Readability * Whoops – add back `stateVersion` check * Only invalidate `OLAPListTables` when the `resultTable` has changed * Remove duplicate state that we can get from the `previousResource` * Account for Sources too * Nit
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR cleans-up the
WatchResources
response handler, including:stateVersion
changesDELETE
eventDELETE
rather than a soft deleteCloses #5480, https://github.com/rilldata/rill-private-issues/issues/591, https://github.com/rilldata/rill-private-issues/issues/628
Relevant Slack convo