Skip to content

Commit d9c2ded

Browse files
jsteemannMongoDB Bot
authored andcommitted
SERVER-100387 Make error code linter work with 6 digit SERVER ticket ids (#31949)
GitOrigin-RevId: 5575ce4
1 parent 0ba13d3 commit d9c2ded

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

buildscripts/errorcodes.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@
2323
print("*** Run 'pip3 install --user regex' to speed up error code checking")
2424
import re # type: ignore
2525

26-
MAXIMUM_CODE = 9999999 # JIRA Ticket + XX
26+
MAXIMUM_CODE = 99999999 # JIRA Ticket + XX
2727

2828
codes = [] # type: ignore
2929

docs/exception_architecture.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ when we expect a failure, a failure might be recoverable, or failure accounting
9090

9191
### Choosing a unique location number
9292

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

0 commit comments

Comments
 (0)