[SERVER-62799] Indicate that an operation tasserted in command response Created: 20/Jan/22 Updated: 30/Jan/24 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | sa-remove-fv-backlog-22 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query Execution
|
||||||||||||
| Sprint: | QE 2023-05-15, QE 2023-05-29, QE 2023-06-12, QE 2023-06-26 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently, when a tassert() is tripped, there is nothing in the command response to indicate that the failure was due to a tassert. In order to change the jstestfuzzer to fail when a command trips a tassert(), we must provide this. There are a few possible ways of doing this, and we should discuss with service arch which is best: |
| Comments |
| Comment by Ana Meza [ 04/Jul/23 ] |
|
Sending back to the Quick Wins bucket |
| Comment by Blake Oler [ 18/Oct/22 ] |
|
Go for it! |
| Comment by Kyle Suarez [ 17/Feb/22 ] |
|
After a discussion in BF Triage, we discussed that we may want tassert to act exactly like uassert in production, and not have any other special behaviors. In that case we would want to not do this ticket. Should I move this into a "Needs Scheduling" state for Service Architecture, billy.donahue? |