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

Try/catch tests need explicit connection #85

ndw opened this Issue Oct 14, 2018 · 0 comments


None yet
1 participant

ndw commented Oct 14, 2018

Since we said that secondary outputs don't automatically bind to the default output port, these tests need an explicit connection.

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