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.

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

Fails to go to project mode second time for noflo-browser #748

Open
jonnor opened this issue Jul 21, 2017 · 1 comment
Open

Fails to go to project mode second time for noflo-browser #748

jonnor opened this issue Jul 21, 2017 · 1 comment

Comments

@jonnor
Copy link
Member

jonnor commented Jul 21, 2017

To reproduce:

  • Run noflo-browser with noflo-runtime-webrtc. Specify a fixed runtime ID
  • Open the runtime in Flowhub via live URL, go to project mode
  • Observe connected OK to runtime
  • Close Flowhub, restart the runtime
  • Open the runtime in Flowhub via live URL, go to project mode

Expected: Connects to runtime in same way as first time, using WebRTC
Actual: Does not connect over WebRTC. Instead a new noflo-browser iframe runtime is loaded

This only happens if the runtime ID is the same as one previously used. This leads me to believe that the connection details are being overwritten somewhere.

Workaround: Always generate a new runtime ID

@jonnor
Copy link
Member Author

jonnor commented Aug 24, 2017

When specifying namespace also in runtime info, the problem seems to go away

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

No branches or pull requests

1 participant