With the new socket authentication from #230, we get a new promise rejection. Seems to be caused by being unable to correctly fetch a user from a JWT.
Unhandled rejection (promise: Promise {
<rejected> TypeError: Cannot read property 'id' of null
at module.exports.getAuthzForUser (/home/waf/queue/build/auth/util.js:70:26)
at Socket.socket.on (/home/waf/queue/build/socket/server.js:198:34)
at Socket.emit (events.js:180:13)
at /home/waf/queue/node_modules/socket.io/lib/socket.js:528:12
at args.(anonymous function) (/home/waf/.nvm/versions/node/v9.9.0/lib/node_modules/pm2/node_modules/event-loop-inspector/index.js:138:29)
at process._tickCallback (internal/process/next_tick.js:112:11) } , reason: TypeError: Cannot read property 'id' of null
at module.exports.getAuthzForUser (/home/waf/queue/build/auth/util.js:70:26)
at Socket.socket.on (/home/waf/queue/build/socket/server.js:198:34)
at Socket.emit (events.js:180:13)
at /home/waf/queue/node_modules/socket.io/lib/socket.js:528:12
at args.(anonymous function) (/home/waf/.nvm/versions/node/v9.9.0/lib/node_modules/pm2/node_modules/event-loop-inspector/index.js:138:29)
at process._tickCallback (internal/process/next_tick.js:112:11) ).
With the new socket authentication from #230, we get a new promise rejection. Seems to be caused by being unable to correctly fetch a user from a JWT.