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
Missing detailed information for some error codes #8890
Comments
i'd like to work on this |
Checking in... it has been awhile since we've heard from you on this issue. Are you still working on it? Please let us know and please don't hesitate to contact a MeshMate or any other community member for assistance.
|
@shashank-kavli hey, are you still working on the issue? If not, I would like to help here :) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Can I work on this issue? Please assign me this. |
@vansh106 you have been assigned the issue. |
This issue has been open for some time with no recent activity, unassigning to open it up for new contributors to give it a go. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue. |
Current Behavior
Currently, there is some information (Probable Cause, Suggested Remediation and Long Description) missing for some error codes like ErrClientConfigCode-1008, ErrClientConfigCode-1009 etc...
https://docs.meshery.io/reference/error-codes
Expected Behavior
The error code reference should give detailed information about individual errors and how to resolve them.
Screenshots/Logs
Environment
Contributor Guides and Handbook
The text was updated successfully, but these errors were encountered: