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
fix (types): this
is FastifyInstance
#3622
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add an unit test for this changes? Not compulsory, but better to prevent the this
problem in future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you please add an assertion so we don't regress?
Yeah I will be home in maybe 10/15 minutes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@climba03003 could you take a final look? I plan to ship this tomorrow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
CI fails on what appears to be an unrelated flacky test :d Hmmm, ok at least 2 flacky tests spotted:
- t.test('preHandler hook in setNotFoundHandler should be called when callNotFound', t => {
+ t.test('preHandler hook in setNotFoundHandler should be called when callNotFound', { timeout: 40000 }, t => {
|
CI is all green on my branch 😠 https://github.com/darkgl0w/fastify/actions/runs/1704685094 I will open a new PR when I figure out how to fix the flacky test in the |
Could you please open a couple of issues? |
@mcollina > sure, the fix for the 404 test randomly timing out is included in this PR (I tried to reproduce it with the fix and it seems to be gone now) And for the last one randomly returning a 503 HTTP Status I think I've got a fix. Currently running the test suite on a little Banana Pi to see if it works as it should ^^ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hello.
This PR aims to :
this
toFastifyInstance
(fix A change in Fastify hook types broke our hooks #3620)404s.test.js
test randomly timing outChecklist
npm run test
andnpm run benchmark
and/or benchmarksare includedand the Code of conduct