Comments (8)
I'm having a similar "already listening" problem, and I tried
new Server('socketioserverurl', {
forceNew: true,
reconnection: false
})
and first typescript said those weren't valid keys, and when I @ts-ignore
that error, I still have the same 'already listening' problem.
from mock-socket.
Sorry, It's actually server.stop(), but that doesn't really matter since that one does not work either :)
from mock-socket.
@Foxhoundn Thanks for finding this. Let me dig into it and see what is happening
from mock-socket.
Because I don't have access to your store/actions its going to be hard for me to debug. Are you able to create a simpler example of this bug without hitting a store?
from mock-socket.
In the meantime I found that force a new connection avoid this issue. But if one test fail all the following tests will trigger this Error: A mock server is already listening on this url
error.
new Server('socketioserverurl', {
forceNew: true,
reconnection: false
})
Is it possible that the problem is due to reconnection activated by default?
from mock-socket.
I'm also getting this error when I attempt multiple vitest cases, both concurrent and non-concurrent
from mock-socket.
@spacehash Can you please provide a minimal reproducible test case?
from mock-socket.
In my case it was a sign of a bug in my code/test which was causing it not to reach the close
call
from mock-socket.
Related Issues (20)
- Security vulnerability in url-parse dependency HOT 2
- Is this repo still maintained? HOT 5
- Using QueryParams in ws url doesn't work HOT 1
- How to mock Apollo client to test graphql subscription HOT 1
- Add `connectionDelay` option to Server to delay opening connection
- Mock ws inside web worker HOT 3
- Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.8. HOT 2
- Delay execution of dispatched events HOT 5
- Enable and disable MockSocket at runtime HOT 2
- mock-socket configuration issue ? HOT 1
- Playwright example HOT 3
- [Typescript] Client.addEventListener and Server.addEventlistener has wrong typing HOT 1
- send should throw an error if readyState is CONNECTING HOT 1
- Bug in ws client mock - wrong close code when server not found HOT 1
- Export `CloseEvent` HOT 1
- Spec doesn't actually say that `send()` should throw when the socket is `CLOSING` or `CLOSED` HOT 2
- Calling `close()` in the `CONNECTING` state should not result in open callback being called
- Do you need to import the WebSocket in this example? HOT 4
- The socket-server stops after 1 message is emitted HOT 4
- Apparently, test.cb() has been deprecated by ava HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mock-socket.