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
Based on what was uncovered during this Pull Request, our API Errors are getting swallowed up and outputting less that complete errors.
Primary concern is we should not break backwards compatibility with regexing on the error strings that the API is currently returning.
https://github.com/rapid7/nexpose-client/tree/conn_err_message
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Based on what was uncovered during this Pull Request, our API Errors are getting swallowed up and outputting less that complete errors.
Primary concern is we should not break backwards compatibility with regexing on the error strings that the API is currently returning.
https://github.com/rapid7/nexpose-client/tree/conn_err_message
The text was updated successfully, but these errors were encountered: