Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Socket.io extended Network is not allowing chained ACs #29

Closed
eudaimos opened this issue Mar 3, 2021 · 0 comments
Closed

Socket.io extended Network is not allowing chained ACs #29

eudaimos opened this issue Mar 3, 2021 · 0 comments
Assignees
@eudaimos
Labels
pkg: socket.io corresponds to the @tao.js/socket.io package pkg: utils corresponds to the @tao.js/utils package

Comments

@eudaimos
Copy link
Contributor

eudaimos commented Mar 3, 2021

When connecting to a server over socket.io using the @tao.js/socket.io package, the local (client) signal network will get the signal of an AC from the source but any subsequent AC returned to make a chain is not forwarded into the network.

It was found this is broken in the implementation of @tao.js/utils.Source that the socket.io integration relies upon.
@eudaimos eudaimos added pkg: socket.io corresponds to the @tao.js/socket.io package pkg: utils corresponds to the @tao.js/utils package labels Mar 3, 2021
@eudaimos eudaimos self-assigned this Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eudaimos eudaimos

Labels
pkg: socket.io corresponds to the @tao.js/socket.io package pkg: utils corresponds to the @tao.js/utils package
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eudaimos