Skip to content
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

HTTP server errors not surfaced #212

Closed
gillesdemey opened this issue Sep 12, 2017 · 3 comments
Closed

HTTP server errors not surfaced #212

gillesdemey opened this issue Sep 12, 2017 · 3 comments

Comments

@gillesdemey
Copy link
Contributor

Errors emitted by the HTTP server aren't passed to the listen callback, I understand that you can access the server property but surely we can do better here? :)

'use strict'

const fastify = require('fastify')

const s1 = fastify()
const s2 = fastify()

s1.listen(3000)

s2.listen(3000, err => {
  console.error(err) // no exception
})

s2.server.on('error', err => {
  console.error(err) // listen EADDRINUSE :::3000
})
@mcollina
Copy link
Member

Errors emitted by the HTTP server aren't passed to the listen callback, I understand that you can access the server property but surely we can do better here? :)

Surely you can send a pull request, this is OSS.

Joke aside, #215 fixes it.

@gillesdemey
Copy link
Contributor Author

Surely you can send a pull request, this is OSS.

Sorry, I thought I'd open a ticket first as a courtesy :) I'll be sure to send in a PR next time! 🙏

@delvedor
Copy link
Member

I think @mcollina was not saying that you should fire a pr instead of an issue, he was just pointing out the tone of your issue :)

property but surely we can do better here? :)

I know it is not intended, but it sounds like an order ;)
Have a nice day!

haggholm pushed a commit to haggholm/fastify that referenced this issue Jun 12, 2021
add support for exploding querystring parameter
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants