You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 11, 2023. It is now read-only.
When the tweet processing function encounters a non internal error, such as a database error, the stream halts without any information given. This is probably due to the default error handling strategy of Akka Streams, which stops the entire stream when an error is encountered, as described at https://doc.akka.io/docs/akka/current/scala/stream/stream-error.html. It should be possible to configure twitter4s with a different error handling strategy, or clarify if this is outside the scope of the library, and should be handled by dispatching the tweets to a different system/stream.
The text was updated successfully, but these errors were encountered:
When the tweet processing function encounters a non internal error, such as a database error, the stream halts without any information given. This is probably due to the default error handling strategy of Akka Streams, which stops the entire stream when an error is encountered, as described at https://doc.akka.io/docs/akka/current/scala/stream/stream-error.html. It should be possible to configure twitter4s with a different error handling strategy, or clarify if this is outside the scope of the library, and should be handled by dispatching the tweets to a different system/stream.
The text was updated successfully, but these errors were encountered: