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

fix(NodeApp): fix responses with null bodies never completing #9931

Merged
merged 9 commits into from
Feb 1, 2024

Conversation

lilnasy
Copy link
Contributor

@lilnasy lilnasy commented Feb 1, 2024

Changes

Testing

Docs

Does not affect usage.

Copy link

changeset-bot bot commented Feb 1, 2024

🦋 Changeset detected

Latest commit: 61a606c

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions github-actions bot added the pkg: astro Related to the core `astro` package (scope) label Feb 1, 2024
@github-actions github-actions bot added the pkg: integration Related to any renderer integration (scope) label Feb 1, 2024
@friedemannsommer
Copy link
Contributor

@lilnasy I've come up with a different test implementation should i discard my changes or do you want to integrate them with your's?

see: friedemannsommer@68c6784

@lilnasy
Copy link
Contributor Author

lilnasy commented Feb 1, 2024

Do you mean for the tests?

@friedemannsommer
Copy link
Contributor

Do you mean for the tests?

@lilnasy Yes correct, I mean the test implementation.

@lilnasy
Copy link
Contributor Author

lilnasy commented Feb 1, 2024

The test looks great to me, I want to add that. Although adding a new fixture also means adding its build-time to the CI. If you could make it use an existing fixture, I will add it.

@friedemannsommer
Copy link
Contributor

friedemannsommer commented Feb 1, 2024

The test looks great to me, I want to add that. Although adding a new fixture also means adding its build-time to the CI. If you could make it use an existing fixture, I will add it.

@lilnasy The only other fixture with the "SSR" prefix that has "@astrojs/node" in it's dependencies is "ssr-api-route". Should I migrate the tests into this fixture then?

@lilnasy
Copy link
Contributor Author

lilnasy commented Feb 1, 2024

Could you use the one used in the current test?

@friedemannsommer
Copy link
Contributor

Could you use the one used in the current test?

@lilnasy Sure i'll use your implementation as a base then, give me ~5 minutes.

@friedemannsommer
Copy link
Contributor

friedemannsommer commented Feb 1, 2024

@lilnasy It took me a bit more than 5 minutes, sorry for that. (I am not familiar with the Node.js test runner)
I've added the examples i used to your changes here: friedemannsommer@713d019 + friedemannsommer@bd19bdb

@lilnasy
Copy link
Contributor Author

lilnasy commented Feb 1, 2024

I need to adjust errors.test.js. I can cherry pick your commit afterwards, thanks!

@matthewp matthewp merged commit 4467441 into withastro:main Feb 1, 2024
13 checks passed
@lilnasy lilnasy deleted the fix/9925 branch February 1, 2024 21:24
@astrobot-houston astrobot-houston mentioned this pull request Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pkg: astro Related to the core `astro` package (scope) pkg: integration Related to any renderer integration (scope)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Node.js SSR redirect timeout
4 participants