fix(app): Fix accidental polling when a query is initially disabled #17853
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.
Overview
While testing EXEC-1342, we noticed a bug in our notifications machinery that would cause the app to poll even when MQTT was available and it shouldn't have to.
Details
Specifically, the bug would happen for queries that started off with
options
of{enabled: false}
and became{enabled: true}
later on. Here is the motivating example.The
useNotifyDataReady
hook had a piece of state,isNotifyEnabled
, that would accidentally permanently latch tofalse
whenever the hook saw{enabled: false}
.Test Plan and Hands on Testing
Tested as part of #17832 by monitoring the network logs.
Review requests
Makes sense? Names good?
Risk assessment
Medium. This is common code for a lot of stuff, and it's hard to test.