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

Do not crash if nested plugin does not call next #252

Merged
merged 2 commits into from
Apr 19, 2024

Conversation

mcollina
Copy link
Member

@mcollina mcollina commented Apr 19, 2024

Fixes fastify/fastify#5410

Checklist

Copy link
Member

@gurgunday gurgunday left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Copy link
Contributor

@Uzlopak Uzlopak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense

app.ready((err) => {
t.ok(err)
t.equal(err.fn, one)
t.equal(err.message, message('one')) // TODO: should be 'two'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So this means we should in the future be able to show that two failed right?

Signed-off-by: Matteo Collina <[email protected]>
@mcollina
Copy link
Member Author

@gurgunday @ivan-tymoshenko PTAL. I fixed the error message too.

@mcollina mcollina merged commit c43f269 into master Apr 19, 2024
21 checks passed
@mcollina mcollina deleted the fix-crash-if-nested-plugin-does-not-call-next branch April 19, 2024 09:01
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

Successfully merging this pull request may close these issues.

incorrect plugin identified for timeout
4 participants