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

CP013: Support partial errors in topology discovery #79

Open
AerialMantis opened this issue Oct 4, 2018 · 1 comment
Open

CP013: Support partial errors in topology discovery #79

AerialMantis opened this issue Oct 4, 2018 · 1 comment

Comments

@AerialMantis
Copy link
Contributor

In the current revision of the paper (r3) the discover_topology function is permitted to throw an exception in case of a failure in discovering the system's topology. However, this could be problematic as this failure could prevent a library dependant on this discovery from functioning, even if the failure had nothing to do with the resources the library was looking to utilise.

A solution to this could be support partial error in topology discovery, where calling discover_topology could be permitted to fail but still return a valid topology structure representing the topology that was discovered successfully. The way in which these errors are reported (i.e. exceptions or error values) would have to be decided, exceptions could be problematic as it could unwind the stack before capturing important topology information.

@mhoemmen
Copy link
Collaborator

mhoemmen commented Oct 4, 2018

Hm, the speeds-and-feeds bit could be trouble. What happens if I discover a device, find out my bandwidth to it, but something bad happened when trying to find the bandwidth from it to me?

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

No branches or pull requests

2 participants