Mahdi Bahrami

this last commit was stuck in Github client again due to the branch renaming i did. just adds the serverName back to the resolved connections.

I came across this issue when i was looking at [one of the boards](https://github.com/orgs/vapor/projects/10). I could not reproduce this issue. What the issue expects is if you run this [existing...

@BennyDeBock I'll be happy to have a reproducible example on my hands but to me seems that what @jareyesda is correct. There is an explicit line in the decoder to...

hmmm, i understand what you are talking about. BUT First: For clarity, this PR includes doesn't include real breaking changes syntax-wise. You can still do `app.queues.shchedule(JOB()).at(Date())` and similar stuff, and...

You both are not wrong, again. What i'm trying to say is that this is worth it although there is a 1/100 chance that this might be breaking. I checked...

So lesson 1 learned ✅: No breaking API changes in minor versions! About releasing a major version, i think we'll need to know what @jdmcd thinks. I personally have no...

I take this PR back 😅 The problem came from the fact that I thought Vapor automatically bootstraps the logging system on Application init and doesn't let you stop it...

Just want to give an update about the original issue (#488) after ~ a year and a half. The update is ... Since yesterday I've enabled back http2 requests and...

This probably shouldn't stay opened. It's breaking and if we were to publish a new major version, we can do better than this.

You might be bumping into some buffering problems. Try `fflush(stdout)` right after your `print()`.