Skip to content
This repository has been archived by the owner on Feb 15, 2018. It is now read-only.

Need a way to handle NoMethod, NoProperty, NoInterface dbus errors #6

Open
mulkieran opened this issue Nov 23, 2016 · 1 comment
Open

Comments

@mulkieran
Copy link
Member

If our code is correct wrt. to stratisd API then all such errors will be caused by a a missing object path. Under that assumption, what should we do?

@mulkieran
Copy link
Member Author

The missing object corresponding to the object path can legitimately go away due to the actions of another client of the stratisd daemon.

We should start thinking about catching them and raising them again, wrapped with errors indicating no corresponding object.

Then the Stratis CLI should handle those by indicating that the operation failed because the object disappeared.

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

No branches or pull requests

1 participant