Skip to content
This repository has been archived by the owner on Mar 22, 2022. It is now read-only.

Fixing issue where next is called twice when hitting an unauthenticated service via socket.io #18

Merged
merged 4 commits into from
Dec 20, 2015

Conversation

corymsmith
Copy link
Contributor

This fixes #17 and fixes up some intermittently failing tests.

@marshallswain
Copy link
Member

It looks like the build is failing when trying to install the bcrypt module. It looks like it's attempting on NodeJS version 5: https://travis-ci.org/feathersjs/feathers-authentication/jobs/97692661#L2823

Maybe that module hasn't been updated to work with Node v5. Want to try setting up the travis.yml to use Node v4.2.2?

@corymsmith
Copy link
Contributor Author

Still fails on bcrypt, buffer-util and utf-8-validate modules. The same thing happened with my documentation change earlier this week.

marshallswain added a commit that referenced this pull request Dec 20, 2015
Fixing issue where next is called twice when hitting an unauthenticated service via socket.io
@marshallswain marshallswain merged commit 1633918 into feathersjs-ecosystem:master Dec 20, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

next called twice using socket.io and using an unauthenticated service
2 participants