mirror
/
mongo
mirror of https://github.com/mongodb/mongo
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
buildscripts/errorcodes.py
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

8
docs/exception_architecture.md
View File

@ -89,10 +89,10 @@ 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
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
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
logging id numbers.
The only real constraint for unique location numbers is that they must be unique across the codebase. This is