You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, pywbem exceptions do not contain any information to relate the issue to a server connection. This would be particularly useful for connection-related issues, but also useful for e.g. CIM errors.
The idea is to add fields to the exception for the connection id and for the server url. Probably it makes sense to have that in the message, at least for connection related exceptions.
The text was updated successfully, but these errors were encountered:
The solution for the remaining cases of raising pywbem exceptions is as follows:
For the tupleparse module: Put the module-global parse_...() and most other functions into a new class that stores the connection ID as an instance attribute.
For the tupletree module: Add the connection ID as an additional optional argument to the three relevant functions of that module that raise exceptions.
Today, pywbem exceptions do not contain any information to relate the issue to a server connection. This would be particularly useful for connection-related issues, but also useful for e.g. CIM errors.
The idea is to add fields to the exception for the connection id and for the server url. Probably it makes sense to have that in the message, at least for connection related exceptions.
The text was updated successfully, but these errors were encountered: