win120a opened a new issue, #11127: URL: https://github.com/apache/dubbo/issues/11127
<!-- If you need to report a security issue please visit https://github.com/apache/dubbo/security/policy --> - [X] I have searched the [issues](https://github.com/apache/dubbo/issues) of this repository and believe that this is not a duplicate. It has been a long time that the Apache Dubbo Error Code Inspector works in tolorence mode due to historical reasons. Hence, the error-code-inspecting GitHub workflow always passes the test regardless the logging method invocations contains error code or not. Since almost all logging method invocations have the corresponding error codes, and there're some absences of error codes in the 3.2 branch, in order to raise the awareness of the error code mechanism, I would like to start a discussion that about the timing of making the Error Code Inspector 'really' works. ## Describe the proposal Make the Error Code Inspector 'really' works after the 3.1 branch passes the test. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
