Complete callback does not fire when Step and Preview used together
See original GitHub issueSo, I don’t think this actually a bug, just potentially confusing, although I was ultimately able to make sense out of it:
If you pass both preview
and step
options and your data source has more than preview
rows, then the complete
callback never fires. Although, it just so happens that if your data source has the same number of rows as preview
, then the complete
callback fires even if you have also defined a step
callback. I haven’t tested if complete
also fires in these circumstances if the data source as fewer than preview
rows, but you get the picture.
Again, not exactly a bug, but I wanted to drop a note here.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Advanced Callbacks | Dash for Python Documentation | Plotly
If it is running in a multi-threaded environment, then all of the callbacks can be executed simultaneously, and they will return values based...
Read more >Handle events - Unity - Manual
Respond to events with custom controls · Callbacks must register on instances of the class. · Callbacks execute for all visual elements in...
Read more >How to make one Observable sequence wait for another to ...
Now, I want to subscribe() to two , but I want to make sure that one has completed before the two subscriber is...
Read more >Call, trigger, or nest logic apps by using Request triggers
If you don't have a subscription, sign up for a free Azure account. ... callback URL that other services can use to call...
Read more >Consent configuration - Tag Manager Help - Google Support
Google Tag Manager includes several features that work together to help you ... The Consent Initialization trigger is not used for tags that...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This also happens when using in Node with the Papa.NODE_STREAM_INPUT to parse a stream with the preview configuration option. Spent a few hours trying to figure out what I did wrong before I realized that the Papa.parse stream never fires the end event if the preview rows are all received before the source stream is completely processed.
If avoiding changes to the current behavior is important it may work to either add a new event (maybe finish or done or something like that) to indicate that Papa.parse is doing no further parsing, or perhaps to fire an end event when the underlying stream that is being piped to Papa.parse fires its own end event.
I’d be interested in a clean solution for this one.