Simon Leeb

just got the same/similar error with the friendly hint to report it: ``` NIO-ELT-0-#0 (7): Fatal error: leaking promise created at (file: "BUG in SwiftNIO (please report), unleakable promise leaked.",...

> For all... probably 0 people running Nimble on a raspberry pi. just FYI, the same issues occur when building on an Apple Silicon mac. so, anyone doing server-side swift...

> In the short term, we should fix the error message and tell users that they've shut down the ELG, right? Clearly not unleakeable ;) Still wrapping my head around...

> There is some existing support as part of parameters At least on the server side I could not find a way to access cookie parameters in the generated request...

Here is the OpenApi snippet of the route I was referring to (I am setting the cookie in a /login route) ``` /refresh-token: post: operationId: refreshToken description: Returns a new...

The `/login` just takes user/password (and station, application specific stuff) as a payload. It returns a short-lived token (for API access) and a `Set-Cookie: refershtoken=xxx` for renewal (refreshToken with longer...

At the moment the `refreshtoken` is only issued on `/login` - when it expires, a password is needed. So `/refresh-token` will not set a new one.

About the "escape hatch", I am currently playing around with this: ``` /// Extensions to work around current limitiation on OpenAPI generator enum RawRequest { @TaskLocal static var current: OpenAPIRuntime.Request?...

since I just stumbled over the issue of "setting cookies" via a Set-Cookie header, I want to add that a "cookie parameter" feature should also include a proper way for...

in case somebody is interested, I hacked together this workaround for my use case for now: ```swift /// Provides Response.setCookies and attaches all added cookies to the response header public...