Honza Dvorsky
Honza Dvorsky
If (1) would address your needs, I agree it's likely the right one to go for. We attempted and ultimately rejected a "mapper" approach earlier this year (https://github.com/apple/swift-openapi-runtime/pull/141/files), but I...
In unit tests, it'll be important to show that the callback sees errors from all these locations: 1. transport 2. middleware 3. encoding of request 4. decoding of response
I'm a bit iffy on not calling the user-provided closure. The doc comment on the method doesn't mention that it wouldn't be called under some circumstances and it can break...
This is great, thanks @slashmo! Let's use this issue to track adding much of your explanation into the docs.
@FranzBusch I'll wait with this PR until https://github.com/swift-server/swift-service-lifecycle/pull/215 lands, as I'll copy the approach to signal handling on Windows over to Wasm too
Hey @phausler, is this an algorithm that you'd accept here? If so I can write up a proposal
Transfered over to the right repo. cc @guoye-zhang @simonjbeaumont
Did you check with .debug logging? IIRC SSL actually does produce pretty detailed logs, as long as you bump your logger's log level.
Asking each library in the ecosystem to allow customizing the level at which it emits logging is one way, but I believe that Swift Log already has a solution for...
Separately, if there are events that aren't logged today that you need, those can certainly be added, but still at the debug/trace level, and you can escalate them in your...