Silently stopped real-time filter
See original GitHub issueHi,
I try to collect tweets over a month regarding the covid-19 outbreak with the following command.
twarc filter 'covid19' > tweets.jsonl
Twice the command silently stopped after ±2hours of collecting without anything in the log file.
What could be the reason and more important how could the error be logged?
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Filter function silently fails - Power Platform Community
No Errors it just won't Filter the datasource any more. These tenants are not connected to the same sources, completely separate. Labels:.
Read more >Aquarium Filter Not Working: Common Reasons and How to ...
Most fish tank filters will make some sound, even those that claim to be completely silent, but it's usually just a gentle hum....
Read more >FFmpeg Filters Documentation
Unused delays will be silently ignored. If number of given delays is smaller than number of channels all remaining channels will not be...
Read more >Event filters reference - Sensu Docs
If the filters do not remove the event, the handler will be executed. The event filter analysis performs these steps: When the Sensu...
Read more >Filter emails in Mail on iPhone - Apple Support
In Mail on iPhone, use filters to temporarily show only certain messages, like Unread. Also specify which email accounts are visible in Mail...
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 FreeTop 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
Top GitHub Comments
A fix for this (adding a log message when terminated) was just released as part of v1.8.2. Thanks for taking the time to file the issue ticket!
@mielverkerken great, I’m glad we figured it out. Let’s leave this issue open because I like your idea of logging when this happens, if possible.