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

Pipes won't work with the service. #1085

Closed

tomwilkie opened this issue Mar 1, 2016 · 0 comments

Assignees

Milestone

Contributor

tomwilkie commented Mar 1, 2016

Pipes are initialised by controls
When sending a control from the app to a probe, the app fills in its unique id, so the probe knows where to send the response (or connect the newly created pipe) to.
In the service, the apps think they have a different id to the one served under /api

To fix, have the probe will in the app id on the control request when received.

tomwilkie added this to the 0.14.0 milestone

tomwilkie self-assigned this

tomwilkie mentioned this issue

Have the probe fill in the app id, not the app #1086

Closed

2opremio mentioned this issue

Update to Scope 0.13 weaveworks/service#313

Merged

tomwilkie modified the milestones: 0.13.1, 0.14.0

tomwilkie mentioned this issue

Have the probe fill in the app id, not the app #1100

Merged

tomwilkie closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment