-
Notifications
You must be signed in to change notification settings - Fork 48
Avoid deprecated code (that will be removed in pekko 2.0.0) #803
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
readability import temp compile workaround Update ConnectionTestApp.scala Update ConnectionTestApp.scala
Update HttpServerBluePrint.scala
| Source.actorRef[(HttpRequest, Int)](10000, OverflowStrategy.dropNew).buffer(20000, OverflowStrategy.fail) | ||
| Source.queue[(HttpRequest, Int)](10000) | ||
| .buffer(20000, OverflowStrategy.fail) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a change in behavior (dropNew -> fail)? Seems fine for a test app though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would https://pekko.apache.org/japi/pekko/1.2/org/apache/pekko/stream/OverflowStrategy.html#backpressure() make sense? OverflowStrategy.dropNew is being removed (already deprecated in 1.x).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would https://pekko.apache.org/japi/pekko/1.2/org/apache/pekko/stream/OverflowStrategy.html#backpressure() make sense? OverflowStrategy.dropNew is being removed (already deprecated in 1.x).
TBH I'm not sure what this means in practice here - would that mean 'offer' would give a return value indicating the backpressure? I think fail is probably a fine choice.
splitting out some changes from #779