You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
There seems to be a way that HTTP requests need to be handled when the tested story is requesting ressources.
The problem arised when I ran test runner against a published storybook (in my case served by a golang application). When running against the local vite dev instance everything worked fine, but with my golang application a message like "Jest did not exit one second after test run..." showed up at the end and test-runner did not exit.
For reproduction purposes I then served the files via the npm http-server which worked fine.
The only thing that I can think of is that by default the HTTP connection to the golang application is left open, and node's express library (used by vite dev and http-server) sends Connection: keep-alive with Keep-Alive: timeout=5 by default, meaning that the connections will close.
To Reproduce
I do not have a reproduction that doesn't involve a golang application yet.
Describe the bug
There seems to be a way that HTTP requests need to be handled when the tested story is requesting ressources.
The problem arised when I ran test runner against a published storybook (in my case served by a golang application). When running against the local vite dev instance everything worked fine, but with my golang application a message like "Jest did not exit one second after test run..." showed up at the end and test-runner did not exit.
For reproduction purposes I then served the files via the npm http-server which worked fine.
The only thing that I can think of is that by default the HTTP connection to the golang application is left open, and node's express library (used by vite dev and http-server) sends
Connection: keep-alive
withKeep-Alive: timeout=5
by default, meaning that the connections will close.To Reproduce
I do not have a reproduction that doesn't involve a golang application yet.
System
Additional context
Could be related to #236 because the described reproduction also includes a link to an image that has
Connection: keep-alive
response headersThe text was updated successfully, but these errors were encountered: