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
0.23 -> main #6551
0.23 -> main #6551
Conversation
Each method takes a FrameTranscoder as parameter, but it is always the non-client one, so we can extract it as a constant.
EncodeFrames was just a pipe to do a flatMap. We extract the function of flatMap as `encodeFrame`. We also replace some calls to `through(encodeFrames)` with a flatMap call.
We replace the `through handleIncomingFrames` parts with just calls to `.evalMapFilter`. We extract from `handleIncomingFrames` the inner function to optional.
It could be to Option, but somehow Option is not Seq.
Before commit, `encodeFrame` takes a frame and generate a stream of bytes, which is then immediately processed chunk by chunk. Instead, we can by-pass the stream phase, leave the chunks in a list, and use a `traverse_`.
…touches Ember-Server: WebSocketHelper rewrite / optimisation
fix typo in `Throttle` middleware `httpAapp->httpApp`
…-minimal-en_us-db-1.4.1 Update locales-minimal-en_us-db to 1.4.1 in series/0.23
…fect-3.3.13 Update cats-effect, cats-effect-std, ... to 3.3.13 in series/0.23
…e-3.2.9 Update fs2-core, fs2-io to 3.2.9 in series/0.23
Create `.git-blame-ignore-revs`
Custom branch for update flake action
Update sbt to 1.7.1 in series/0.23
…uffer-4.1.79.Final Update netty-buffer, netty-codec-http to 4.1.79.Final in series/0.23
Completely my bad, the changes in http4s#6498 needed the action to be updated to latest 😅
…fect-3.3.14 Update cats-effect, cats-effect-std, ... to 3.3.14 in series/0.23
…s-core-2.4.0 Update log4cats-core, log4cats-noop, ... to 2.4.0 in series/0.23
Update to update-flake-lock v10
Add Hireproof to adopters
Executed command: sbt tlPrePrBotHook
…p4s-org-0.14.4 Update sbt-http4s-org to 0.14.4 in series/0.23
Flake lock file updates: • Updated input 'typelevel-nix': 'github:rossabaker/typelevel-nix/a183dd87238be83478fdca8a35b05dbcf57e96f8' (2022-07-04) → 'github:rossabaker/typelevel-nix/2d2b118d056b851dea9ccb0775ddd5ce8a1dbd79' (2022-07-18) • Updated input 'typelevel-nix/flake-utils': 'github:numtide/flake-utils/bee6a7250dd1b01844a2de7e02e4df7d8a0a206c' (2022-06-24) → 'github:numtide/flake-utils/7e2a3b3dfd9af950a856d66b0a7d01e3c18aa249' (2022-07-04) • Updated input 'typelevel-nix/nixpkgs': 'github:nixos/nixpkgs/660ac43ff9ab1f12e28bfb31d4719795777fe152' (2022-07-02) → 'github:nixos/nixpkgs/78e748fa68079b77ac055c80ef21342dd7e2ae2b' (2022-07-17)
flake.lock: Update
Remove references to `HttpService` in `testing.md`
@@ -129,9 +129,14 @@ object Throttle { | |||
Throttle.httpRoutes(bucket, defaultResponse[F] _)(httpRoutes) | |||
) | |||
|
|||
@deprecated("Use httpApp instead.", "0.23.14") | |||
def httpAapp[F[_]](amount: Int, per: FiniteDuration)(httpApp: HttpApp[F])(implicit |
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.
I think we can remove this
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.
Maybe we should give once cycle of deprecation, to help migration?
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.
🤷🏻 Can't suggest how many users might be affected by just removing this, but this was introduced weeks ago
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.
Oh, I didn't realize it was so recent. I guess it was in M33 and M34.
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.
I don't mind if we release this with deprecation and then remove it. Just we definitely have to remove it for 1.0 :)
No conflicts.