Problem when running with new workers implementation

Seems it losing context between processes or something ( I have told it to spawn several processes either). I’m just running forever start index.js and this error occures when the client tries to join. I’m using 0.7.0-alpha.3 on the client with: client.join(‘room’); , a note is that it works fine “localhost”, this is behind an nginx. But tried the “stable” version and they worked fine with the nginx config. but got into some other problems with that. So would need to run the latest versions 😃

data:    dist/index.js:6306 - process wants to communicate directly with pid (6320)
data:    dist/index.js:6306 - process 6320 is responding to JOIN_ROOM
data:    dist/index.js:6306 - process wants to communicate directly with pid (6321)
data:    dist/index.js:6306 - /var/www/c-c-c-combo/backend/node_modules/colyseus/lib/MatchMaker.js:85
data:    dist/index.js:6306 -         client.sessionId = clientOptions.sessionId;
data:    dist/index.js:6306 -                                         ^
data:    dist/index.js:6306 - TypeError: Cannot read property 'sessionId' of undefined
data:    dist/index.js:6306 -     at MatchMaker.onJoin (/var/www/c-c-c-combo/backend/node_modules/colyseus/lib/MatchMaker.js:85:41)
data:    dist/index.js:6306 -     at Server.<anonymous> (/var/www/c-c-c-combo/backend/node_modules/colyseus/lib/cluster/Worker.js:41:20)
data:    dist/index.js:6306 -     at emitOne (events.js:96:13)
data:    dist/index.js:6306 -     at Server.emit (events.js:188:7)
data:    dist/index.js:6306 -     at Server.emitConnection [as _upgradeCallback] (/var/www/c-c-c-combo/backend/node_modules/uws/uws.js:15:10)
data:    dist/index.js:6306 -     at Server.native.server.group.onConnection (/var/www/c-c-c-combo/backend/node_modules/uws/uws.js:465:18)
data:    dist/index.js:6306 -     at Socket.socket.on (/var/www/c-c-c-combo/backend/node_modules/uws/uws.js:502:32)
data:    dist/index.js:6306 -     at emitOne (events.js:101:20)
data:    dist/index.js:6306 -     at Socket.emit (events.js:188:7)
data:    dist/index.js:6306 -     at TCP._handle.close [as _onclose] (net.js:497:12)

[Tazer]

Absolutely, sounds great. You can absolutely do that 👌

[endel]

@Tazer I thank you 😃 very interesting! I’m about to publish a blog post this month with a couple of games, may I use yours + link to your GitHub profile there (or another link of your choice)?