Skip to content

Make the Dubbo Error Code Inspector 'really' works. #11127

@win120a

Description

@win120a
  • I have searched the 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    type/proposalEverything you want Dubbo have

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions