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

next and 1.x branch is currently failling CI build #1678

Closed
Ethan-Arrowood opened this issue May 29, 2019 · 5 comments
Closed

next and 1.x branch is currently failling CI build #1678

Ethan-Arrowood opened this issue May 29, 2019 · 5 comments
Assignees
Labels
bug Confirmed bug typescript TypeScript related

Comments

@Ethan-Arrowood
Copy link
Member

Ethan-Arrowood commented May 29, 2019

See this manual pipeline execution: https://dev.azure.com/fastify/fastify/_build/results?buildId=1699&view=results

The error is TypeScript related: https://dev.azure.com/fastify/fastify/_build/results?buildId=1699&view=logs&j=bf7c6fb2-34e3-5d65-0f4a-49158f2ba27b&t=3357be4a-1360-5b27-f34e-4cd70356d9a8&l=8278

test/types/index.ts(247,13): error TS2345: Argument of type 'RouteShorthandOptions<Http2Server, Http2ServerRequest, Http2ServerResponse, DefaultQuery, DefaultParams, DefaultHeaders, any>' is not assignable to parameter of type 'RouteShorthandOptions<Http2SecureServer, Http2ServerRequest, Http2ServerResponse, DefaultQuery, DefaultParams, DefaultHeaders, any>'.

Self assigning. Will fix this asap (also investigating stability of 1.x)
Property 'addContext' is missing in type 'Http2Server' but required in type 'Http2SecureServer'.

@Ethan-Arrowood Ethan-Arrowood self-assigned this May 29, 2019
@Ethan-Arrowood Ethan-Arrowood added bug Confirmed bug typescript TypeScript related labels May 29, 2019
@Ethan-Arrowood Ethan-Arrowood changed the title next branch is currently failling next and 1.x branch is currently failling CI build May 30, 2019
@Ethan-Arrowood
Copy link
Member Author

@fastify/core pinging core team to be aware of this. Both errors are the same. Manual CI builds for both 1.x and next branches can be found below.

@Ethan-Arrowood
Copy link
Member Author

😕 Looks like master is also failing because of this TypeScript issue: https://dev.azure.com/fastify/fastify/_build/results?buildId=1702&view=results

I have class for another hour then I'll be able to investigate this. I'm worried as to why this wasn't caught before

@Ethan-Arrowood
Copy link
Member Author

Replicate by:

  • Locally pull any of 3 main branches
  • Clear node_modules and run npm install
  • Run npm run typescript

@Ethan-Arrowood
Copy link
Member Author

This commit to @types/node may be the cause of the issue: DefinitelyTyped/DefinitelyTyped@2bc4577

Regardless, I believe the fix will come as a type update on our end.

@Ethan-Arrowood
Copy link
Member Author

PRs open for all branches. CI is running for all of them as well 😄

Crossing my fingers that everything passes. After that some rebasing will need to be done on my other open prs and we can start getting stuff merged and closed 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bug typescript TypeScript related
Projects
None yet
Development

No branches or pull requests

1 participant