Resolve fetchNext promise when no data returned - #822
Open
philip-khaisman wants to merge 1 commit into
Open
Conversation
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
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.
NOTE: This will be merged in botts/osh-js not here. Just wanted eyes outside of botts to see it and provide feedback if necessary
I found an issue where if a data source has no data and i try to replay it with other non-empty data sources (with a data synchronizer) no data streams. Maybe im wrong but that doesn't seem like desired behavior. Ive worked with sensors where one of the datastreams is empty for one reason or another.
This happens because in the
DataSynchronizerAlgoReplayclass we gate the streaming of data with this check:if ((nbFetch + nbSkip) === totalDataSources) { start processing data }nbFetchincrements for every data source that has a status ofFETCH_STARTED. The empty data source does not have this status. The status is set in theDelegateReplayHandlerclass in thestartLoop()method:Previously
nextBatch()(defined in theSweApiReplayContextclass) was implemented like this:Note that the condition where
data.length === 0)leaves this promise hanging resulting in theFETCH_STARTEDstatus never being set. By resolving the promise to an empty array this promise allows the logic in thestartLoop()method to continue, setting theFETCH_STARTEDstatus allowing the replay algorithm to process data. I also added an early return in thestartLoop()method since subsequent logic is unnecessary if there is no data returned.Testing: