SERVER-100387 Make error code linter work with 6 digit SERVER ticket ids (#35295)

GitOrigin-RevId: a3d81970bc2d8ecf2f504589d418ac55af7f4208
This commit is contained in:
Erin McNulty 2025-04-23 11:27:04 -04:00 committed by MongoDB Bot
parent b4f58033eb
commit 65245f659c
2 changed files with 5 additions and 5 deletions

View File

@ -23,7 +23,7 @@ except ImportError:
print("*** Run 'pip3 install --user regex' to speed up error code checking")
import re # type: ignore
MAXIMUM_CODE = 9999999 # JIRA Ticket + XX
MAXIMUM_CODE = 99999999 # JIRA Ticket + XX
codes = [] # type: ignore

View File

@ -89,7 +89,7 @@ when we expect a failure, a failure might be recoverable, or failure accounting
### Choosing a unique location number
The current convention for choosing a unique location number is to use the 5 digit SERVER ticket number
The current convention for choosing a unique location number is to use the 5 or 6 digit SERVER ticket number
for the ticket being addressed when the assertion is added, followed by a two digit counter to distinguish
between codes added as part of the same ticket. For example, if you're working on SERVER-12345, the first
error code would be 1234500, the second would be 1234501, etc. This convention can also be used for LOGV2