We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There used to be a message about a failure of data service installation in zss. https://github.com/zowe/zowe-common-c/blob/master/c/dataservice.c#L118-L120
We find the message useful as we can spot the failure immediately in the log without switching to debug mode.
Could it be set at least to WARN level? Similarly, the same for other messages that indicate a failure: https://github.com/zowe/zowe-common-c/blob/e82f4c634827d8fffe0853fcb5d524658ea3c65f/c/dataservice.c#L128 https://github.com/zowe/zowe-common-c/blob/e82f4c634827d8fffe0853fcb5d524658ea3c65f/c/dataservice.c#L133 https://github.com/zowe/zowe-common-c/blob/e82f4c634827d8fffe0853fcb5d524658ea3c65f/c/dataservice.c#L137
This issue is a duplicate of the zowe/zowe-common-c#210 issue
The text was updated successfully, but these errors were encountered:
No branches or pull requests
There used to be a message about a failure of data service installation in zss.
https://github.com/zowe/zowe-common-c/blob/master/c/dataservice.c#L118-L120
We find the message useful as we can spot the failure immediately in the log without switching to debug mode.
Could it be set at least to WARN level? Similarly, the same for other messages that indicate a failure:
https://github.com/zowe/zowe-common-c/blob/e82f4c634827d8fffe0853fcb5d524658ea3c65f/c/dataservice.c#L128
https://github.com/zowe/zowe-common-c/blob/e82f4c634827d8fffe0853fcb5d524658ea3c65f/c/dataservice.c#L133
https://github.com/zowe/zowe-common-c/blob/e82f4c634827d8fffe0853fcb5d524658ea3c65f/c/dataservice.c#L137
This issue is a duplicate of the zowe/zowe-common-c#210 issue
The text was updated successfully, but these errors were encountered: