[SERVER-46273] During development, provide a mechanism to log in logv2 without providing a logid Created: 20/Feb/20 Updated: 06/Dec/22 Resolved: 27/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | DO NOT USE - Backlog - Dev Tools |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Developer Tools
|
||||||||
| Participants: | |||||||||
| Description |
|
During development it's occasionally desirable to be able to cheaply sprinkle log messages into source code to aid in debugging (printf style debugging). logv2 makes this painful, by requiring logids for each message (requiring some kind of elaborate provisioning system for what previously could have been as inexpensive as copy/paste). If we could provide a special log macro, or allow a special logid, that was usable in local development and for patch builds (but not allowable through the commit queue) that would enable that use case, while still enforcing that log messages have ids in production builds. |
| Comments |
| Comment by Kevin Pulo [ 21/Feb/20 ] |
|
Another possibility might be to move the running of buildscripts/errorcodes.py out of the compile task (ie. out of scons), and into lint instead. |